FlowRunner
PricingContact
Theme
Start Free

Dotdigital

Email Marketing

Connect AI agents to Dotdigital marketing automation. Agents create and update contacts with custom data fields, add them to address books, and browse and send email campaigns scoped to your account's hosting region.

9 actions Basic auth available
Dotdigital website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
A new order arrives from the storefront, or a signup lands from the website form
Create or Update Contact upserts the buyer by email, writing order value, product line, and region into custom data fields
Add Contact To Address Book places the contact on the post-purchase nurture list
Get Contact By Email confirms the contact's opt-in type and status before any send is considered
List Campaigns pulls the prepared campaigns that match the contact's nurture stage
The lifecycle marketer reviews the proposed campaign and recipient set before anything leaves the account
Send Campaign delivers the approved campaign to the confirmed contact IDs
A summary posts to the team channel with the send count and the segment definition used

What This Integration Enables

Dotdigital's campaigns are only as sharp as the contact data fields behind them, and those fields describe events that happen everywhere except Dotdigital: in the store, the CRM, the billing system, the signup form. That gap is the actual job. FlowRunner agents close it by upserting contacts with fresh data fields the moment the source event fires, filing them into the right address books, and resolving opt-in status before a send is ever staged. - Sync contacts from a CRM, storefront, or spreadsheet and keep their custom data fields current - File new signups and customers into the correct address book as they arrive, not at month end - Resolve any contact by email to check opt-in type and status before acting on them - Stage a prepared campaign against an exact recipient set and hold it for [human-in-the-loop](/concepts/human-in-the-loop) approval - Audit address books and campaigns on a schedule by exporting them for review

Without FlowRunner

Segments built by export Someone pulls a CSV from the store, edits it in a spreadsheet, and re-imports it into Dotdigital days after the behavior it describes
Data fields that rot Custom data fields were filled once at import and never again, so the segmentation logic runs on stale facts

With FlowRunner

Contacts upserted at the source event The moment an order, signup, or CRM change happens, the contact and its data fields are refreshed by email match, never duplicated
Address books that fill themselves New customers land on the right list as they arrive, with the data fields the nurture program keys on already set
Sends gated by a person Agents resolve recipients and stage the campaign, and a marketer approves the send before it reaches an inbox

Use Case Scenarios

Post-purchase nurture that starts at the order, not the import

An order fires from [Shopify](/integrations/shopify). The agent calls Create or Update Contact to upsert the buyer by email, writing order total and product category into custom data fields, then Add Contact To Address Book to place them on the post-purchase list. The nurture program Dotdigital runs from that list now keys on data that is hours old instead of weeks old, and no one exported anything.

The subscriber sync that logs its own receipts

A marketing ops manager keeps the master subscriber list in [Google Sheets](/integrations/google-sheets). On a schedule, the agent reads the rows, calls Create or Update Contact for each one so existing contacts are refreshed rather than duplicated, and writes the outcome of every upsert back to the sheet. When a row fails, the agent flags it for a person instead of silently skipping it. The sheet stops being a hopeful intention and becomes a reconciled record.

A targeted send with a named approver

A win-back campaign is prepared in Dotdigital. The agent assembles the recipient set by calling Get Contact By Email for each lapsed customer surfaced by the CRM, filters out anyone whose status or opt-in type disqualifies them, and posts the campaign subject, the recipient count, and a sample of the list to [Slack](/integrations/slack). The marketer approves. Only then does Send Campaign fire, and the confirmation lands back in the channel.

Human-in-Loop Highlight

Send Campaign delivers immediately to the contact IDs it is given. There is no scheduled window to cancel and no unsend: a mis-targeted campaign reaches real inboxes, burns sender reputation, and harvests unsubscribes from people who should never have received it. So in every FlowRunner workflow on this page, the agent does the resolving, filtering, and staging, then presents the campaign name, recipient count, and sample contacts to a marketer. The send happens at machine speed, but only after a person has said this campaign, to these people, now.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

9 actions

Contacts

5
  • List Contacts Retrieves contacts from the account address book, ordered by contact ID. Use Select to control the page size (up to 1000) and Skip to page through results. Returns each contact's ID, email, opt-in type, email type, status, and custom data fields.
  • Get Contact Retrieves a single contact by its numeric contact ID. Returns the contact's email, opt-in type, email type, status, and custom data fields.
  • Get Contact By Email Retrieves a single contact by email address. Dotdigital resolves the email against the account and returns the contact's ID, opt-in type, email type, status, and custom data fields. The resolution step before Update Contact or Send Campaign.
  • Create or Update Contact Creates a new contact or updates the existing one matched by email address. Set custom data fields as key/value pairs, plus opt-in type and email format. The default write for sync workflows, because it cannot create a duplicate.
  • Update Contact Updates an existing contact identified by its numeric contact ID, replacing the supplied fields including email, custom data fields, opt-in type, and email format.

Address Books

2
  • List Address Books Retrieves the account's address books, ordered by ID, with each book's name, visibility, and contact count. The audit step that shows where the lists actually stand.
  • Add Contact To Address Book Adds a contact to a specific address book by email address, creating the contact if it does not already exist. The step that files a new customer into the nurture program.

Campaigns

2
  • List Campaigns Retrieves the account's email campaigns with each campaign's ID, name, subject, and status. Used to match a prepared campaign to a workflow before staging a send.
  • Send Campaign Sends an existing, prepared campaign immediately to a specific set of contacts identified by their numeric contact IDs. The operation this page's human gate exists for.

Frequently Asked Questions

What can FlowRunner do with Dotdigital?

FlowRunner agents can run List Contacts, Get Contact, and Get Contact By Email in Dotdigital, plus 6 more actions.

Does connecting Dotdigital to FlowRunner require OAuth?

No. Dotdigital connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Dotdigital trigger a FlowRunner workflow automatically?

Dotdigital doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Dotdigital

$100 in credits. No card required. Connect in minutes.