Sending Calendar Invites to millions using AWS PinPoint and AWS SES

Using Pinpoint or other Lambda upload methods to send millions from email lists

Introduction

This use case focuses on direct calendar invite sending and how we have staged the direct sending workflow in the demo application that comes with the Calendar Invite Server, called Calendarsnack.

API# 3 is for both embedded web pages and direct calendar invite list sending or what we refer to as “BULK” uploading. In AWS terms, this could be an AWS list request from the Pinpoint API to shuffle the list to our APIs. 

1. The customer logs into the Calendarsnack App. The APIs supplied for the Calendarsnack Service build out the VUE.APP in the browser in the CDN and start the customer session.

2. Once the customer signs up for the CalendarSnack Service, the customer can proceed to the Dashboard in the Free Version.

3. In this example, the no-code VIP LIST is selected in the send options and configured to send calendar Invites to the email list in 10 seconds.

The VIP List can be used in marketing campaigns to choose events and send calendar invites to the email address in the box. It is perfect for Calendar Invites and large email Lists of 5K+, and the AWS Pinpoint API Integration is being worked on to insert it into this Lambda workflow.

4. The Calendar Invite API call is made to the API gateway to summon a calendar invite from the storage layer for that event. A Lambda assembles the calendar invite for AWS SES transport, including proper encoding for the MIME type and multipart for that specific calendar invite using the AWS RAW API using the Calendar Invite Server API#3 and Lambda #2.

5. Edits, Cancels, or what the Calendar Client considers an Update to the original Calendar Client used to create the event are now registered with the Calendar Invite Server UID. Suppose there is an update to the Calendar Invite UID. In that case, the automation Lambda updates the information in the database and then resends the calendar invite information through AWS SES using the same process.

RSVP receipts are gathered from the customer’s Calendar Invite until the event ends via the API gateway and stored in an S3 bucket for retrieval.

6. The data for all events is stored for the individual UIDs of the calendar invites and aggregated for the Organizer to view from S3 in the VUE.JS Dashboard that the reporting API calls in the application.

AWS Quick Sight is an alternative to the Vue dashboard for viewing all events in the email or domain owners.

Licensing

The Calendar Invite Server is free to download and test for up to 50,000 sends.

After that has been met, a $5,000 yearly fee is charged to use the product with periodic updates.

That includes the demo app - Calendarsnack front end.

We do not connect to your account. You run it and own it in your AWS account. Includes all access to Lambdas and APIs to modify or change.

We provide periodic updates via our private Github account.