Engage
Email MarketingSync customers and send lifecycle messages with Engage, covering customers, accounts, events, and campaigns. Agents keep lifecycle messaging driven by product behavior rather than a periodic list upload.
What This Integration Enables
Engage models a customer as a person inside an account, which is what B2B software actually looks like and what most lifecycle tools flatten away. A Customer can be attached to several Accounts, each with a role, and an Account is itself a user object you can message and segment. That matters more than it sounds. It means an agent can fan a workspace-level event out to every seat, message the billing owner rather than whoever signed up first, or stop messaging one person about a workspace they left last month while leaving their membership of two others alone.
The identity discipline is deliberate too. Users are keyed by an identifier from your own database, never by an email address, so an address change is an attribute update rather than a new record. Update User upserts, Merge Users folds duplicate profiles together, and Archive User exists as a distinct thing from Delete User: archiving stops engagement and stops recording events while preserving the message history, which is usually what you want for a churned customer and almost never what a hard delete gives you. FlowRunner connectors expose all of it, plus transactional email and SMS for the one-off messages that should never go through a campaign, and a batch endpoint for volume.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Seat changes flowing straight into messaging
An admin removes a teammate in the product. The agent calls Remove Customer From Account so that person stops receiving anything scoped to that workspace, while their profile and any other account memberships stay untouched. If the departing person held an owner role, the agent also calls Get Account Members to find who is left, then Change Account Role to promote the remaining admin, and sends a transactional email confirming the handover. Nothing about this requires a marketer to notice a seat changed.
Product behavior driving the sequence
A trial account hits a meaningful activation milestone. The agent calls Track User Event with the properties that describe what happened, then Add User To Lists to move them into the activated cohort so Engage's own automations pick up the segmentation from there. If the milestone was a payment, the agent reads the amount from Stripe and attaches it as the event value so revenue-weighted segments stay accurate. Behavior updates the profile the moment it happens rather than in the next sync window.
Deduplicating profiles created by two front doors
Anonymous signups and a separate CRM sync have produced two Engage profiles for the same person. A cleanup agent finds the pair with List Users, pulls both with Get User to compare account memberships, roles, list subscriptions and message statistics, and then calls Merge Users to fold the source profile into the destination. Because Engage keys on the ID you assigned, the flow can also write the surviving key back into Salesforce so the two systems stop disagreeing about who this person is.
Human-in-Loop Highlight
The gate is on choosing the import path, because Engage offers two that look interchangeable and are not. Create User subscribes any lists you supply silently, with no opt-in confirmation email. Subscribe To List creates the user and subscribes them, and if the list has double opt-in enabled it sends a confirmation email automatically. Point a bulk import at the first and you have silently added thousands of people to a marketing list with no recorded consent. Point it at the second and eight thousand confirmation emails leave in one burst against a sending domain that has never seen that volume, which is its own kind of afternoon you cannot take back. Both are one-line differences in the flow and neither errors. So the agent stops before the write and puts the tradeoff in the room: "8,000 rows ready. 1,240 already exist in Engage. The target list has double opt-in enabled, so Subscribe To List will send 6,760 confirmation emails today. Create User would add all of them with no confirmation and no consent record. Send the confirmations, throttle them across five days, or hold the import until the consent basis for this list is confirmed?" The agent is not asking permission to work. It is refusing to make a consent decision that belongs to a person.
Agent Capabilities
27 actionsUsers
10- Create User Adds a Customer or Account to Engage, keyed by an identifier from your own database rather than an email address. Used on signup so segments and automations have a complete profile from day one. Lists supplied here are subscribed silently with no opt-in confirmation email, which is a consent decision, not a technical detail.
- Get User Retrieves the full profile for a Customer or Account including list memberships, segment membership with suppression state, account roles, custom attributes and message statistics. Used to check current state before a write, and to compare two records before a merge.
- List Users Returns a cursor-paginated page of Customers and Accounts, optionally narrowed to one email address. Used to walk a full audience for export or cleanup, following the next cursor.
- Update User Updates profile fields and custom attributes, creating the user when the ID is not yet known. Attributes merge into the existing profile, so a flow sends only what changed. Changing the email address requires the full key and secret credentials.
- Delete User Attribute Removes a single custom attribute from a profile. Used to retire a trait that no longer means anything. Standard name, email and number fields are cleared with Update User instead.
- Delete Device Token Removes a stored push notification device token from a profile. Used when someone logs out of a mobile app so they stop receiving push on a device they no longer control.
- Track User Event Records an application event against a user so it can drive segmentation and trigger automations, with either a simple numeric or string value or a properties object for richer context. Used for the product moments that should change what someone receives next.
- Merge Users Folds one user profile into another, consolidating duplicates created by anonymous signups or by separate integrations. Used in cleanup flows. The source profile's data moves into the destination, so the surviving record inherits both histories.
- Archive User Archives a Customer or Account so it stops receiving engagements and no longer records events, while preserving all historical messages, logs and related data. Used for churned customers where an auditable record still matters.
- Delete User Permanently deletes a Customer or Account and all of its data. Irreversible, and normally reserved for GDPR or CCPA erasure requests. Archive User is the right operation when the goal is only to stop messaging someone.
Accounts and Seats
5- Change User Type Converts a Customer into an Account or an Account back into a Customer, preserving existing attributes and history. Used when a personal signup becomes a company workspace once other members join.
- Add Customer To Accounts Attaches a Customer to one or more Accounts with an optional role per Account. Used to model B2B seat membership, with Account IDs being the user IDs of the Account entities.
- Remove Customer From Account Detaches a Customer from a single Account while leaving the profile and any other memberships untouched. Used when a teammate is deprovisioned, so workspace-scoped messaging stops immediately.
- Change Account Role Sets or replaces the role a Customer holds inside an Account, creating the assignment when none exists. Roles are free-form strings and can be used as segmentation criteria, so a promotion changes what someone receives.
- Get Account Members Returns every Customer belonging to an Account as a full user object including role, attributes and message statistics. Used to fan a workspace-level event out to all seats, or to audit who has access.
Lists
5- Create List Creates a subscriber list, optionally with double opt-in confirmation and a post-subscription redirect for hosted forms. Titles and descriptions are visible to subscribers on the preference page, so they are written for people rather than for operators.
- List Lists Returns a cursor-paginated page of lists with subscriber and broadcast counts. Used to resolve list names to IDs and to report on audience sizes.
- Get List Retrieves a single list with its title, description, opt-in settings and current counts. Used as the preflight check that tells a flow whether a subscription will trigger a confirmation email.
- Update List Updates the title, description, redirect URL or double opt-in setting of an existing list, changing only the fields supplied.
- Archive List Archives a list so no new subscribers can be added, while existing subscribers keep receiving anything already scheduled. Used to retire a campaign audience without disrupting sends in flight.
Subscriptions
4- Add User To Lists Subscribes an existing Customer or Account to one or more lists in a single call. Used when a purchase or a preference change should widen the audiences a known user belongs to. Subscribe To List is the right operation instead when the person may not exist in Engage yet.
- Subscribe To List Creates a user and subscribes them to a list in one step, matching an existing profile by email or phone when one is present. Used to wire a signup or newsletter form directly to a flow. When the list has double opt-in enabled, a confirmation email is sent automatically.
- Update Subscriber Status Subscribes or unsubscribes an existing user on a list without removing them from it. Used to honor an opt-out, because the membership record stays and preserves the compliance evidence.
- Remove Subscriber From List Deletes a user's membership of a list entirely, unlike unsubscribing which keeps the record with an opt-out flag. Used for bad-data cleanup, never as the response to an unsubscribe request.
Messaging
2- Send Transactional Email Sends a one-off transactional email such as a password reset or a receipt, using HTML, plain text, or a named Engage template with its variables. Used for the messages that must arrive regardless of marketing preferences. Requires a connected sending domain or ESP.
- Send Transactional SMS Sends a one-off transactional SMS through a connected provider. Used for time-sensitive service notifications. The provider must be named explicitly and the sender ID has to be one registered with that provider.
Bulk Operations
1- Send Batch Request Queues many create-user, update-user and track-event operations in a single call. Used for nightly syncs and backfills. The response returns queued without validating individual items, so malformed rows fail silently and the flow needs its own verification step rather than trusting the acknowledgement.
Frequently Asked Questions
What can FlowRunner do with Engage?
FlowRunner agents can run Create User, Get User, and List Users in Engage, plus 24 more actions.
Does connecting Engage to FlowRunner require OAuth?
No. Engage connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Engage trigger a FlowRunner workflow automatically?
Engage doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Engage
$100 in credits. No card required. Connect in minutes.