Resources · Zapier integration

Autopilot Journeys Zapier integrationAutomate Autopilot Journeys with Zapier.

The Autopilot Journeys Zapier integration has 4 triggers and 4 actions, all about contacts and lists. Every trigger is instant, even on the free plan. Here is what each operation does, what it costs and where contact syncs go wrong.

See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Autopilot Journeys Zapier integration does

The Autopilot Journeys Zapier integration links Autopilot Journeys, a visual tool for automating customer journeys across email, SMS, web and mail, to your other apps without code. It keeps contacts moving both ways: new people flow into Autopilot lists, and list changes or unsubscribes flow back out to your CRM or your sales tools.

Three outcomes cover most setups. Journeys fed from anywhere: a webinar sign-up, a checkout or a CRM deal runs Add Contact to List, and since lists can start journeys in Autopilot, the right sequence begins on its own. Unsubscribes respected everywhere: Contact Unsubscribes fires the moment someone opts out, so your CRM or your other email tool can mark them too. Clean exits: Contact Removed From List tells your sales team when a lead leaves a nurture list, and Delete Contact handles erasure requests from another system.

What the integration does not cover matters as much. There is no search step, so a Zap cannot look up a contact first. There is no action to remove someone from a single list, no way to update tags or fields outside the add actions, and nothing about email opens or clicks. Contacts that existed before your Zap was switched on are never picked up.

The same app is covered on the Autopilot Journeys n8n integration and the Autopilot Journeys Make integration pages, if you are comparing platforms.

Vocabulary

Zapier vocabulary, the short version

Seven words do most of the work on this page. Here is what each one means.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier simply waits for that event to come in.
Action
What the Zap does after it starts: the step that adds, deletes or updates something for you, here mostly contacts.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan allowance counts nothing else.
Polling vs instant
Zapier checks a polling trigger on a timer. An instant trigger is sent by the app itself the moment the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it there otherwise.
Multi-step Zap
Any Zap with more than one trigger and one action. A filter or a second action makes one, and it needs a paid plan.
Cost

What an Autopilot Journeys Zap costs

Autopilot Journeys is not reserved for paid plans, so the free Zapier plan can connect it. The bill depends on actions, never on triggers.

  • Paid plan requiredNo, free plan works
  • Free plan100 tasks a month, two-step Zaps
  • Trigger cost0 tasks
  • Autopilot triggers4 of 4 instant

Triggers cost nothing, and Zapier checking for new data costs nothing either. Each action that succeeds counts once, so a Zap that adds a contact to a list and then posts a message uses two tasks per run. A failed action is not counted. The free plan offers 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger and one action. A filter or a second action makes the Zap multi-step, which requires a paid plan. All four Autopilot triggers are instant, so the polling grid below never delays them.

Connect

Connect Autopilot Journeys to Zapier

  1. 01

    Open your connections

    In Zapier, go to Apps and click + Add connection. The connection you create here is reused by every Zap and every step that talks to Autopilot Journeys afterwards.

  2. 02

    Select the app and sign in

    Type Autopilot Journeys in the dialog, pick it, then click Add connection. Sign in to the Autopilot account that holds your contact lists in the tab that opens.

  3. 03

    Grant access

    Approve the access Zapier asks for. You need an Autopilot account, plus access to any list or contact you do not own yourself but want the Zap to read or change.

First Zap

Your first Autopilot Journeys Zap

GoalWhen a webinar registrant joins your registrants list in Autopilot, they also join the sales follow-up list, but only when a company is filled in.

  1. 01

    Set the trigger

    Create a Zap, choose Autopilot Journeys and the Contact Added to List event, select your connection, then the Contact List of webinar registrants.

  2. 02

    Test with real contacts

    Run the test: Zapier brings back the three most recent contacts who joined that list, so you map fields on a real person.

  3. 03

    Add the filter

    From the plus icon add Filter, choose the company field, a rule that checks it exists, then Configure & test. The Zap is now multi-step.

  4. 04

    Add the list action

    Add Autopilot Journeys again with Add Contact to List, pick the sales follow-up list, never the list the trigger watches, and map the Email field from the trigger.

  5. 05

    Publish

    Test the last step, check the contact in the new list, then click Publish. The lightning bolt in the editor confirms the trigger is instant.

Triggers

Autopilot Journeys triggers

4 events start a Zap when something happens in Autopilot Journeys, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Contact Added

Instant trigger

In Zapier“Triggers when a contact is newly added.”

Any person who appears in your Autopilot account, whatever the source, starts the Zap. A form on your site, an import or another integration: they all count, because the trigger watches the whole contact base rather than one list.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
copying every new Autopilot contact into your CRM so sales sees the same people as marketing.
Watch out
it also fires for contacts added by your own Zaps, so a Zap that writes back into Autopilot can loop.
2

Contact Added to List

Instant trigger

In Zapier“Triggers when a contact is newly added to list.”

This one is narrower: it reacts only when someone joins a specific list. Lists are how Autopilot groups contacts for a journey, so this is the trigger for following one segment instead of everybody.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
notifying a sales rep in chat when a lead joins your hot leads list.
Watch out
the Contact List field is required, so each Zap follows one list; two segments mean two Zaps.
3

Contact Removed From List

Instant trigger

In Zapier“Triggers when a contact is removed from a list.”

The reverse move: the Zap runs when a contact leaves a chosen list. The person stays in Autopilot, they just stop belonging to that segment, which often means a journey has ended or a status changed.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
moving a lead to the next stage in your CRM when they finish a trial nurture list.
Watch out
like the previous trigger, it requires a Contact List chosen when you set it up.
4

Contact Unsubscribes

Instant trigger

In Zapier“Triggers when a contact unsubscribes from Autopilot.”

When a person opts out of your Autopilot emails, this trigger passes their details on. It is the safest way to make sure an opt-out recorded in one tool is honoured in the others.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
marking the person as do-not-email in your CRM and any other sending tool you use.
Watch out
it covers the whole account, so there is no list to choose and no way to limit it to one segment without a filter.
Actions

Autopilot Journeys actions

Autopilot Journeys gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Contact to List

Action

In Zapier“Adds a new contact and adds them to a list.”

Adds or updates a contact and places them in a list in the same step, which can start the journey tied to that list.

When to use it
enrolling every webinar registrant in the follow-up sequence the moment they sign up.
Watch out
both the Contact List and the email are required, so pick the list that starts the journey you want, not the one a trigger already watches.
2

Add Contact

Action

In Zapier“Adds a new contact.”

Creates a contact in Autopilot from data another app sent, or updates it when the email already exists there.

When to use it
syncing customers from your shop or CRM so Autopilot always has the latest details.
Watch out
Autopilot matches on email alone, so a typo in the address creates a second contact instead of updating the first.
3

Delete Contact

Action

In Zapier“Deletes an existing contact.”

Removes a contact from Autopilot entirely, finding them by email address.

When to use it
processing a data-erasure request logged in your support or privacy tool.
Watch out
any contact with that email is deleted, so test with your own address first.
4

Unsubscribe Contact

Action

In Zapier“Unsubscribes contact from all emails.”

Opts a contact out of all Autopilot emails, using their address to find them.

When to use it
honouring an unsubscribe that happened in another email tool or in your CRM.
Watch out
map the email from the trigger exactly; the opt-out applies to every email, not to a single list.
When it breaks

When an Autopilot Journeys Zap breaks

Zapier attaches no help article to Autopilot Journeys, so these are the general Zapier limits as they show up in contact syncs.

Contact syncs rarely crash loudly. They duplicate, loop or skip people quietly, and you usually notice in the task count or in a journey that sends twice.

  • Existing contacts are ignored

    A Zap only reacts to what happens after it is switched on. Contacts already in Autopilot or in your CRM stay where they are; moving them is a separate job.

  • The two-way sync loop

    Contact Added copying to a CRM, plus a second Zap pushing CRM contacts back with Add Contact, can bounce the same person back and forth and burn tasks.

  • Big imports get held back

    A large CSV import into Autopilot can fire a huge batch of Contact Added events at once, and Zapier's flood protection may hold it back.

  • Email is the only key

    Every action finds the contact by email. A different spelling of the same address means a new contact, or an unsubscribe that misses its target.
Need help

Need help automating Autopilot Journeys with Zapier?

A person reads every message.

FAQ

Autopilot Journeys Zapier integration: FAQ

01Is the Autopilot Journeys Zapier integration free?
Yes on the Zapier side: Autopilot Journeys is not reserved for paid plans, so you can connect it on the free plan. That plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps, one trigger and one action. Adding a filter, for example to keep only customers, or a second action requires a paid plan. A simple Contact Unsubscribes to CRM update fits within the free limits.
02How many tasks does an Autopilot Journeys Zap use?
One per action that succeeds, and none for the trigger. A Zap that fires on Contact Added and copies the contact into your CRM uses one task per new contact. If it also posts a message, that makes two. Failed actions are not counted. The surprise usually comes from imports: a large CSV loaded into Autopilot fires Contact Added for every row, and each run of the Zap consumes tasks.
03Is the Autopilot Journeys Zapier integration real time?
All four Autopilot Journeys triggers are instant: Autopilot tells Zapier as soon as a contact is added, joins or leaves a list, or unsubscribes, and the Zap starts at once. The polling grid of the plans, 15 minutes on the free plan, does not apply. The editor shows a lightning bolt next to the trigger to confirm it, and a free plan reacts just as quickly as a paid one here.
04What do you need to connect Autopilot Journeys to Zapier?
An Autopilot Journeys account and a Zapier account, plus the lists you plan to use already created in Autopilot. The connection is made once from the Apps page in Zapier: search for the app, sign in in the tab that opens and grant access. If a colleague owns some lists or contacts, you also need access to them, otherwise they will not show up when you set up a step.
05Why does Autopilot create duplicate contacts from a Zap?
Because email is the only thing Autopilot uses to recognise a person. If the address arriving from your form or CRM is spelt differently, with a typo or an alias, Autopilot sees a new contact and creates it. Clean the email in the source app before it reaches Add Contact or Add Contact to List. The same logic applies to Unsubscribe Contact and Delete Contact, which miss anyone whose address does not match exactly.
06What if the Autopilot Journeys operation you need is not there?
Then the integration does not offer it, and it will not appear under another name in the editor. The visible set is four triggers and four actions, all about contacts and lists. There is no search, no action to remove someone from a single list, and nothing on email activity. A workaround is to drive lists from your CRM. For anything beyond that, the flow needs a different tool or a custom build.
07Zapier, Make or n8n for Autopilot Journeys?
Pick on criteria rather than reputation. Zapier is the quickest way to sync contacts and unsubscribes, and its four instant triggers behave the same on every plan. Before choosing Make or n8n, check that their Autopilot Journeys integration covers the list and unsubscribe events your flow depends on, and who on your team will maintain it. Coverage and maintenance are better criteria than a ranking, because a contact sync runs every day once it is live.
Same platform

Other docs you might need on this stack.

Browse all integrations