Launch Front Chat
Skip to content

Zapier Integration

This guide explains how to connect Sender to Zapier so you can automate workflows between Sender and thousands of other apps — such as syncing new subscribers, triggering actions when campaigns are created, or adding contacts from external tools.

Prerequisites

  • An active Sender account
  • A Zapier account (free or paid plan)
  • An API access token from Sender (generated in Account settings → API access tokens)
  • A Zap idea in mind — knowing which trigger and action you want to automate

Where to Find This Setting

The Sender side of the connection is managed through your API access token. To find it, go to Account settings → API access tokens in your Sender dashboard. Click Create API token if you don't have one yet, then copy the token value.

The Zapier side of the connection is managed entirely within Zapier. You configure the integration when creating or editing a Zap in the Zap editor at https://zapier.com. You can also manage existing connections from the Apps page under My Apps in your Zapier dashboard.

Note: The Zapier interface may change over time. Steps and menu labels described below reflect the current layout but may vary slightly.

Steps to Connect Sender to Zapier

Step 1 — Generate an API Access Token in Sender

In your Sender dashboard, navigate to Account settings → API access tokens. Click Create API token. Give your token a descriptive name (e.g., Zapier integration) so you can identify it later. Once the token is created, copy it and store it securely. You will paste this token into Zapier during the authentication step.

Step 2 — Create a Zap and Authenticate Sender

Log in to your Zapier account and click Create → Zaps (or + Create depending on your interface). In the Zap editor, choose whether Sender will serve as the trigger app or the action app. Search for and select Sender. When prompted to connect your Sender account, click Sign in and paste your API access token into the authentication field. Click Yes, Continue to confirm the connection.

Step 3 — Configure the Trigger and Action

Select the specific trigger event or action event you want to use. If Sender is your trigger, choose an event such as New Subscriber or New Campaign. If Sender is your action, choose an event such as Add / Update Subscriber or Add Subscriber to Group. Configure any required fields — such as selecting a subscriber group — then click Continue. Test the step to confirm data is flowing correctly, then publish your Zap by toggling it on.

How to Verify the Integration

After publishing your Zap, trigger the event manually to confirm data flows as expected. For example, if your trigger is New Subscriber, add a test subscriber in Sender and check that the action fires in the connected app. In Sender, go to Subscribers to verify that any new contacts pushed by a Zap action appear in the correct subscriber group. In Zapier, check the Zap History page to confirm the Zap ran successfully without errors.

What Syncs Between Platforms

Subscriber data (Sender → Zapier) — When a trigger event occurs in Sender (such as a new subscriber being added, updated, or unsubscribed), Zapier receives the subscriber's details in real time. All Sender triggers are instant, meaning data is sent to Zapier immediately when the event happens.

Subscriber data (Zapier → Sender) — When a Zap action pushes data into Sender, it can create or update subscribers, add or remove subscribers from groups, or unsubscribe email addresses. Data is sent to Sender as soon as the Zap's trigger fires.

Campaign data (bidirectional) — Sender can trigger a Zap when a new campaign is created. In the other direction, Zapier can create a draft campaign or send an existing draft campaign in Sender.

Integration Tips

Use descriptive token names — When creating your API access token in Sender, name it something identifiable like Zapier integration so you can easily manage or revoke it later without affecting other integrations.

Test before publishing — Always use Zapier's built-in test feature for each step before turning on your Zap. This confirms that authentication works and data maps correctly between platforms.

Use filters and formatting in Zapier — Add Zapier filter or formatter steps between your trigger and action to control which data flows into Sender. For example, filter out subscribers from a specific domain or format phone numbers before syncing.

Monitor Zap History — Regularly check the Zap History page in Zapier to catch errors early. Failed Zap runs typically indicate expired tokens, missing required fields, or changed configurations.

One token per integration — Consider creating a separate API access token for each third-party integration. This way, revoking one token does not break other connected services.

Common Issues

Sender account fails to authenticate in Zapier → The API access token may be incorrect or contain extra spaces. Go to Account settings → API access tokens in Sender, create a new token, and paste it carefully into Zapier without any leading or trailing spaces.

Zap runs but no data appears in Sender → The action step may be misconfigured. Open the Zap in the Zap editor, verify that required fields (such as email address and subscriber group) are correctly mapped, and re-test the step.

Trigger not firing for new events → All Sender triggers are instant and rely on webhooks. If triggers stop working, go to My Apps in Zapier, find the Sender connection, and click Reconnect to re-establish the webhook connection.

Duplicate subscribers appearing in Sender → Use the Add / Update Subscriber action instead of creating a new subscriber each time. This action checks for an existing email address and updates the record rather than creating a duplicate.

Zap turns off automatically → Zapier disables Zaps after repeated errors. Check the Zap History for error details, fix the underlying issue (expired token, deleted group, etc.), and turn the Zap back on.

FAQs

Where do I find my Sender API access token?

Go to Account settings → API access tokens in the Sender dashboard. Click Create API token if you don't have one yet. Copy the token and paste it into the Zapier authentication field when connecting your Sender account.

What triggers and actions does Sender support in Zapier?

Sender supports seven instant triggers: New Campaign, New Subscriber, New Group, New Subscriber in Group, New Unsubscriber, New Unsubscriber From Group, and Updated Subscriber. It also supports seven actions: Add / Update Subscriber, Add Subscriber to Group, Remove Subscriber From Group, Create Campaign, Send Campaign, Send Transactional Campaign, and Unsubscribe Email.

Does the integration sync existing subscribers or only new ones?

Sender triggers in Zapier only fire for new events going forward — they do not sync historical data. To bring existing subscribers into a Zap workflow, use a Zapier action triggered by another app (such as a spreadsheet) to push contacts into Sender.

Can I connect Sender to multiple apps through Zapier at the same time?

Yes. Each Zap operates independently. You can create multiple Zaps that connect Sender to different apps simultaneously without conflicts.

What happens if I revoke my API access token in Sender?

Any Zapier Zaps authenticated with that token will stop working. You will need to create a new token in Account settings → API access tokens and reconnect your Sender account in Zapier using the new token.

Are Sender triggers in Zapier instant or polling-based?

All Sender triggers in Zapier are instant. They use webhooks to send data to Zapier the moment the event occurs in Sender, with no polling delay.