Dynosend
Email MarketingDynosend is an email marketing and transactional messaging platform. Agents manage audiences, contacts, and events, start and resume broadcast campaigns, send transactional messages, and maintain the account blocklist.
What This Integration Enables
Dynosend models an audience as a self contained list with its own custom fields, its own contacts and its own subscription state. That is not a filing detail. It means consent is recorded per audience, the same person can be subscribed in one and unsubscribed in another, and the platform is perfectly happy with that. Find Duplicate Contacts exists precisely because it happens, and it is the only route that looks past a single audience.
FlowRunner agents work with that grain rather than against it. They read audience definitions and field tags before writing, add contacts and tags without clearing what is already stored, feed product events in so Dynosend's own automations can react, fire transactional messages, and start, pause and resume broadcasts. Where the platform draws a distinction that matters, between unsubscribing from one audience and blocking an address across the account, the agent respects it and escalates the cases where the right answer is not written anywhere in the data. That is the human-in-the-loop discipline applied to consent, which is the part of lifecycle marketing least suited to being guessed.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Product behavior feeding lifecycle mail
An upgrade, a first successful import or a churn signal reaches the agent from the product or from Stripe. Send Event records it against the contact under a name Dynosend accepts, and the automations already built in the platform take it from there. The agent then calls Tag Contact to add the plan tag, deliberately choosing the additive operation because Update Contact's tag parameter replaces the whole set and would quietly empty every segment built on the others. Get Audience supplies the field tags first, since custom values are written under those tags rather than under a nested object.
-
A broadcast with a working stop button
A campaign is prepared in Dynosend and the agent is asked to release it once a set of upstream checks pass. List Campaigns confirms which record is the right one, Get Campaign reads its configuration, and Start Campaign sends it. There is no confirmation step and no undo, which is exactly why the agent watches what happens next: a spike in the reported spam and bounce figures triggers Pause Campaign, and the remaining recipients wait. Messages already delivered stay delivered. When the owner clears it, Resume Campaign picks up the rest. Reported rates arrive as fractions, so the agent converts before anything reaches a dashboard in Google Sheets.
-
An erasure request handled as an erasure
A request arrives through Zendesk. The agent uses Find Duplicate Contacts to locate every audience holding the address, then applies what the requester actually asked for. Delete Contact removes the record, which is the right call for an erasure but records no opt out, so an address deleted this way can be added again by any later import and will receive mail. Where the request was to stop mail rather than to erase data, the agent calls Unsubscribe Contact per audience or Add To Blocklist for the whole account, and Check Blocklist afterwards to confirm the state and record the reason. The ticket closes with a note naming the operation used.
Human-in-Loop Highlight
Find Duplicate Contacts routinely turns up the contradiction Dynosend's model permits: the same person unsubscribed in one audience and still subscribed in another. Both ways of tidying that up are wrong without a person. Subscribe Contact everywhere overrides a recorded opt out; Unsubscribe Contact everywhere silently removes someone who deliberately joined a list they still want. Nothing in the API says which the person meant, because the platform recorded two separate choices and both are real. So before a cross audience send, the agent gathers the evidence and stops: "This address is unsubscribed from Product Updates and subscribed to Billing Notices, with the opt out recorded more recently. Treat the opt out as global, leave the two audiences as they are, or move the address to the blocklist?" A named owner answers, the agent applies it consistently across every audience, and the decision is recorded against the contact. The agent did the discovery work no person would do by hand. It did not resolve a consent conflict by picking whichever answer was easier to write.
Agent Capabilities
20 actionsAudiences
2- List Audiences Lists the account's audiences with their names, default sender details and identifiers. Almost every other operation needs an audience, so this is the first call in most flows.
- Get Audience Reads one audience with its custom field definitions, the contact details shown in the footer of its emails, and its subscribe and unsubscribe statistics. The field tags returned here are what the contact write operations expect.
Contacts
9- List Contacts Reads a page of an audience's contacts, each with its status, source, tags and custom field values.
- Get Contact Reads one contact from an audience by its identifier, or by email address when the identifier is not held.
- Find Duplicate Contacts Finds every contact holding an address across all audiences, with the status in each. The only route that looks past a single audience, and the one that surfaces a consent state that disagrees with itself.
- Create Contact Adds a contact to an audience. An existing address is an error rather than an update, and the resulting status depends on the audience's double opt in setting.
- Update Contact Changes a contact's address, tags or custom field values. Tags here replace every existing tag rather than adding to them, so this is the deliberate choice rather than the default one.
- Tag Contact Adds tags to a contact, leaving the existing ones in place. The additive counterpart to Update Contact.
- Subscribe Contact Sets a contact's status to subscribed so they receive future messages from that audience.
- Unsubscribe Contact Sets a contact's status to unsubscribed for that audience only. The same address can stay subscribed elsewhere, which is why the cross audience view matters before this is used as a blanket opt out.
- Delete Contact Permanently removes a contact from an audience, which is the operation for an erasure request. No opt out is recorded, so an address removed this way can be added again by a later import.
Events
1- Send Event Records that a contact did something in your own application, which is what the platform's automations listen for. Event names are restricted to letters, numbers and underscores.
Campaigns
5- List Campaigns Lists broadcast campaigns with their subject, sender details, status and delivery time.
- Get Campaign Reads one campaign with its insights: recipients, delivery, opens, clicks, spam reports, bounces and unsubscribes, each as a count and a rate. The rates arrive as fractions.
- Start Campaign Sends a prepared broadcast to its audience. There is no confirmation step and no undo, which is why a flow that calls it should already know what it is releasing.
- Pause Campaign Stops a campaign that is currently sending. Messages already delivered stay delivered.
- Resume Campaign Restarts a paused campaign, resuming the send to the recipients it had not reached yet.
Transactional and Blocklist
3- Send Transactional Message Sends a configured transactional message to one recipient. If no contact holds that address, one is created, and the parameters accepted depend on whether the message is configured as internal or external in the platform.
- Check Blocklist Reports whether an address is on the account blocklist, when it was added and why. The reason distinguishes a platform block after bounces from a person who opted out.
- Add To Blocklist Blocks an address across the whole account, which is stronger than unsubscribing it from one audience and is the right operation when the request was to stop all mail.
Frequently Asked Questions
What can FlowRunner do with Dynosend?
FlowRunner agents can run List Audiences, Get Audience, and List Contacts in Dynosend, plus 17 more actions.
Does connecting Dynosend to FlowRunner require OAuth?
No. Dynosend connects to FlowRunner with an API key, no OAuth flow required.
Can Dynosend trigger a FlowRunner workflow automatically?
Dynosend doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Email Marketing integrations
Start building with Dynosend
Free plan, no card required. Connect in minutes.