FlowRunner
PricingContact
Theme
Start Free

Attentive

Email Marketing

Feed Attentive's SMS and email marketing engine from your flows. Agents subscribe and unsubscribe shoppers, stream purchase, add-to-cart, and custom events to trigger journeys, and enrich profiles with custom attributes for segmentation.

7 actions API key available
Attentive website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
A completed signup arrives from a [Typeform](/integrations/typeform) offering SMS-first access to product drops
The agent validates the phone number as E.164 and records which version of the consent language the form showed
If the workflow requests Single Opt-In, the program owner approves skipping the confirmation step, because that is a compliance decision, not a convenience toggle
Subscribe User opts the shopper in under the form's sign-up source
Set Custom Attributes stamps the acquisition source and stated preferences onto the profile
Track Custom Event fires "Account Created" so the welcome journey starts with real context
The day's subscriber adds and any held opt-ins summarize to [Slack](/integrations/slack)

What This Integration Enables

Attentive's journeys are only as good as the events they run on. The platform reacts to what it can see, and out of the box it sees the storefront. FlowRunner's job here is to be the honest event pipeline for everything else: the POS sale, the subscription renewal, the reward earned in a loyalty database, the account created in your own app. Agents translate those moments into Attentive events and attributes the second they happen, and they treat the subscribe call itself as the regulated act it is. - Stream Track Purchase, Track Add To Cart, and Track Product View events from systems the pixel cannot see, powering post-purchase, abandoned-cart, and browse-abandonment journeys - Fire Track Custom Event for the moments unique to your business, with external event IDs so retries never double-trigger a journey - Keep profiles segmentation-ready with Set Custom Attributes as loyalty tiers and preferences change at the source - Mirror opt-outs from every support channel with Unsubscribe User, scoped to the right subscription type and channel - Put [human-in-the-loop](/concepts/human-in-the-loop) approval on every opt-in path that would skip confirmation

Without FlowRunner

Journeys blind to half the business Attentive sees the website pixel, but purchases from the POS, renewals from billing, and rewards from the loyalty system never become events
Imports treated as consent Lists arrive from partners and popups, and someone subscribes them in bulk without anyone owning the opt-in decision
Segments built on stale profiles Loyalty tier and preferences live in other systems, so the "VIP" segment is whoever was a VIP at the last manual sync

With FlowRunner

Every system becomes an event source Agents stream purchases, carts, views, and custom events from storefronts, POS, and billing into the journeys engine
Opt-ins carry a named approver Subscriptions flow automatically when consent is clean, and a person signs off whenever confirmation would be skipped
Profiles refresh as facts change Custom attributes update the moment the loyalty system or CRM changes, so segmentation reflects today

Use Case Scenarios

The order becomes a journey, whichever system it lands in

An order confirms in [Shopify](/integrations/shopify), and the agent calls Track Purchase with the line items, order ID, and totals, identified by the shopper's phone or email. The same agent watches the wholesale channel and the POS export, so an in-store sale fires the identical event. Post-purchase journeys, order confirmations, and revenue attribution now run on the full order stream instead of the online slice, and the attribution numbers the team argues about finally include every sale.

The loyalty program that lives elsewhere finally drives messaging

Loyalty math happens in a separate database. When a member crosses a threshold, the agent fires Track Custom Event with "Reward Earned" and the reward's properties, then calls Set Custom Attributes to update loyaltyTier on the profile. Attentive's segments and journeys pick both up immediately: the VIP segment grows the moment someone earns it, and the reward message goes out while the achievement is fresh. Because Set Custom Attributes overwrites existing keys, the agent writes complete values, never partial guesses.

Opt-outs honored across channels, with the match confirmed

A customer emails support asking to stop getting texts. The agent finds the ticket, extracts the identity, and assembles the evidence: the email on the ticket, the phone on the customer record, the subscription type in question. The program owner confirms the match, and the agent calls Unsubscribe User scoped to marketing messages on the SMS channel, leaving transactional notices intact unless the customer asked otherwise. The request is honored in minutes and logged to [Google Sheets](/integrations/google-sheets), and nobody's shipping notifications were casualties of an overbroad opt-out.

Human-in-Loop Highlight

Subscribe User carries a switch that changes its legal weight: Single Opt-In skips the confirmation step where your program allows it. Used well, it removes friction from a signup that already carries clean consent. Used carelessly, it subscribes a phone number to SMS marketing on the strength of a form fill nobody verified, and in US text marketing that is regulatory exposure attached to every message that follows. The subscription itself is also not quietly reversible: the shopper who gets an unwanted text does not distinguish between your agent's judgment and your brand's. So FlowRunner agents never flip that switch on their own. When a partner list or sweepstakes export arrives, the agent reports: "412 signups from the spring giveaway form, consent language v3 attached, requesting Single Opt-In. Approve, or route through confirmation?" The program owner makes the call, and the log records who made it. Everything else on this page runs at machine speed. The decision to skip confirmation never does.

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

Subscriptions

2
  • Subscribe User Subscribes a shopper to marketing messages for a given sign-up source, identified by E.164 phone and or email. Single Opt-In can skip the confirmation step where the program allows, which is exactly why this action sits behind the page's human gate.
  • Unsubscribe User Opts a shopper out of marketing or transactional subscriptions on a chosen channel. The compliance mirror for opt-out requests that arrive anywhere other than the unsubscribe keyword.

Events

1
  • Track Custom Event Sends a named behavioral event such as "Reward Earned" with arbitrary key and value properties, plus an optional external event ID for idempotency. The hook that lets any system in the stack start an Attentive journey exactly once.

Ecommerce

3
  • Track Purchase Records a completed purchase with line items, order ID, and totals. Powers post-purchase journeys, order confirmations, and revenue attribution, which is why agents feed it every sales channel, not just the web store.
  • Track Add To Cart Records an add-to-cart event with the products added. The standard trigger for abandoned-cart journeys.
  • Track Product View Records a browse event with the products viewed. Feeds browse-abandonment journeys and behavioral segmentation.

Attributes

1
  • Set Custom Attributes Sets custom attributes such as loyaltyTier or favoriteCategory on a profile, overwriting existing keys. The write that keeps segmentation synchronized with the systems where those facts actually change.

Frequently Asked Questions

What can FlowRunner do with Attentive?

FlowRunner agents can run Subscribe User, Unsubscribe User, and Track Custom Event in Attentive, plus 4 more actions.

Does connecting Attentive to FlowRunner require OAuth?

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

Can Attentive trigger a FlowRunner workflow automatically?

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

Start building with Attentive

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