SendFox
Email MarketingKeep your SendFox creator audience in sync. Agents create contacts, build and organize lists, unsubscribe opt-outs by email, and page through subscribers and sent campaigns for reporting.
What This Integration Enables
SendFox keeps its API surface small on purpose: contacts, lists, opt-outs, and read-only campaign history. That restraint fits how creator audiences actually break, which is rarely inside the email tool and almost always at the edges, where signups from the store, the form, and the community never make it into the list. FlowRunner agents own those edges. They upsert every signup by email so the audience stays deduplicated, build lists to match campaigns instead of forcing campaigns onto stale lists, and page the full subscriber and campaign history out for reporting. - Sync customers and leads from storefronts, forms, and CRMs into the audience as contacts, subscribed to the right list on arrival - Spin up a new list per launch or lead magnet with Create List, so segmentation reflects what people actually signed up for - Check unsubscribed_at before any re-add, so past opt-outs are surfaced to a person instead of overwritten - Export subscribers and sent campaigns on a schedule for growth reporting - Route every [human-in-the-loop](/concepts/human-in-the-loop) decision, especially suppression, to the person who owns the list
Without FlowRunner
With FlowRunner
Use Case Scenarios
The store feeds the newsletter without anyone copying emails
Each evening, an agent picks up the day's new customers from [Shopify](/integrations/shopify), resolves the welcome list with List Lists, and calls Create Contact for each shopper with their email and name. Because SendFox treats create as an upsert matched on email, a repeat buyer refreshes their existing record instead of becoming a duplicate. Shoppers whose lookup shows a past opt-out are held and flagged rather than re-subscribed. The audience grows with the store, and nobody exports a CSV.
A list per lead magnet, built the moment the campaign ships
A new guide goes live behind a [Typeform](/integrations/typeform). The agent calls Create List with the campaign's name, then subscribes each respondent with Create Contact and the new list's ID as responses arrive. When the follow-up sequence ends, List Contacts scoped by that list membership feeds the results into [Google Sheets](/integrations/google-sheets): who signed up, when, and who has since unsubscribed. Segmentation stays honest because every list maps to a real thing people asked for.
Opt-outs from every channel, honored through one gate
Unsubscribe requests do not all arrive through the unsubscribe link. They show up in support tickets, replies, and social DMs. An agent collects them from the helpdesk, matches each against the audience with List Contacts, and assembles the day's suppression batch with names, sources, and matched emails. The list owner reviews the batch once, corrects any mismatched address, and approves. Only then does the agent call Unsubscribe Contact for each confirmed address and log the batch to [Google Sheets](/integrations/google-sheets) as the compliance record.
Human-in-Loop Highlight
Unsubscribe Contact is quiet, permanent in practice, and aimed at the asset the whole operation runs on. It marks a subscriber as unsubscribed from all mailings, and while the record survives, the relationship does not: re-adding someone who was suppressed by mistake means asking for consent you already had. A fuzzy match is all it takes, a support ticket from j.smith@ matched to jsmith@, and a paying reader silently stops hearing from you. So FlowRunner agents never suppress on their own judgment. The agent posts: "Seven opt-out requests today. Six matched exactly. One fuzzy: ticket from 'Jon at Acme' matched to [email protected] with 84 percent confidence. Approve all seven, or hold the fuzzy match?" The list owner decides, the agent executes, and the audience shrinks only by the people who actually asked to leave.
Agent Capabilities
8 actionsContacts
4- List Contacts Retrieves a paginated list of subscribers with email, name, subscription status, and list membership. The lookup step behind dedup checks, opt-out matching, and audience exports.
- Get Contact Retrieves a single contact by numeric ID, including custom fields, unsubscribed_at, and the lists they belong to. Used to gather full context before a re-add decision or a report.
- Create Contact Creates a subscriber or updates an existing one matched by email, optionally subscribing them to one or more lists. The default write for every sync workflow, because the upsert cannot create a duplicate.
- Unsubscribe Contact Marks a contact as unsubscribed from all mailings by email address without deleting the record. The suppression step this page's human gate exists for.
Lists
3- List Lists Retrieves the audience lists in the account with ID, name, and creation date. The resolution step before any subscribe.
- Get List Retrieves a single list's details by numeric ID. Used to verify a target list before a batch subscribe.
- Create List Creates a new audience list with a given name and returns its ID. The step that gives every launch and lead magnet its own segment from day one.
Campaigns
1- List Campaigns Retrieves sent email campaigns with subject, status, and timestamps. Campaigns are read-only through the API, which makes this the reporting feed for send-history digests.
Frequently Asked Questions
What can FlowRunner do with SendFox?
FlowRunner agents can run List Contacts, Get Contact, and Create Contact in SendFox, plus 5 more actions.
Does connecting SendFox to FlowRunner require OAuth?
No. SendFox connects to FlowRunner with an API key, no OAuth flow required.
Can SendFox trigger a FlowRunner workflow automatically?
SendFox doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with SendFox
$100 in credits. No card required. Connect in minutes.