Moosend

Keep Moosend email marketing lists in sync from your flows: agents subscribe, look up, unsubscribe, and remove members with custom fields, discover lists with member counts, and review campaign send history for reporting.

7 actions API key available

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

A new customer or newsletter signup arrives from the storefront or a form

Get Lists resolves the destination list for this signup source

Get Subscriber checks whether the email already exists on the list and in what status

Subscribe adds the new member with display name and custom fields, or refreshes the existing record

The marketing channel gets a daily digest of additions by source

A separate event, an opt-out or a bounce handled elsewhere, reaches the flow

Unsubscribe marks the member unsubscribed while keeping the record on the list

Any request to permanently remove a member, which erases their history from the list, waits for a person

What This Integration Enables

Moosend keeps email marketing simple: lists, subscribers, campaigns, without an object model to fight. The work that actually determines results happens at the edges of that simplicity, feeding the lists from every place customers appear, and honoring every opt-out no matter where it was expressed. FlowRunner agents own both edges. They subscribe, look up, unsubscribe, and remove members with custom fields intact, discover lists with live member counts, and pull campaign history out for reporting. - Sync signups, customers, and form respondents into lists with display names and custom fields - Keep membership current by unsubscribing or removing members in response to events elsewhere - Look up a subscriber's status and field values before an automation decides its next step - Discover lists and member counts to drive routing and reporting - Archive campaign send history and delivery stats to spreadsheets and chat The API draws a sharp line between marking someone unsubscribed and erasing them entirely, and FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) discipline keeps agents on the right side of it. Custom fields carry the segmentation weight in Moosend, and they are strict: field names supplied on Subscribe must match the list's own definitions. FlowRunner agents read those definitions through Get List Details before writing, so a renamed field in the Moosend dashboard shows up as a flagged mismatch in the flow rather than as months of silently unrecorded data. The list's schema stays the single source of truth, and the agents conform to it instead of fighting it.

Without FlowRunner

Signups reach the list in batches Customers and respondents pile up in other tools until someone runs the import, days after the interest peaked

Opt-outs propagate unevenly A customer unsubscribes in one place and keeps getting campaigns because the list never heard about it

Campaign stats stay in the dashboard Send history and delivery numbers live in Moosend, visible only to whoever logs in to look

With FlowRunner

Every source subscribes in real time Stores and forms add members with names and custom fields the moment the signup happens

Suppression is synchronized Opt-out events anywhere mark the member unsubscribed on the right lists within minutes, with the record preserved

Delivery recaps come to the team Agents pull campaign history on a schedule and post the numbers where the team already works

Use Case Scenarios

Shoppers join the list with their history attached

A new order fires in [Shopify](/integrations/shopify). The agent resolves the marketing list, checks Get Subscriber for an existing record, and calls Subscribe with the shopper's name and order details in custom fields matching the list's field definitions. Buyers enter segmented and current, and the same call safely refreshes members who already existed instead of erroring or duplicating.

The opt-out that actually propagates

A customer unsubscribes through a preference page, or a support agent records a do-not-email request in the helpdesk. The event reaches the agent, which finds every list carrying that address via Get Lists and Get Subscriber, and calls Unsubscribe on each. The member stays on the lists as a suppression record, exactly what you want, and the flow logs when and why each opt-out was honored. Deliberately not Remove Subscriber: the difference is the compliance trail.

Friday's send recap without Friday's dashboard tour

On a schedule, the agent pages through List Campaigns, collects each campaign's subject, status, and delivery stats, archives them to [Google Sheets](/integrations/google-sheets), and posts a recap to [Slack](/integrations/slack) with the outliers flagged: the send whose delivery rate dipped, the campaign still sitting in draft. List health rides along via Get List Details, active, unsubscribed, and bounced counts per list, so shrinking lists get noticed while the trend is young.

Human-in-Loop Highlight

Remove Subscriber and Unsubscribe look like siblings and are opposites. Unsubscribe preserves the member as a suppression record: the list remembers this person opted out and keeps protecting them. Remove Subscriber deletes the member from the list entirely, and with the record goes the memory, so the next enthusiastic CSV import or storefront sync can re-add the same address as a fresh subscriber and start mailing someone who explicitly said stop. That is how a clean-looking list becomes a compliance incident with an audit trail that proves you once knew better. So FlowRunner agents default every opt-out to Unsubscribe, and Remove Subscriber sits behind a gate reserved for the cases that genuinely require erasure, a data-deletion request, a confirmed spam trap. The agent resolves the ID via Get Subscriber, presents the member's status and history, and states what will be lost: "Removing erases this member's unsubscribe record from Newsletter. If they are re-imported, they will be mailed again. Confirm removal?" A person confirms, and the deletion is logged with its reason.

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

7 actions

Lists

Get Lists Retrieves all mailing lists with IDs, names, and status. The routing step that picks a destination list per source.
Get List Details Retrieves one list's custom field definitions and member counts, optionally broken down by active, unsubscribed, bounced, and removed status. The health check behind list reporting.

Subscribers

Subscribe Adds a member to a list or updates the existing record for that email, with display name, custom fields, and optional double opt-in confirmation. The intake write for every signup source.
Unsubscribe Marks a member unsubscribed while keeping them on the list as a suppression record. The default opt-out write in every FlowRunner flow.
Get Subscriber Retrieves a member by email with ID, status, custom field values, and timestamps. The lookup that resolves emails to subscriber IDs and checks status before any decision.
Remove Subscriber Permanently deletes a member from a list by subscriber ID, erasing their record entirely. The operation this page's human gate exists for.

Campaigns

List Campaigns Retrieves campaigns with ID, name, subject, status, delivery stats, and timestamps, with pagination for large histories. The reporting read behind send recaps.

Frequently Asked Questions

What can FlowRunner do with Moosend?

FlowRunner agents can run Get Lists, Get List Details, and Subscribe in Moosend, plus 4 more actions.

Does connecting Moosend to FlowRunner require OAuth?

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

Can Moosend trigger a FlowRunner workflow automatically?

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

Start building with Moosend

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

Start Building Free Talk to us