Iterable Zapier integrationAutomate Iterable with Zapier.
The Iterable Zapier integration gives you 0 triggers, 6 actions and 0 searches. It is a one-way street into Iterable: user profiles, custom events, purchases and shopping carts arrive from your other tools, ready for the campaigns you already run there.
Verified Trustpilot reviews · AI, automation & growth agency
What the Iterable Zapier integration is for
Iterable is a growth marketing platform: it personalizes your campaigns, but only around the people and behaviors it has on record. This integration feeds it. A Zap (the automation you build on Zapier, one starting event followed by the steps it sets off) takes something that happened in another tool and writes it into Iterable.
Three things you can build with it:
Fresh profiles from every signup. A form, a webinar tool or a CRM hands each new contact to Create a User, so onboarding sequences start with no CSV import.
Behavior Iterable could not see on its own. Track Event records a custom event, say a demo booked in a scheduling tool, which your journeys can then react to.
Revenue and abandoned carts. Update a User's Shopping Cart Items keeps the cart current, and Track a Purchase logs the order and empties that cart in the same move.
What Zapier does not do here: it cannot start a Zap from Iterable. There is no trigger and no search, so an unsubscribe, an email open or a campaign send in Iterable will never set anything off on the Zapier side. Data goes in, nothing comes back out.
The same app is documented as an Iterable n8n integration and an Iterable Make integration if you need to compare what each platform exposes.
Zapier vocabulary in one minute
Seven words come back on this page. Here they are in plain English, once.
- Zap
- The automation itself: one event that starts it, then one or more steps that run every single time that event happens.
- Trigger
- The event that starts the Zap. With Iterable it always comes from another app, since Iterable offers none.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you. All six Iterable operations are actions.
- Task
- The unit Zapier bills. One action that completes successfully is one task, and your plan counts those.
- Instant vs polling
- An instant trigger is reported by the app the moment it happens. A polling trigger is checked by Zapier on a timer instead.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and quietly stops it otherwise.
- Multi-step Zap
- Anything beyond one trigger plus one action. Add a filter or a second action and you are there, which means a paid plan.
What an Iterable Zap really costs
Iterable is not reserved to paid plans, so it runs on the free plan. Every Iterable step is an action, which means every successful run is billed.
- Paid plan requiredNo, free plan works
- Free plan100 tasks a month, two-step Zaps
- Each Iterable actionOne task when it succeeds
- Failed actionNot counted
One successful action is one task; the trigger in the other app costs nothing. A Zap that creates a user and then tracks an event spends two tasks per signup, and an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, capped at two steps each: one trigger, one Iterable action. Chain two Iterable actions, or add a filter, and the Zap becomes multi-step and needs a paid plan. How fast the Zap starts depends on the trigger app, not on Iterable.
Connect Iterable to Zapier in three steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Iterable account linked to Zapier once, then reused by every Zap that writes to it.
- 02
Pick Iterable and sign in
Search Iterable in the dialog, select it and click Add connection. Sign in to Iterable in the tab that opens, with an account that has write access to the Iterable data your Zaps will touch.
- 03
Grant access
Approve the access Zapier requests. Zapier also attaches a getting-started article for Iterable in its help center, worth a read before the first test.
Your first Zap: new signups become Iterable users
GoalCreate an Iterable user for every new signup collected in another tool, then record a custom event so a welcome journey can start.
- 01
Pick the starting app
Create a Zap and choose the form or tool where people sign up, with its new-entry event. Iterable has no trigger, so the Zap always opens on another app.
- 02
Test that trigger
Run the test. Zapier brings back the three most recent items of that account, so you map fields from a real signup rather than an empty sample.
- 03
Add Create a User
Add Iterable as the action, pick Create a User, select your connection and map the contact details from the form into the profile fields.
- 04
Add Track Event
Click the plus icon, add Iterable again with Track Event and type the event name your journey listens for. This second action makes it a paid, multi-step Zap.
- 05
Test, then publish
Test each step and read what came back, then click Publish. Each signup now costs two tasks, one per Iterable action that succeeds.
Iterable actions
Iterable gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a User
ActionIn Zapier“Add new user profile data. Iterable API users/update docs”
Adds a new profile to Iterable from data collected anywhere else, so the person exists before your first campaign tries to reach them.
Track Event
ActionIn Zapier“Create a custom event. Iterable API events/track docs”
Records a custom event on a user, giving your journeys a behavior to react to that Iterable could not observe itself.
Track a Purchase
ActionIn Zapier“Tracks when a user makes a purchase. Also clears shoppingCartItems on the user profile.”
Logs a completed order on the user and, in the same run, clears the shopping cart items saved on that profile.
Update a User's Shopping Cart Items
ActionIn Zapier“Update the "shoppingCartItems" field on the user profile with shopping cart items. User profile is updated if it already exists (created otherwise).”
Updates the cart items stored on a profile with the current contents, and creates the profile if it did not exist yet, so Iterable knows what each person left behind.
Update a User
ActionIn Zapier“Update user profile data. Iterable API users/update docs”
Rewrites profile data on someone Iterable already knows, which keeps segments accurate when a plan, a role or a preference changes in another tool.
API Request (Beta)
ActionIn Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”
The advanced option: it sends your own HTTP request to Iterable, reusing the connection you already set up, for anything the five other actions do not cover.
When an Iterable Zap breaks
Zapier lists one help article for Iterable, How to get started with Iterable on Zapier. The rest of what breaks comes from the general limits, plus two behaviors of the actions themselves.
Since everything flows into Iterable, most failures are silent: the Zap runs, but the profile or the journey does not look the way you expected. If you are stuck, see the Zapier troubleshooting page.
Past signups are not imported
A Zap only reacts to what happens after you switch it on. Contacts collected before stay out of Iterable; moving that backlog is a separate job.A purchase empties the cart
Track a Purchase also clears the cart items on the profile. Run it before an Update a User's Shopping Cart Items step and the cart reappears.API Request stays inside Iterable
API Request (Beta) can only call Iterable's own domains. Pointing it at another address fails, and Stop on error decides whether the Zap halts there.A bulk import gets held back
If the trigger app suddenly returns a huge batch, after a migration for instance, Zapier's flood protection can hold the run back.
Need help automating Iterable with Zapier?
A person reads every message.
