--- title: "RudderStack Integration" description: "Stream events to RudderStack from any workflow. Agents send track, identify, page, screen, group, and batch calls to the data plane and manage sources, destinations, and connections on the control plane." url: https://flowrunner.ai/integrations/rudderstack date_modified: 2026-08-04T10:04:16-07:00 --- # RudderStack [Analytics & Data](https://flowrunner.ai/integrations/category/analytics-data) Stream events to RudderStack from any workflow. Agents send track, identify, page, screen, group, and batch calls to the data plane and manage sources, destinations, and connections on the control plane. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 15 actions · API key · available [RudderStack website](https://rudderstack.com/) · [Platform Documentation](https://www.rudderstack.com/docs/) · Capability data verified 2026-07-27 1. A new customer completes signup in the product 2. Identify User creates the profile with email, name, and plan traits 3. Track Event records "Signed Up" with the acquisition properties attached 4. Group associates the user with their company account and its traits 5. The agent finds a prior anonymous ID whose session history overlaps the signup 6. The proposed identity merge goes to the analytics owner with both histories side by side 7. Alias merges the anonymous history into the known user after approval 8. The team channel confirms the profile is complete and flowing to every destination ## What This Integration Enables A customer data platform is only as good as what feeds it, and what feeds most of them is the website and nothing else. The events that actually explain revenue, the order that needed a manual approval, the refund a human authorized, the onboarding step that stalled for three days, happen in operational tools that never call a tracking API. FlowRunner closes that gap by making every workflow an event source: agents stream track, identify, page, screen, and group calls to the RudderStack data plane as a side effect of doing the work itself. - Record operational events, approvals, exceptions, fulfillment milestones, as first-class analytics events - Build unified profiles by sending identify and group calls with user and account traits from any system - Merge anonymous and known identities with alias calls that a person approves first - Ingest high volume efficiently with batch calls carrying mixed event types - Provision and inspect sources, destinations, and connections on the control plane without opening the console This is the [Orchestration as a Service](https://flowrunner.ai/concepts/orchestration-as-a-service) thesis applied to analytics: when agents do the work, the record of the work comes free. ### Without FlowRunner **The pipeline only sees the website**: Events from back-office workflows, approvals, exceptions, fulfillment, never reach analytics **Anonymous history stranded**: A visitor's pre-signup behavior stays orphaned under an anonymous ID after they convert **Plumbing changes wait on a ticket**: New sources and destinations queue for whoever has console access this sprint ### With FlowRunner **Every workflow is an event source**: Agents emit track, identify, and group calls from any automation, so operational events land in the CDP **Identities merge with evidence**: Alias calls are proposed with both histories attached and approved by a person before they propagate **Pipeline provisioning on demand**: Sources, destinations, and connections are created and inspected programmatically ## Use Case Scenarios ### Commerce events without instrumenting the store When a [Shopify](https://flowrunner.ai/integrations/shopify) order lands, the agent calls Track Event with an "Order Completed" event carrying the order value and customer ID. New customers get Identify User with email, name, and shopper traits. When [Stripe](https://flowrunner.ai/integrations/stripe) confirms the payment, a "Payment Succeeded" event follows, and a row appends to a revenue sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets). The CDP sees the full purchase story, and none of it required a developer to touch the storefront's tracking code. ### The back office becomes visible A FlowRunner approval workflow escalates a high-value refund to a manager through [Slack](https://flowrunner.ai/integrations/slack). Whatever the manager decides, the agent records it: Track Event logs "Refund Approved" or "Refund Denied" with the amount, the reason, and how long the decision took. Overnight, Batch Events ships the day's accumulated operational events, mixed track, identify, and group payloads in one request. For the first time, the analytics team can segment customers by what happened in operations, not just what happened on the site. ### Pipeline provisioning as a governed workflow A new product launch needs its own event stream. The agent calls Get Workspace to confirm the access token targets the right workspace, Create Source to provision the HTTP source and capture its generated write key, and Create Destination to route events onward. List Connections verifies the routing before launch day, and the destination config goes past a human before any live customer data flows through it. What used to be a console session and a ticket is a reviewed, repeatable flow. ## Human-in-Loop Highlight Alias is the one call in this connector with no undo. It merges two identities, and every destination downstream, the warehouse, the analytics tools, the marketing platforms, replays that merge into its own records. Fuse the wrong anonymous history onto a customer and their profile is contaminated everywhere at once, with no API to split them apart again. So FlowRunner agents never alias on inference alone. The agent presents its case: this anonymous ID shares a device fingerprint and an overlapping session window with the new signup, here is each history. The analytics owner confirms or rejects the match. Only a confirmed match becomes an Alias call. Identity resolution runs at machine speed; the irreversible merge waits for a person. 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 15 actions ### Event Stream 7 - **Track Event** Sends a track call recording a user action such as "Order Completed" with optional properties, attributed by user ID or anonymous ID. The workhorse for making workflow outcomes visible in analytics. - **Identify User** Sends an identify call associating a user with traits like name, email, and plan. The profile-building step for signups and enrichment sweeps. - **Page** Sends a page call recording a web page view with name, category, and properties such as url and referrer. - **Screen** Sends a screen call, the mobile-app equivalent of a page view, with screen name and properties. - **Group** Sends a group call associating a user with a company, account, or organization and its group-level traits. The step that makes account-level analytics possible. - **Alias** Sends an alias call merging a previous identity into a new user ID. Irreversible downstream, and the operation this page's human gate exists for. - **Batch Events** Sends multiple events in one request, each with its own type and payload. The efficient path for high-volume and end-of-day ingestion. ### Workspace Management 8 - **List Sources** Lists every event stream source in the workspace with id, type, write key, and enabled state. The discovery step before wiring connections. - **Get Source** Retrieves one source's full configuration by ID. - **Create Source** Creates a new event stream source of a given type and returns the write key RudderStack generates for it. The provisioning step for new apps and launches. - **List Destinations** Lists every configured destination with id, type, config, and enabled state. - **Get Destination** Retrieves one destination's full configuration by ID, used to review routing before changes. - **Create Destination** Creates a destination of a given type with its destination-specific config. Reviewed by a person before live data flows, because events sent onward cannot be recalled. - **List Connections** Lists the source-to-destination connections that control where events route. The verification step before a launch. - **Get Workspace** Retrieves the workspace tied to the access token, including id, name, and region. The safety check that management operations target the right workspace. ## Frequently Asked Questions ### What can FlowRunner do with RudderStack? FlowRunner agents can run Track Event, Identify User, and Page in RudderStack, plus 12 more actions. ### Does connecting RudderStack to FlowRunner require OAuth? No. RudderStack connects to FlowRunner with an API key, no OAuth flow required. ### Can RudderStack trigger a FlowRunner workflow automatically? RudderStack doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at RudderStack?** This integration exposes RudderStack 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/rudderstack. Site index: https://flowrunner.ai/llms.txt