Emma
Email MarketingManage your Emma by Marigold email audience from a flow. Agents add and look up members by email, segment them into groups ahead of a send, opt contacts out to honor unsubscribes, and read mailings and custom field definitions for reporting and data mapping.
What This Integration Enables
Emma by Marigold is an audience system: members, custom fields, groups, mailings. The mailing is the visible part, but everything that makes a mailing land is upstream of it, and that upstream work is exactly what leaks when it depends on imports and memory. FlowRunner agents do the upstream work continuously: they upsert members from the systems where customers actually appear, map data into the account's own field definitions, and file members into the groups a campaign will target. - Sync contacts from a store, CRM, or form tool into Emma as members, updating existing records by email rather than duplicating them - Segment audiences by adding members to targeted groups before a campaign, not during it - Honor unsubscribe and compliance requests with a reviewed, [human-in-the-loop](/concepts/human-in-the-loop) opt-out step - Look up any member by email or ID to verify status before acting on them - Export members and review mailings and field definitions for reporting and data mapping
Without FlowRunner
With FlowRunner
Use Case Scenarios
Every new shopper joins the audience with their fields intact
A new customer fires from [Shopify](/integrations/shopify). The agent calls List Fields once at setup to learn the account's shortcut names, then Add Member to upsert the shopper with name, city, and first purchase date mapped to those fields. Because Add Member updates by email instead of duplicating, a repeat buyer refreshes their record rather than splitting it. Add Members To Group places new customers into the welcome-series group the same hour they buy.
Form signups become a segmented audience, not a pile
Newsletter signups collect in [Typeform](/integrations/typeform). On a schedule, the agent pulls new responses, calls Add Member for each respondent, and uses Add Members To Group to route them by the interest they selected: product updates to one group, events to another. The next mailing targets people who asked for exactly that content, and no one hand-sorted a spreadsheet to make it true.
The unsubscribe queue with an approver
Opt-out requests arrive through the helpdesk and reply-to inbox. The agent resolves each one with Get Member By Email, assembles the evidence, the request text, the matched member, their current status, and posts the queue to [Slack](/integrations/slack). The marketer confirms each match, the agent calls Opt Out Member for the approved ones, and a weekly List Members export to [Google Sheets](/integrations/google-sheets) gives compliance a standing record that requests were honored.
Human-in-Loop Highlight
Opt Out Member is one-way. It sets the member's status to opt-out across the entire account, and the API cannot reverse it: only the member themselves can re-subscribe. Aim it at the wrong record in a dedup-prone audience and you have silently removed a willing subscriber who will never know to come back. So the agent never opts anyone out on its own judgment. It matches the request to a member, shows the marketer the request text and the matched record side by side, and waits. The matching runs at machine speed. The irreversible status change belongs to a person.
Agent Capabilities
9 actionsMembers
5- List Members Retrieves members in the Emma account with pagination. Use Start and Count to page through large audiences; each page returns member records with email, status, and custom field values. Optionally includes deleted members.
- Get Member Retrieves a single member by their numeric Emma member ID, including email address, status, and all custom field values.
- Get Member By Email Retrieves a single member by email address, including status and all custom field values. The resolution step when you know the contact but not their Emma ID.
- Add Member Adds a new member or updates an existing one by email address. Provide custom field values and the group IDs the member should join. An existing email is updated, never duplicated, which makes this the default write for sync workflows.
- Opt Out Member Opts a member out of all mailings by their numeric member ID. Cannot be undone through the API; the member must re-subscribe themselves. The operation this page's human gate exists for.
Groups
2- List Groups Retrieves the member groups in the Emma account, including each group's ID, name, and type. The map of how the audience is segmented.
- Add Members To Group Adds one or more existing members to a group by their numeric member IDs. Members must already exist; create them with Add Member first. The step that builds a campaign's target segment.
Mailings
1- List Mailings Retrieves mailings in the account with pagination, including each mailing's ID, name, subject, and send status. Used to review sent, scheduled, and draft campaigns and to connect segments to the sends they feed.
Fields
1- List Fields Retrieves the custom fields defined in the account, including each field's ID, display name, shortcut name, and data type. The schema lookup that keeps Add Member writes mapped to real fields.
Frequently Asked Questions
What can FlowRunner do with Emma?
FlowRunner agents can run List Members, Get Member, and Get Member By Email in Emma, plus 6 more actions.
Does connecting Emma to FlowRunner require OAuth?
No. Emma connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Emma trigger a FlowRunner workflow automatically?
Emma doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Emma
$100 in credits. No card required. Connect in minutes.