1 - We made the CIS Pipeline easy for organizers
In the demo, Mandy uses create@calendarsnack.com in her calendar client, and that event is then registered into the CIS database.
The Calendar Client is then attached to that record in the CIS database for the event and can be updated or canceled by using the same event through the Calendar Client for Editing or Cancellation and then saving it with the same create@calendarsnack.com email address in the list of attendees.
Once the save occurs, the data is pushed back through the pipeline.
This series of functions prepares the data to be created, updated, or canceled by the Organizer Calendar Client.
The Calendar Invite Server is designed to be installed in an AWS account in 1 hr and includes access to all APIs, functions, lambdas, and Python code.
The Front End is designed as a VUE.JS GUI that comes with an installer and notes on how it was built for the Organizer and the Domains System Administration User.
Inbound - Calendar Invite Disassemble
The calendar invite is copied to an email box.
The calendar invite data is disassembled and stored as a “NEW” Event in the DB with an assigned UID.
If an update occurs to the original calendar invite and is saved, it is resent to the AWS SES Mailbox and follows the “NEW” workflow with a UID increment added, we have developed.
Updates can occur an unlimited number of times before or after the new event creation.
Examples are for date, time, location, or message body changes. Or for promotional offers.
Cancellation can occur at any time before the event, and it is marked in the DB.
Outbound - Calendar Invite Assembly
The stored Calendar Invites in the CIS can be retrieved using the Calendar Invite Send API Endpoint, which matches the Email to the UID and reassembles the calendar invite for that specific event, then sends it using the AWS SES RAW API with our proprietary workflow.
Updates or cancellations to the event from the Organizer’s Calendar Client are then processed in the messaging pipeline, and the updated or cancelled Calendar Invites are sent out to anyone who has responded Y or M to the previous event.
This is a software switch in the Calendar Invite Server and can be queued for approval if needed.
By default, we allow Update or Canceled Calendar Invites to be sent automatically through the pipeline.
2 - Calendar Clients are Rockstars for CIS
Why is the Calendar Client so Important to the Calendar Invite Server?
We have no infrastructure costs associated with building and maintaining a calendar client.
We work on all languages that Google and Outlook Calendar support.
We support Calendar Invite Ingest for new, update, and cancel operations of the Calendar Client.
The Calendar Clients are supported across Mobile, Web, and Desktop.
The Calendar Invite Server is now ready for AWS Customers today.
The Calendar Client excels at organizing large datasets, such as those for the NBA, NFL, and NHL.
3 - The CIS APIs can be used to build mini applications and microsites quickly
The data loading is trivial compared to the value it could bring to a retailer or brand that wants to enhance the customer experience and communicate directly with customers' calendars.
The Calendar Invite Server and Front-End Applications can be deployed within a few hours into your AWS account.
See Arnie’s Explainer on this concept.
https://nfl2025.31events.com/docs
4- The same Messaging pipeline is used for displaying and analyzing Calendar Event Data in the Event Organizer Console with the same APIs
The Calendarsnack App comes with the Calendar Invite Server and can be rebranded for use in your brand or vertical market.
There are a total of 9 APIs that are well-documented on GitHub, along with the Calendar Invite installation guide for an AWS account.
5 - The Embedded Calendar Invite API is the 1 Click Calendar Invite for Customers and a gold mine of data for Event Organizers
The One-Click Calendar Invite is straightforward for customers of the NFL Demo Game Schedule.
Please review the build template here. https://nfl2025.31events.com/
This should apply to any Sports Schedule.
Enter your email address in the box, click the game, and receive a calendar invitation.
The data from the APIs is presented in the Calendarsnack dashboard. This includes the email address and the status of the event from the calendar receipts, which can be represented as Y, M, N, or not answered.
Then, the organizer can decide to run a promotion directly to those customers who have the event on their calendars.
Y, N, M data is collected for analytics.
Summary
We create, send, update, and cancel calendar invites using an automated pipeline that utilizes the AWS stack with the Organizer Calendar Client as a CRUD interface. The invention comprises 30 functions and nine core APIs for moving and shuffling calendar invite data in the pipeline, facilitating calendar invite sending from the REST API we have developed.
This CIS pipeline was built for simple yet powerful Calendar Invite sending in marketing and Transactional Use Cases.
https://www.youtube.com/@calendarinvite
