CleverReach

Connect AI agents to CleverReach. Agents manage recipient groups, add, update, and remove receivers, and read mailings and signup forms so email lists stay current without manual imports.

10 actions OAuth available

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

A new customer completes registration in the online store

List Groups resolves the target recipient group for the store's market

Get Receiver checks whether the email already exists in the group and in what activation state

Agent inspects the signup context for evidence of consent, which checkbox, which form, what timestamp

The marketing owner rules on any receiver the agent would activate without a clear consent record, because in a double opt-in market, activation is a legal assertion

Add Receiver upserts the subscriber with name and city attributes, source label, and registration timestamp

The signup logs to the marketing channel with source and group named

What This Integration Enables

CleverReach serves a market where email consent is not a best practice but a legal regime: double opt-in, documented provenance, deletion on request. That makes list hygiene a compliance function, and compliance functions deserve better than quarterly CSV imports. This connector puts FlowRunner agents on the job: they manage recipient groups, upsert receivers with activation state, source labels, and custom attributes, keep records current as source systems change, remove subscribers on unsubscribe or account deletion, and read mailings and forms for auditing. The payoff compounds: a list maintained continuously is also a list that can be defended continuously. When every receiver carries a source label and a registration timestamp written at the moment of signup, the answer to "prove this person consented" is a lookup, not an investigation, and the marketing team stops treating audit requests as emergencies. - Sync CRM, store, and form signups into the right recipient groups continuously - Upsert receivers with attributes, source labels, and Unix-second registration timestamps - Activate and deactivate receivers as consent state changes, with human review where evidence is thin - Execute removals same-day on unsubscribe or account deletion - Export receivers, mailings, and forms for audits and backups

Without FlowRunner

Imports happen quarterly Subscribers from the store and CRM reach the mailing list in batches, months stale

Consent evidence is scattered Who agreed to what, on which form, at what time lives in three systems and no report

Unsubscribes crawl through support An account deletion in one system leaves the address mailable in CleverReach for weeks

With FlowRunner

Lists update the day of signup Receivers upsert with attributes, source, and timestamp as registrations happen

Every receiver carries provenance Source labels and registration timestamps document where each address came from

Removal is same-day and logged Deletion and deactivation execute the moment the signal fires, with an audit line written

Use Case Scenarios

Store signups with provenance attached

A new customer registers in [Shopify](/integrations/shopify). The agent calls Add Receiver into the market's group with first name and city as attributes, the source labeled "shop-checkout-2026", and the registration timestamp from the actual event. Because Add Receiver upserts by email within the group, repeat purchases refresh the record instead of duplicating it. When the data protection officer later asks where an address came from, the answer is on the record, not in someone's memory.

The bulk import that checks before it writes

Marketing hands over a spreadsheet of event leads. The agent reads rows from [Google Sheets](/integrations/google-sheets) and, for each, calls Get Receiver first. Fresh addresses get added deactivated, queued for the double opt-in mailing; existing active receivers get their attributes updated with Update Receiver; addresses previously deactivated stop and wait for a human ruling. The list grows without ever quietly overriding a recorded refusal.

The deletion that actually completes

A customer deletes their account, triggering the erasure flow. The agent captures the receiver's state with Get Receiver for the compliance log, calls Delete Receiver to remove the group membership, and writes the confirmation with timestamps to the audit sheet. A weekly sweep of List Receivers against the CRM's deletion log verifies nothing resurrected. The DPO's report shows requests closed in hours, with evidence.

Human-in-Loop Highlight

Add Receiver and Update Receiver can set a receiver's activation state, and in CleverReach's home market that flag is a legal claim: activated means this person consented to receive marketing email, provably. An agent that activates receivers because a CRM field said "newsletter: yes" is manufacturing consent evidence it does not have, and the cost surfaces as a complaint to a data protection authority, not as a bounce. So FlowRunner flows hold a hard line: agents may add receivers deactivated, update attributes, and deactivate freely, but any transition to activated requires either a documented double opt-in event in the flow's inputs or a human's explicit sign-off: "Activate 43 receivers from the trade-fair list? No opt-in mailing has been sent to them." The marketing owner, who answers to the DPO, makes that call. The agent's job is to make the consent gap visible before the send list grows, and the ruling lands on the record next to the receivers it covered.

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

Groups

List Groups Lists all recipient groups with ID, name, total and active receiver counts, and creation timestamp. The map of the account's audiences.
Get Group Retrieves one group by ID with name, receiver counts, and configuration.
Create Group Creates a recipient group with a name, returning the new ID for receiver operations. The provisioning step for new markets or campaigns.

Receivers

List Receivers Lists a group's subscribers with pagination and optional detail fields: email, ID, activation and deactivation timestamps, source, and attributes. The export behind audits and backups.
Add Receiver Upserts a receiver by email within a group, with activation state, registration timestamp, source label, and custom attributes. The default sync write, gated in FlowRunner when it would activate without consent evidence.
Get Receiver Retrieves one receiver by email with activation state, timestamps, source, and attributes. The consent check that fronts every write.
Update Receiver Updates an existing receiver's activation state, source, or attributes, changing only supplied fields.
Delete Receiver Removes a receiver's membership from a group by email. The erasure executor in deletion flows, run with the audit line written alongside.

Mailings

List Mailings Lists newsletter campaigns with ID, name, subject, type, and status, paginated. The send-history read for reporting.

Forms

List Forms Lists sign-up forms with ID, name, and the group each feeds. The wiring reference that keeps subscription flows pointed at the right list.

Frequently Asked Questions

What can FlowRunner do with CleverReach?

FlowRunner agents can run List Groups, Get Group, and Create Group in CleverReach, plus 7 more actions.

Does connecting CleverReach to FlowRunner require OAuth?

Yes. CleverReach connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can CleverReach trigger a FlowRunner workflow automatically?

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

Start building with CleverReach

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

Start Building Free Talk to us