Bulk Calendar Invite Sending is cool
This is a tech talk on sending bulk calendar invites with a Rest API.
We create, send, track, and cancel calendar invites for web and email use cases.
The Front end and back end are available for installation into your AWS account with a CloudFormation template to build out your Calendar Invite strategy.
We use data from MLB, NBA, and NFL for demo purposes only.
Ready to deploy your own AWS RSVP Engine
The Project is ready for download into your own AWS account, complete with installation instructions for Front and Back end, and an optional CI/CD pipeline for developers and production for GITHUB.
Step 1. Pick the Event from the VIP List Interface, also known as BULK Sending of Calendar Invites to an authorized list.
Washington VS Indiana is selected for Round 16 on Feb. 19th in the picker.
When the “Use Event“ button is clicked, that Event is loaded into the Bulk Uploader Interface for sending Calendar Invites to a List.
The Bulk Uploader is now ready to upload a TXT or CSV file via the picker in the browser interface.
This list has been loaded into the browser app and is ready to send.
Send VIP Invites is selected, and the email list is sent to the Outbound processor, which includes the Lambas for the REST API.
>SEND VIP INVITES Button<
The button triggers the OUTBOUND processor, which houses the Lambda Logic and workflow for the REST API that packages the Calendar Invite UID data, sends a correct Calendar invite via the AWS SES RAW API to each email address on the list, and REQUESTS a calendar receipt for tracking back to the API gateway.
The stored Calendar Invite UID data is used via the Calendar Invite Send REST API endpoint to send Calendar Invites.
This REST API is a multi-purpose API used to SEND Calendar Invites for RSVP Buttons (e.g., Mailchimp), embed Calendar Invites in Sports Schedule Web Pages, and embed the API in a GUI Picker for selecting and sending Calendar Invites to a bulk email List.
In all use cases, the API matches the Email collected to the Event UID stored in DynamoDB, reassembles the calendar invite data from DynamoDB using ETL functions, and sends the package via AWS SES RAW.
The calendar invites are crafted to request a calendar receipt from the customer’s calendar client for each event.
Calendar Invite Receipt Data Collection
Every Calendar Invite sent from the Outbound Processor requests calendar invite receipts for collection, storage, and decision-making. The calendar receipt is sent back to the API gateway and continuously monitored until the event time for that UID. We follow RFC 1554, which specifies how to collect calendar receipt data across calendar clients.
9 APIS for Calendar Invite Creation, Sending, Updating, and Data Collection
The Front-end CalendarSnack App communicates via 9 APIs, which in turn interact with 30 Lambda functions to build the GUI and generate workflows.
For a detailed HLD, see our GitHub.
https://github.com/calendarinvite/calendarinviteserver/wiki/AWS-Calendar-Invite-Server-%E2%80%90HLD
