Sender

Manage your Sender email and SMS marketing audience. Agents create and update subscribers, organize them into groups for segmentation, delete lapsed contacts, and review email and SMS campaign activity for reporting.

10 actions API key available

Sender website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A checkout completes in the store and a new customer record arrives

Get Subscriber looks the email up first, reading status, tags, and current group memberships

Create Subscriber adds the shopper with first name, last name, and custom fields like plan and city

Add Subscribers To Group places them in the Customers group, and Remove Subscribers From Group retires them from Prospects, so no one gets courted for a purchase they already made

The quarterly audience review pulls List Subscribers per group and cross-references the suppression list to draft a deletion batch

The marketing owner reads the batch, every email on it, and approves what is actually deleted versus what is merely removed from groups

Delete Subscribers executes the approved batch in a single call, and nothing outside it

The cleanup summary posts to the marketing channel with counts per category

What This Integration Enables

In Sender, the group is where targeting decisions actually live: campaigns aim at groups, so a segment that has drifted from reality mis-aims every send that touches it, across both email and SMS. FlowRunner agents treat group membership as a live property of the customer rather than a quarterly project, moving contacts in and out as the facts about them change in the store, the CRM, and the product. - Sync new signups and customers into Sender as subscribers, with names and custom fields mapped from the source - Look up any contact by email or ID to check status and memberships before acting - Move contacts between groups as they convert, upgrade, lapse, or opt into new topics - Keep custom fields current so campaign personalization draws on facts, not stale imports - Run audience cleanup as a disciplined pipeline: reversible removals freely, permanent deletions under review - Read campaign status and history for reporting across email and SMS

Without FlowRunner

Segments rot quietly The Prospects group still contains three years of customers, and every campaign to it says so

Two channels, two truths Email lives in one export and SMS consent in another, and nobody is sure which list is current

Cleanup is all-or-nothing Audience pruning means someone deletes a spreadsheet's worth of contacts and hopes the list was right

With FlowRunner

Groups track reality Signups, purchases, and plan changes move contacts between groups the moment they happen

One audience, kept current Contact fields and memberships update from the systems where changes originate, email and SMS alike

Deletion is a reviewed batch Reversible moves run freely; the permanent batch waits for a person to read the actual names

Use Case Scenarios

The segmentation that keeps up with the customer

A shopper's first order lands in [Shopify](/integrations/shopify). The agent checks Get Subscriber, creates the contact if new, writes the order category into a custom field, and swaps their memberships: into Customers, out of Prospects. When they later subscribe to the premium plan, Update Subscriber revises the plan field and Add Subscribers To Group adds them to the premium onboarding sequence's target group. Every campaign that fires afterward aims at who the customer is now.

The opt-in that files itself by interest

Signups arrive from [Typeform](/integrations/typeform) with a topic preference question. The agent calls Create Subscriber for each respondent and Add Subscribers To Group according to their answer: product updates, the newsletter, the SMS early-access list. When a topic needs a new segment, Create Group builds it on the spot and List Groups confirms the ID for the next batch. Preference data collected at signup actually governs what people receive, which is the whole reason anyone asks.

The audience review with evidence attached

Quarterly, the agent assembles the cleanup picture: List Subscribers across groups, the bounce and complaint log from [Google Sheets](/integrations/google-sheets), and List Campaigns for recent send context. It drafts two lists: contacts to remove from active groups but keep, and contacts to delete outright. The draft posts to [Slack](/integrations/slack) with counts and the full email lists attached. After approval, Remove Subscribers From Group and Delete Subscribers execute exactly the approved lists, and the summary is logged where the next review will find it.

Human-in-Loop Highlight

Delete Subscribers is a batch operation: one call, a list of emails, and every contact on it is permanently removed, not unsubscribed, removed, with their fields, tags, and membership history gone from the account. The API will erase three hundred contacts as readily as three, which is exactly why FlowRunner agents never assemble and execute a deletion batch in the same breath. The connector's own design offers the safer instrument for most cleanups, Remove Subscribers From Group leaves the contact intact, so the agent's standing rule is: removal from groups is automation, deletion is a proposal. The proposal arrives with the complete list, the reason each email is on it, and a count. A person approves the batch that runs. No approved list, no call.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

10 actions

Subscribers

List Subscribers Retrieves subscribers with pagination, optionally narrowed to a single group, returning email, name, status, and memberships. The audit read behind segmentation reviews and cleanup drafts.
Get Subscriber Retrieves one subscriber's full details by ID or email: contact fields, status, tags, and group memberships. The check-before-acting step in every sync.
Create Subscriber Adds a subscriber with email, optional names, group memberships by ID, and custom field values keyed by field name. The write that turns a signup into an audience member.
Update Subscriber Updates a subscriber by ID or email, changing only the fields provided: name, memberships, custom fields. The instrument that keeps personalization data true.
Delete Subscribers Permanently deletes one or more subscribers by email address in a single call, removing them entirely rather than unsubscribing them. The batch this page's human gate exists to review.

Groups

List Groups Retrieves the account's groups with ID, title, and subscriber counts. The lookup that turns segment names into the IDs other operations need.
Create Group Creates a new group with a given title and returns its ID. The step that gives a new campaign or topic its own target segment.
Add Subscribers To Group Adds existing subscribers to a group by email. The reversible segmentation move agents make freely as facts about contacts change.
Remove Subscribers From Group Removes subscribers from a group by email without deleting them, leaving other memberships intact. The safe instrument for most cleanup work.

Campaigns

List Campaigns Retrieves email and SMS campaigns with ID, title, status, type, and send details, paginated. The reporting read for campaign status and history.

Frequently Asked Questions

What can FlowRunner do with Sender?

FlowRunner agents can run List Subscribers, Get Subscriber, and Create Subscriber in Sender, plus 7 more actions.

Does connecting Sender to FlowRunner require OAuth?

No. Sender connects to FlowRunner with an API key, no OAuth flow required.

Can Sender trigger a FlowRunner workflow automatically?

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

Start building with Sender

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

Start Building Free Talk to us