--- title: "Vero Integration" description: "Connect AI agents to Vero. Agents identify users, update profiles and tags, track behavioral events, manage subscription state, and reidentify anonymous users after signup to drive behavioral email." url: https://flowrunner.ai/integrations/vero date_modified: 2026-08-07T17:20:23-07:00 --- # Vero [Email Marketing](https://flowrunner.ai/integrations/category/email-marketing) Connect AI agents to Vero. Agents identify users, update profiles and tags, track behavioral events, manage subscription state, and reidentify anonymous users after signup to drive behavioral email. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 8 actions · API key · available [Vero website](https://www.getvero.com/) · [Platform Documentation](https://developers.getvero.com/) · Capability data verified 2026-07-14 1. A user signs up or acts in another system 2. Agent identifies them with Identify User and a stable id 3. Agent records behavior with Track Event to trigger a campaign 4. Agent stores plan and profile data with Update User 5. Agent segments the user with Edit User Tags 6. Customer success channel gets a churn-risk signal 7. A permanent id migration routes for confirmation before Reidentify User runs ## What This Integration Enables An agent can identify a user (create or update their profile with a stable, unique id and optional email and properties), which is the required first half of Vero's model before any event is tracked. It updates properties on an existing profile, edits tags for segmentation, and manages subscription state with unsubscribe and resubscribe. Track Event is the second half: it records a named event that can trigger behavioral campaigns, creating the user from the identity object if they do not yet exist. For lifecycle and compliance, the agent deletes a user permanently, and reidentifies a user to migrate a temporary or anonymous id to a permanent one after signup while preserving the profile, events, and history. Vero exposes no event triggers in this integration, so flows start from the systems feeding it: a signup, a subscription, or a product event. The agent is the bridge between where behavior happens and the behavioral email that responds to it. ### Without FlowRunner **Events with no profile**: Behavior is tracked against users who were never identified **Profiles go stale**: Plan and signup data are set once and never refreshed **History lost on signup**: An anonymous user's activity is orphaned when they get a real id ### With FlowRunner **Identify precedes track**: Identify User creates the profile before Track Event records behavior **Profiles kept current**: Update User refreshes plan and properties as they change **History preserved**: Reidentify User migrates an anonymous id to a permanent one intact ## Use Case Scenarios ### Onboard on Subscription After a [Stripe](https://flowrunner.ai/integrations/stripe) Create Subscription succeeds, the agent calls Track Event with the plan details to enroll the customer in an onboarding email campaign, and Update User to store their plan on the profile. The onboarding sequence starts on the real subscription event, and the profile carries the plan campaigns segment on. ### Mirror a Signup When a source system captures a new signup, the agent mirrors it into Vero with Identify User and Edit User Tags so behavioral campaigns can target the right segment from the first event. The user is identified and tagged before any behavior is tracked. ### Churn-Risk Alert When Track Event records a churn-risk signal, the agent alerts the customer success team with the user id and event details through [Slack](https://flowrunner.ai/integrations/slack) Send Message To Channel. The signal reaches a human who can intervene, not just a campaign. ## Human-in-Loop Highlight Reidentify User changes a user's identifier while preserving their profile, events, and history. It is exactly what a signup needs when an anonymous id becomes permanent, and exactly the kind of change that corrupts a profile if the id mapping is wrong. When the agent is about to run Reidentify User, it treats the migration as a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step for cases it is not fully certain about. It pauses, shows the current id, the new id, and the profile the history will move to, and routes the decision to a data owner through Slack or email. The owner confirms the mapping, and the agent reidentifies. The owner holds, and the ids stay separate. Routine identify and track work flows through untouched; the change that rewrites who a profile belongs to gets a human. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 8 actions ### Profiles 5 - **Identify User** Creates or updates a user profile (the identify half of Vero's model). A user must be identified before events can be tracked. Provide a stable unique id and optionally an email and custom properties. - **Update User** Updates properties on an existing profile. Provide the id and a changes object with only the properties to add or update; others are left unchanged. - **Edit User Tags** Adds or removes tags on a user for segmenting and targeting. Tags already present (or already absent) are ignored. - **Delete User** Permanently deletes a user profile and its data. This cannot be undone. - **Reidentify User** Changes a user's identifier from their current id to a new one, preserving profile, events, and history. Used to migrate an anonymous id to a permanent one after signup. ### Subscription State 2 - **Unsubscribe User** Unsubscribes a user from all email in Vero. The profile is retained but no further campaign or transactional email is sent until resubscribed. - **Resubscribe User** Resubscribes a previously unsubscribed user, re-enabling email communications. ### Events 1 - **Track Event** Tracks an event performed by a user (the track half of Vero's model), which can trigger behavioral campaigns. Identify the user by id or email; the user is created from that identity if they do not yet exist. ## Frequently Asked Questions ### What can FlowRunner do with Vero? FlowRunner agents can run Identify User, Update User, and Edit User Tags in Vero, plus 5 more actions. ### Does connecting Vero to FlowRunner require OAuth? No. Vero connects to FlowRunner with an API key, no OAuth flow required. ### Can Vero trigger a FlowRunner workflow automatically? Vero doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Vero?** This integration exposes Vero to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/vero. Site index: https://flowrunner.ai/llms.txt