--- title: "involve.me Integration" description: "involve.me is a funnel builder for quizzes, calculators, surveys and lead forms. Agents build personalized funnel links and embed snippets from flow data, list funnels, and start a flow on every funnel submission." url: https://flowrunner.ai/integrations/involve-me date_modified: 2026-09-04T19:08:45-07:00 --- # involve.me [Forms](https://flowrunner.ai/integrations/category/documents-forms) involve.me is a funnel builder for quizzes, calculators, surveys and lead forms. Agents build personalized funnel links and embed snippets from flow data, list funnels, and start a flow on every funnel submission. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 trigger · 3 actions · API key · available [involve.me website](https://involve.me/) · [Platform Documentation](https://help.involve.me/en/articles/2193514-receive-submission-data-with-webhooks-anywhere) · Capability data verified 2026-08-26 1. A campaign segment becomes due to receive a qualification quiz 2. Agent reads each contact's first name, plan tier and campaign source from the CRM 3. Agent compares those fields against the hidden fields the funnel actually declares 4. Build Funnel Link produces one personalized URL per contact with a remote id attached 5. Agent decodes a sample of the generated links back into plain text 6. Demand gen reads the decoded sample and approves the payload before the batch is mailed ## What This Integration Enables involve.me is a distribution surface, not a system of record, and the connector is honest about that. involve.me publishes no meaningful REST API: one live route lists your funnels, and everything else the platform offers happens in the browser. So the two operations you will use most, Build Funnel Link and Build Funnel Embed Code, do not call involve.me at all. They assemble the artifact you are about to hand a person, encoding hidden fields, a remote id and a starting page into a URL or an embed container that involve.me reads when the participant arrives. That inverts where the risk sits. There is no stored record to correct, no update call, no delete. The only thing an agent can get wrong is what it wrote into the link before the link left the building, which is exactly the kind of moment FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) discipline is built for. Agents pull the segment, build the links, decode a sample, and put the payload in front of the person who owns the campaign. Every operation here is built and verified against involve.me's documented behavior. ### Without FlowRunner **One link for everyone**: A single funnel URL goes to the whole list, so nothing comes back attributed to a person **Reconciliation after the fact**: Submissions are matched to contacts later by email address, which breaks the moment someone answers from a different one **Hand-edited embed snippets**: Landing page code is copied and adjusted per campaign, and drifts from the funnel it points at ### With FlowRunner **One link per contact**: Every recipient gets a URL carrying their own values and a remote id the flow chose **Attribution at submission time**: The completed submission arrives already keyed to the record it belongs to **Snippets assembled from flow data**: Embed code is generated per campaign from the same values the link carries ## Use Case Scenarios ### A personalized quiz link per contact An agent pulls a segment from [HubSpot](https://flowrunner.ai/integrations/hubspot) and, for each contact, calls Build Funnel Link with the first name, plan tier and a remote id set to the CRM record id. The links go out through [Brevo](https://flowrunner.ai/integrations/brevo) as a transactional send, one personalized URL per recipient. When On Submission Completed fires, the payload carries that remote id back, so the agent writes the outcome and score onto the right record without guessing at email addresses. The join key was decided by the flow, not inferred afterwards. ### Score-based routing the moment a funnel finishes On Submission Completed delivers the whole finished funnel: the outcome, the score value, the flat answer list and the values map keyed by question text. An agent branches on the score. High scorers post to the sales channel in [Slack](https://flowrunner.ai/integrations/slack) with the outcome and the answers that drove it, so a rep sees the reasoning rather than a number. Everyone else lands in a nurture sequence. Partial submissions never fire the trigger, so nobody is scored on a funnel they abandoned halfway. ### A submissions ledger nobody maintains Every completed submission appends a row to [Google Sheets](https://flowrunner.ai/integrations/google-sheets): the funnel name, the finish time, the outcome and the flattened values map. List Funnels runs alongside it on a schedule so the ledger's funnel column stays reconciled against the live account rather than a list somebody typed once. Marketing gets a queryable record of every quiz, calculator and survey the account runs, in a place they already know how to filter. ## Human-in-Loop Highlight Build Funnel Link writes hidden fields into a query string, and a query string is not private. The participant can read it, and so can anyone they forward the link to. The remote id is worse, because it is the only join key the submission will ever carry: set it wrong and every response in the campaign attaches to the wrong record, with no stored object on involve.me to go back and repair. So before the first send of a new campaign, the agent builds ten links, decodes them, and posts the result to the campaign owner: "This batch carries first\_name, plan\_tier and internal\_account\_value as hidden fields, and remote\_id is the HubSpot record id. Recipients can read all three in the address bar. Send, or drop a field?" The owner usually drops one. Then the batch goes. 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 3 actions ### Funnels 1 - **List Funnels** Lists the funnels in the account with their ids, names and URL slugs. This is the single live route involve.me's API namespace exposes, and it is how a flow discovers a funnel to build against or reconciles an incoming submission back to a project. ### Personalized Distribution 2 - **Build Funnel Link** Builds a shareable funnel URL with hidden fields, a remote id and an optional starting page encoded into the query string. Used to send each contact their own quiz, calculator or survey with their data already carried in. - **Build Funnel Embed Code** Builds the HTML snippet that embeds a funnel inside your own page, with hidden fields, remote id and start page written into the container's data attributes. Used when the funnel lives on a landing page rather than at the end of an email. ## Triggers 1 triggers ### Event Triggers 1 - **On Submission Completed** Fires in real time when a participant finishes a funnel and reaches the thank you or outcome page. Partial submissions never fire it. The delivery carries the outcome, the score, the flat answer list and the values map, which is enough to route, score and record without a follow-up read. ## Frequently Asked Questions ### What can FlowRunner do with involve.me? FlowRunner agents can run List Funnels, Build Funnel Link, and Build Funnel Embed Code in involve.me. ### Does connecting involve.me to FlowRunner require OAuth? No. involve.me connects to FlowRunner with an API key, no OAuth flow required. ### Can involve.me trigger a FlowRunner workflow automatically? Yes. involve.me supports 1 trigger that can start a FlowRunner workflow automatically. **Work at involve.me?** This integration exposes involve.me 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/involve-me. Site index: https://flowrunner.ai/llms.txt