Why I didn’t hire an event manager for my wedding

Why I didn’t hire an event manager for my weddingYasith LokugeBlockedUnblockFollowFollowingJan 19rsvp and automated mobile notification system using webtask and AWSAfter reading this article, you may find the title of this article somewhat misleading.

This is not about how I planned my wedding.

In this article I’ll explain how I created a very basic RSVP system to remind the guests of the wedding date and inform their table numbers.

Not only that, I’ll cover how I distributed the wedding day tasks within a group of family members and how I reminded them by sending mobile notifications at the time on which the task required to be performed.

RSVP website and SMSIn this section I’ll explain how I created RSVP website along with the SMS notification (guests) and email notification (host) system.

First I’ll briefly explain the flow of the design.

I assigned each guest a unique id.

You can easily generate bulk UUID using this website.

After generating sufficient UUIDs for the number of guests, you will notice that only the first 8 characters of the IDs were unique.

Therefore you can remove the remaining digits and use only the first 8 characters.

There are three main parts of the application.

RSVP websitePython script for sending personalised SMSWebtask serverlessRSVP website is a simple angular 5 application and you can find the code from this github repository.

Python script will read a csv file in a particular format and send SMS to the guest using AWS SNS.

Keep in mind that AWS SNS does not allow you to send SMS more than a certain budget.

So make sure you make a budget increase request to the AWS support before planning to send SMS.

Furthermore, I’m using google url shortener API.

In order to use that, you may need to acquire an access token first.

Please make sure that your list.

csv is in the following format.

name, mobile number, table number, unique id,list.

csvOk, now the most important thing — backend.

I decided to use Auth0’s webtask instead of going for AWS lambda because I found it so easy to use and the embedded json datastore was ideal for my use case.

for the backend I’m using 3 serverless functions.

wedding.

jsthis is the main function which returns the guest details when the unique id is provided through the frontend.

Webtask has its own embedded json data storage, so I used that in order to store the guest details.

json data format should look like follows,{ "f3dca298": { "name": "Mr & Mrs John Doe", "table": "19" }, "ceabcc5e": { "name": "Mr Matt Peiris", "table": "26" }, .

}wedding-reply.

jsThis function is used to get the response from the guest and send it back to the organisers.

Make sure you obtain an access key from SendGrid in order to send emails using their API.

Furthermore, you can store the access key inside webtask secrets storage.

wedding-store.

jsThis is an optional function which I created to track the number of visits from a certain guest.

This will write data to the embedded json data store with the number of times the user visited our website.

Initially you should add a dummy data to the data store in the following format.

{ "counter": 1,.

}I think I have covered everything for the RSVP website and SMS system.

Now I’ll move on to the SMS reminder system for the organisers.

SMS reminders for the organisersMost difficult part of planning any kind of event is assigning people with tasks and give them the ownership.

When it comes to a wedding, the bride and groom can’t engage in any kind of task during the time of the wedding.

Hence all the tasks should be assigned to a set of friends and family members.

In this section I’ll explain how I reminded them about the tasks they were assigned with few minutes before which the task needed to be performed.

task remindersI used AWS Lambda function (python) using Serverless framework and specified a set of cloudwatch events to trigger the function with a set of parameters.

Lambda function is just a skeleton and the task, mobile number, name of the assigned person, time on which the task need to be performed will be passed through the cloudwatch events.

The events part of my serverless.

yml looks like follows.

functions: hello: handler: handler.

hello events: – schedule: rate: cron(15 20 5 12 ? 2018) enabled: true input: name: 'Charini' number: '+947xxxxxxxx' task: '1.

35 am Testing for mobitel, reply yasith if works'- schedule: rate: cron(15 20 5 12 ? 2018) enabled: true input: name: 'Yasith' number: '+94xxxxxxxx' task: '1.

35 am Test message, reply yasith if works'- schedule: rate: cron(0 4 6 12 ? 2018) enabled: true input: name: 'Nimanthika' number: '+94xxxxxxxx' task: 'Attend to Jayamangala girls / Dancers / Ashtaka (Check whether they got drinks)'AWS won’t allow you to create more than a certain number of cloudwatch events for a given function, in which case you may need to request them to increase the limit, or you can divide the events within a set of functions.

Even the webtask supports cron expressions but I haven’t tried that yet.

Maybe you can try using webtask as well.

This article does not provide the background knowledge for the technologies I used here.

There are plenty of other resources you can refer if you are not familiar with those technologies.

Initially I was planning to create a SaaS platform for this use case, where the users can create events, assign users, send sms on their own.

However it was on hold due to certain other priorities.

If you are an event organiser or an event host who is planning to use this kind of solution, please feel free to contact me through my email yasith1@gmail.

comI hope you enjoyed this article, and if you have any questions, please comment below.

I’m more than happy to answer your queries.

.

. More details

Leave a Reply