--- title: "What FlowRunner Offers Integration Partners" description: "What a FlowRunner integration does for the vendor behind it: instant MCP capability, AI agents that call your product as a tool, a public page AI answer engines can read, and a Verified badge, at no cost to you. 2142 products are already connected." url: https://flowrunner.ai/integrations/partners date_modified: 2026-09-05T15:31:58-07:00 --- # Your product, as a tool AI agents can call FlowRunner connects 2,142 products to AI agents that run business workflows and pause for a human when a decision carries weight. If your product is one of them, this page explains what the integration does for you. If it is not yet, it explains how to get one built. Either way, it costs you nothing. ## What you get ### Instant MCP capability We MCP-fy your API. Every action in the connector is exposed through FlowRunner's native Model Context Protocol support, so agents that speak MCP can call your product the day the connector ships. You do not design, build, or host an MCP server to get there. ### A tool, not a recipe Trigger-and-action recipes run your product on a fixed path. In FlowRunner, agents decide when to call your product, with what inputs, and what to do with the result, inside a workflow that spans the rest of the customer's stack. That is a larger surface than any recipe covers. ### Your customers build agents on your product Operations teams assemble agents visually, with no code, and the agent pauses for a person through email, Slack, WhatsApp, or phone when it needs judgment. Your product becomes something a non-technical team can put an AI agent in front of. ### A page AI answer engines can read Your integration gets a public, indexed page on flowrunner.ai listing every trigger and action by name, with a Markdown twin, an entry in the machine-readable catalog, and structured data. When someone asks an AI assistant what your product connects to, the answer has a source. ### A checkable quality claim The [Verified badge](https://flowrunner.ai/integrations/verified) means the connector was built from your official API reference and exercised against your live service, with the capability list re-checked mechanically on every sync. It is a claim your team can hold us to. ### No cost, no engineering time FlowRunner builds the connector, publishes the page, and keeps both current when your API moves. A sandbox account and a technical contact speed things up. Neither is required. ## How an integration gets built 1 Send your API documentation Fill out the contact form with a link to your API reference and, if you have one, a sandbox or trial account. That starts the conversation. 2 We build and verify The connector is implemented from your official reference and exercised against the live service. You get a timeline in the first conversation and a draft page before it publishes. 3 Your page goes live The integration ships to every FlowRunner plan and its page is indexed. Link to it from your own directory, and tell us when your API changes so both move together. ## Already in the catalog? Most vendors on this site never had to lift a finger, and some do not know their page exists. Three things make the integration work harder for you. - **Link to your page.** Add FlowRunner to your own integrations directory and point it at your page here. The page already lists every capability by name, so there is nothing to write. - **Tell us when your API moves.** The catalog tracks your API surface, but a note from your team gets new endpoints into the connector faster than a sync cycle does. - **Earn the Verified badge.** If your page does not carry it yet, the usual reason is that we could not get live credentials. Send sandbox access and we will do the rest. 2,142 Products connected 56,186 Callable actions 1,816 Verified against live APIs ## Frequently asked questions ### What does an integration cost the vendor? Nothing. FlowRunner builds the connector, publishes the page, and keeps both current when your API changes. There is no listing fee, no revenue share, and no engineering time required from your side. ### What does "MCP-fy" mean in practice? Every action in your connector is exposed through FlowRunner's native Model Context Protocol support. An agent that speaks MCP can call your product the same way it calls any other MCP service, and you did not have to design, build, or host an MCP server to get there. ### What do you need from us to build an integration? Your official API reference and a way to exercise the API against the real service, usually a sandbox or trial account. A technical contact who can answer questions about edge cases shortens the build. None of it is mandatory: if live access is not available, the connector is built from your published documentation and ships without the Verified badge until it has been exercised against the live service. ### How long does it take? It depends on the size and shape of your API. Send your documentation through the contact form and you will get a realistic timeline in the first conversation, not a generic promise. ### Can we review the integration page before it goes live? Yes. The capability list is generated mechanically from the connector, so the actions and triggers it shows are exactly what the connector does. The narrative around them is yours to correct before publication and any time after. ### Do FlowRunner customers pay extra to use our integration? No. Every integration is available on every FlowRunner plan, including the Free plan. Executions, concurrency, and log history are the only things FlowRunner meters. Your product is never behind a paywall. ### We are already integrated. What should we do? Link to your FlowRunner page from your own integrations directory, tell us when your API changes so the connector and page move with it, and if your page does not carry the Verified badge yet, send us sandbox access and we will earn it. --- Markdown version of https://flowrunner.ai/integrations/partners. Site index: https://flowrunner.ai/llms.txt