Dynosend Zapier integrationAutomate Dynosend with Zapier.
The Dynosend Zapier integration gives you 1 trigger and 4 actions, with no search. Enough to react to every new contact in your audience, push events that start your journeys, and keep the blacklist in step with the rest of your tools.
Verified Trustpilot reviews · AI, automation & growth agency
What the Dynosend Zapier integration actually does
Dynosend is a customer engagement platform: contacts, audiences and multi-channel messages. Hooking it to Zapier means one thing in practice. Contacts and events stop being typed in by hand, and Dynosend reacts to what happens in your other tools, or tells them when someone new joins.
Three results you can build today. A synced audience: a signup somewhere else becomes a Dynosend contact through Create a Contact. A journey that starts on its own: Send an Event records something a contact did, like a demo booked or a first order, so your automations can pick it up. A clean blacklist: Blacklist a Contact stops messages to someone who asked out in another tool, and Delete a Contact removes a person from an audience.
Now the part the app page skips. There is a single trigger, New Contact, and Zapier polls it (more on that word below). There is no search step either, so a Zap cannot look up an existing Dynosend contact before acting: every action works from an email that an earlier step already carried. And nothing here reads back the events or messages Dynosend sent.
Figures on this page were read on 2026-10-01 from Zapier's listing, implementation App145870CLIAPI@1.0.1. If you would rather compare tools, the Dynosend Make integration covers the same app on Make.
Zapier vocabulary in one minute
Seven words, and the rest of the page reads easily.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it. Here, a new Dynosend contact.
- Action
- What the Zap does once started: the step that writes, sends or removes something for you, like creating a contact in Dynosend.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The number on your plan is a count of those.
- Polling vs instant
- Polling: Zapier checks the app on a timer and keeps what is new. Instant: the app calls Zapier the moment the event happens.
- Filter
- A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it otherwise.
- Connection
- Your Dynosend account linked to Zapier once, then reused by every step of every Zap that touches Dynosend.
What a Dynosend Zap really costs
The New Contact trigger costs nothing, however often Zapier checks. You pay per action that goes through: one task each time.
- TriggerFree, never counted
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, available on the free plan
So a Zap that creates a contact and then sends an event burns two tasks per run, and an action that fails is not counted. Dynosend is not a premium app (the kind Zapier keeps for paid plans), so it works on the free plan: 100 tasks a month, a check every 15 minutes, and Zaps of two steps only. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. Practical rule: start with New Contact and one action on Free, and only move up when the scenario really needs a condition.
Connect Dynosend to Zapier in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Dynosend account first, plus access to any audience you do not own yourself and want the Zap to touch.
- 02
Pick Dynosend
Type Dynosend in the search box of the dialog, select it, then click Add connection. A new tab opens on the Dynosend side so you can finish the sign-in there and come back to Zapier.
- 03
Sign in and grant access
Log in to Dynosend in that tab and allow Zapier to reach the account. From then on, every Zap that uses Dynosend picks this connection instead of asking again.
Your first Zap: brief the journey for real signups only
GoalEvery new contact that is not one of your own test addresses gets a signup event, so the welcome journey in Dynosend starts by itself.
- 01
Build: pick the trigger
Start a new Zap, choose Dynosend as the app and New Contact as the event that starts it, then select the Dynosend connection you made above.
- 02
Test the trigger
Run the test: Zapier brings back the three most recent contacts of the account. Pick a real one, you map the next steps from it.
- 03
Add the filter
From the plus icon, add a Filter. Pick the contact email, the text rule that says it does not contain, then your own domain.
- 04
Add Send an Event
Choose Dynosend again and Send an Event. Map the contact email from the trigger and type the event name your journey listens for.
- 05
Test, then Publish
Test the action once and check the event landed on the right contact in Dynosend. Then click Publish to switch the Zap on.
The Dynosend trigger
1 event starts a Zap when something happens in Dynosend. Zapier checks for them at the interval your plan allows.
New Contact
Polling triggerIn Zapier“Triggers when a new contact is added to your audience.”
Starts the Zap each time a contact joins your Dynosend audience, however it got there. Each contact comes through once, so it suits anything that should happen a single time per person.
Dynosend actions
Dynosend gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Blacklist a Contact
ActionIn Zapier“Add a contact to the blacklist”
Puts a contact on the Dynosend blacklist from just their email, the move to make when someone must stop hearing from you.
Create a Contact
ActionIn Zapier“Add a contact to an audience”
Adds a person to one of your Dynosend audiences from data that came in elsewhere. The email address is the only field the action insists on.
Send an Event
ActionIn Zapier“Perform an event for a specific contact”
Records that a given contact did something, under the event name you choose, so Dynosend can react to it. It needs the contact email and the event name.
Delete a Contact
ActionIn Zapier“Delete a contact from an audience”
Takes a contact out of an audience, identified by email. Unlike the blacklist, the person is no longer in that audience at all.
When a Dynosend Zap breaks
Zapier attaches no help article to Dynosend, so what follows comes from the way Zapier works for every app.
Most surprises come from the trigger side: what it sees, what it skips, and what it sees twice. If a Zap stops for a reason you cannot spot, our Zapier troubleshooting guide is the next stop.
Old contacts are never picked up
A Zap only reacts to contacts added after you publish it. The audience you already had stays where it is: moving that backlog is a separate job.The Zap that feeds itself
New Contact plus Create a Contact on the same audience: every contact the Zap creates triggers it again, and your task count drains fast.A bulk import gets held back
Import thousands of contacts at once and the trigger returns a huge batch. Zapier's flood protection can hold it back instead of running it all.The same contact twice? No
Zapier remembers which contacts it has already seen on a polling trigger, so one person does not start the Zap twice.
Need help automating Dynosend with Zapier?
A person reads every message.
