Iterable's Zapier integration makes it easy to connect to the apps you're already using. Here's some examples of what you can do using Zapier:
- Collect Unbounce landing page submissions and automate on-boarding emails
- Forward SurveyMonkey responses to Iterable
- Add new Delighted NPS Survey responses to your contacts in Iterable
- Add GoToWebinar signups to reminder and follow up workflows in Iterable
- Add new Facebook Lead Ad submissions to Iterable Onboarding Workflows
Zapier is essentially a way to forward activity collected in one app (the trigger) to another app (the action). Each trigger/action combo is called a "Zap." You can chain multiple actions together so that in one Zap you can (for example):
- Capture an email from your blog via Gravity Forms.
- Enrich the data with Lead Score by Zapier or Clearbit.
- Filter the non-work emails
- Add only contacts with a work email to Iterable
#What actions does Zapier support?
- Create/update a user
- Track a custom event
#Connecting Zapier to Iterable
Before opening Zapier, we recommend creating a unique API Key for use with Zapier. You can create a new API key by navigating to Integrations > API Keys:
Request access to the beta integration.
Click Make a Zap.
Zapier connects to hundreds of apps, for the sake of this example we’ll be using Typeform. You can choose any Zap you like; we recommend using one that contains an email field since Iterable’s Action steps require an email.
For the action step, select Iterable. If you do not see Iterable as an option, make sure you have requested access to the beta.
If you haven’t connected to your Iterable account already, Zapier will ask you to enter the API key you generated in step 1.
We recommend using sandbox projects for testing. Zapier allows you to integrate multiple Iterable projects in your Zapier account. Make sure to rename your account in Zapier in a way you can easily recognize. Each project will have a unique set of API keys.
For this example, we’ll use the Create/Update a User option.
Configure your Zapier template by mapping fields captured in other apps to Iterable.
Once you’re ready to test the Zap, click Continue and send a test user to Iterable. You’ll be able to find the user by going to Users > User Lookup and entering their email address.
Once you’ve activated the Zap, Iterable will automatically capture contacts that have submitted the Typeform survey. If they’re an existing contact, their contact record will be updated with any new information in the survey submission. Iterable will use the email address to determine if the contact is the same.
The contact can then:
- Be added to dynamic lists based on data sent from Zapier.
- Have personalized messages sent to them using merge parameters.
- Change their path in a workflow based on their survey submission with workflow filters.
#Tracking a Custom Event in Iterable through Zapier
In addition to Adding/Updating contacts to Iterable, Zapier can also send custom events to:
- Trigger contacts into a workflow.
- Segment contacts based on custom event history.
- Track campaign conversions.
- Measure which variant in an experiment resulted in the conversion.
One example we'll set up is sending a reminder email and SMS to the contacts that have registered for an event.
In Zapier, click Make a Zap.
For the Trigger, select your event registration app. In this case we’re using Splash That. In this example event, we are capturing the registrant’s name, email, and phone number.
For the action, select Iterable. If you do not see Iterable as an option, make sure you have requested access to the beta.
Select Track Event and your connected Iterable project.
In the Edit Template page, add an Event Name, Email, and any additional fields (phone number and first name) into the JSON data fields.
If you are using this custom event to trigger a conversion in another campaign, you can also include the campaign ID and template ID for the campaign and the conversions and experiment results will be tracked in Iterable.
For this use-case, we’ll want to create a workflow in Iterable to capture these events and add the contacts into a list of registrants. This can be done by creating a simple workflow that’s triggered off of the Custom Event, adds the custom event data to the contact’s record, and adds the contact to a list:
Now the fun part: we'll create a workflow in Iterable to send a reminder email and text to the registrants.
Create a new workflow and configure the trigger to use the recurring event. We’ll use the recurring event trigger to set up a scheduled one-time send on the day before the event. To ensure the trigger only fires once, we set the end date before the next scheduled recurrence.
Lastly, let’s add the action to send a reminder email at 9:30AM the day before the event then delay until 10AM on the day of the event to send a reminder SMS.
#Where do I request more Triggers/Actions to be added to the integration?
Right now, this integration is in beta. We are taking feedback on which Zaps should be added. For now, send requests to firstname.lastname@example.org with the subject line "Zapier Beta Feature Request". V2 of the integration is not slated until early 2019.
#Will Send Event create a user if they do not currently exist in Iterable?
Yes, the user will be added to Iterable with the email specified in the Template. If data fields are passed through the event that should be stored in the contact record, we recommend creating a simple workflow triggered by the custom event and an update contact fields action using merge parameters from the event properties.