What the Verified badge means
Integration directories are easy to inflate. A logo wall says nothing about whether the connector behind it works, covers the API it claims, or was ever pointed at the real service. The Verified badge is our answer: a specific, checkable claim about how an integration was built, published where you can hold us to it.
An integration earns the badge when all of this is true
- Built against the vendor's official API. Every action and trigger is implemented from the vendor's own API reference, not scraped from a third-party wrapper or guessed from marketing pages.
- Exercised against the live service. Authentication behavior, endpoint existence, and response handling were confirmed against the vendor's real API during development, not assumed from documentation alone.
- The page matches the connector, mechanically. The capability list on each integration page is generated from the same catalog the platform runs, and checked name-for-name on every sync. If the page says the action exists, the action exists.
- Re-checked when the vendor moves. The catalog tracks each vendor's API surface. When actions are added or removed upstream, the connector and its page are updated together, with the sync date stamped on the page.
What about integrations without the badge?
A small number of vendors offer no sandbox, no trial account, and no path to live credentials. For those services the connector is built from the vendor's official API documentation or published OpenAPI specification, coverage is checked mechanically against that spec, and the things we could not confirm live are documented rather than smoothed over. Those integrations ship without the badge until they have been exercised against the real service. No badge is a statement of provenance, not a warning: it means we are telling you exactly how the connector was built instead of rounding up to "verified."
Why we publish this
FlowRunner agents call these integrations as tools and pause for a human when a decision carries weight. That model only works if the tool layer is honest about what it can do. Inflating a directory with connectors nobody ever ran would be the same dishonesty we built the platform to prevent, one layer down.
See it work on your data
$100 in credits. No card required. We build the first workflow with you.