While Tito doesn't have a dedicated Mailchimp plugin, you can use webhooks with an automation service like Zapier to configure your own integration. This article provides basic instructions for how to get started, which you can adapt according to your own requirements.
💡 Webhooks allow data to be passed from Tito to an external system in real time. If you're new to webhooks, you may wish to read this help article before getting started.
Setting up a basic integration
It's up to you which endpoint you listen for when setting up your integration. Our example below uses the
ticket.completed webhook, which is fired when all required fields like name, email, etc and required questions have been answered. Essentially, this means that an attendee would get added to Mailchimp once they have filled in their ticket details.
Although there are a few steps involved in getting set up, the flow is pretty straightforward:
Create or log in to your Zapier account and set up a new connection.
Opt to connect "Webhooks by Zapier" with "Mailchimp".
The trigger (i.e. when this happens) should be set to "Catch hook", and the outcome (i.e. then do this) should be set to "Find or create subscriber".
Click to "Use Zap" and copy the webhook URL that Zapier generates.
Open up your Tito event dashboard, navigate to Settings > Webhook endpoints, and then click on "New webhook endpoint" and paste the URL from Zapier. Check the
ticket.completedwebhook box (or any of your choice, based on the options here) and save.
Head back over to Zapier, and hit "Continue".
To test the webhook is firing correctly, put through an order for a single ticket in Tito, and click on "Catch hook" in Zapier to see the captured webhook.
Next, select the "Mailchimp" step in Zapier (ensuring the Mailchimp app is selected), and set the action to "Add/update subscriber", then continue to the next step. You will need to authenticate your Mailchimp account if you haven't already.
Follow the on-screen instructions to set your audience, then select the "Subscriber email" field. Under "Catch hook" you want to also select "Email" from the dropdown. Send a test to check that it shows up in Mailchimp.
When you've finished editing, enable the Zap and put through another Tito order to double check the email address is added to Mailchimp on ticket completion.
Note: The instructions above refer specifically to Zapier's copy at the time of writing this help article, but the general principles may be applicable to other automation services. You could also potentially adapt these instructions to pair Tito with a service other than Mailchimp.
A few things to be aware of
This integration is basic, and subject to some limitations. For instance, the original attendee's email address will remain in Mailchimp even if their ticket is reassigned or voided (unless you configure a Zap to handle these situations). Additionally, it should be noted that webhooks are sent to Zapier whether the Tito event is in test mode or not.
If you’re concerned about any of these points, you may prefer to export your Tito attendees, review the data, and import them into Mailchimp manually. However, if you're looking for a way to handle copying email addresses across automatically, this could be a good option.
If you have any follow-up questions, drop us a line at firstname.lastname@example.org or chat to us in-app and we’ll get back to you as quickly as we can.