FlowRunner
PricingContact
Theme
Start Free

User.com

Email Marketing

Sync contacts into User.com and keep them current: agents create or update users matched on email, update individual profile attributes, look up contacts by any field, and send custom events that power User.com automations and segmentation.

6 actions API key available
User.com website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
An order completes in the storefront with a customer email attached
Search Users looks the customer up by email to see whether a profile already exists
Create or Update User syncs the buyer's name and order-derived custom attributes, matched on email
The agent confirms this is a genuinely new purchase, not a replay from a re-run or a refund reversal
Send Event fires purchase_completed with the order value and products as event data
The synced profile and fired event log to the audience tracking sheet
A lifecycle marketer reviews the weekly log of fired events against orders, and rules on any mismatch before the next run

What This Integration Enables

User.com sells itself as all-in-one engagement: chat, email, automations, and segmentation driven by user profiles and the events that hit them. The catch in every event-driven platform is that automations only know what the event stream tells them, and the native tracker only sees the website. FlowRunner agents widen the stream. They sync contacts from every capture point, keep individual attributes current without re-sending whole profiles, and fire the custom events, purchase_completed, feature_used, plan_upgraded, that User.com's automations and segments are built to react to. - Sync signups, CRM records, and enriched profiles into User.com, matched on email - Update specific attributes in place as customer data changes elsewhere - Look up contacts by email or any custom attribute before updating or messaging - Fire custom events with structured data to trigger automations and refine segments - Browse and export the audience with paginated listing The attribute model rewards precision. Update Attributes changes exactly the fields named and nothing else, which means concurrent workflows can each own their slice of the profile, one syncing billing state, another syncing product usage, without overwriting each other's work. Search Users then turns those attributes into an operational query surface: any field an agent writes becomes a field another workflow can select on. Events are triggers with customer-facing consequences, which is why FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) discipline treats Send Event as the operation to respect. Profile writes are reversible edits; a fired event is a starting gun.

Without FlowRunner

Profiles freeze at signup Contacts enter User.com once and never learn anything the customer did afterward
Automations wait on events that never come The journeys are built, but the triggering events only fire from the website tracker
Lookups mean exports Finding contacts by attribute means exporting the audience and filtering in a spreadsheet

With FlowRunner

Profiles track the customer Attributes update from every system the customer touches, matched on email
Events flow from everywhere Purchases, feature usage, and milestones fire as events no matter which system saw them
The audience is queryable Search Users answers attribute questions in-flow, and matches route straight to people

Use Case Scenarios

The purchase event that starts the journey

A [Shopify](/integrations/shopify) order lands. The agent upserts the buyer with Create or Update User, then fires Send Event with purchase_completed and the order details as event data. Inside User.com, the post-purchase journey starts on time: the thank-you message, the review request two weeks out, the replenishment reminder when the product runs low. Marketing built the journey once; the agent guarantees every order actually enters it, including the ones placed through channels the website tracker never sees.

Form answers that become segmentation fuel

Lead submissions arrive from [Typeform](/integrations/typeform). For each respondent, the agent calls Create or Update User with the answers mapped to custom attributes: company size, use case, urgency. Segments keyed on those attributes update immediately, and the nurture automations built on them start sorting leads the same hour the form was submitted. When a single field changes later, Update Attributes corrects just that field instead of re-sending the record, leaving every other workflow's writes intact.

The high-value match that finds a human

The agent runs Search Users for contacts whose attributes cross a threshold, enterprise domain, high lifetime value, trial expiring this week, and posts each match to [Slack](/integrations/slack) with the full profile from Get User attached. The rest of the audience export appends to [Google Sheets](/integrations/google-sheets) for the weekly review, page by page via List Users until the whole base is covered. The team stops discovering their best accounts in retrospective reports and starts hearing about them while the timing still matters, with the evidence attached to the alert instead of a link to go find it.

Human-in-Loop Highlight

Send Event is the trigger wire of this integration: User.com automations listen for named events, and the moment purchase_completed fires, whatever journey is bound to it starts delivering real messages to a real customer. The dangerous case is not the single event, it is the replay. A re-run workflow, a backfill of historical orders, a retry loop that fires the same event three times, and suddenly customers get thank-you sequences for purchases from last spring, or three copies of the same journey at once. There is no unsending what the automation dispatched. So FlowRunner agents fire events only from verified fresh occurrences, deduplicate against what was already sent, and stage anything backfill-shaped for human review: this event name, this many users, these automations listening on the other end. A person confirms the blast radius before history is allowed to replay. Live events flow at machine speed; bulk event operations wait for a yes.

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

6 actions

Users

5
  • Create or Update User Creates or updates a contact matched on email, setting standard fields and any custom attributes as a key/value object. The primary write for syncing signups, CRM records, and enrichment.
  • Get User Fetches one contact by User.com ID with full profile and all custom attributes. The context pull before routing or messaging decisions.
  • List Users Retrieves the audience with page-based pagination, returning core profile fields and custom attributes. The read behind exports and audits.
  • Search Users Finds contacts whose attribute matches a value, email, name, or any custom attribute, returning all matching profiles. The lookup that makes the audience queryable in-flow.
  • Update Attributes Updates one or more attributes on a contact by ID without re-sending the full record. The surgical write for keeping profiles current.

Events

1
  • Send Event Sends a named custom event for a user with optional structured data, powering automations, triggers, and segmentation. The automation trigger this page's human gate exists for.

Frequently Asked Questions

What can FlowRunner do with User.com?

FlowRunner agents can run List Users, Get User, and Create or Update User in User.com, plus 3 more actions.

Does connecting User.com to FlowRunner require OAuth?

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

Can User.com trigger a FlowRunner workflow automatically?

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

Start building with User.com

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