Integrations

Using integrations

Use a connected account in a workflow step, an agent tool, a trigger or a hosted MCP server, and see what happens when the account is missing.

A connected account does nothing by itself. It becomes useful when a step, a tool or a trigger uses it. This page shows the places where that happens. To connect an account first, see Connecting accounts.

The step reference#

Every action an integration offers is documented in the integration step reference, grouped by app. Each entry shows the inputs and outputs of the step, the plans it is available on, and whether an agent can call it as a tool. Use it to see what an app can do before you build.

In a workflow#

In the Add Component dialog, the steps for each app form their own category, next to the core ones. Search for the app by name or pick its category. See Canvas basics.

When you add a step whose account is not connected, a dialog tells you that the integration is required and shows its card. Click the card to connect it, then continue. Later, when you select the step, its settings panel shows Integrated in the header if the account is connected. If it is not, the panel offers to connect it there.

As a trigger#

Some triggers start a workflow when something happens in an app, such as a new email in Gmail, a Slack message or a GitHub pull request. They work like any other app step: the account has to be connected, and the workflow has to be published. See Triggers.

As an agent tool#

In the agent builder, the Apps section lists what an agent can use. Choose Add app, and in the dialog pick Use FlowHunt tools. Each app row shows whether it is Connected, and a Connect button when it is not. See Agent tools.

If you open an agent that needs accounts you have not connected, a Connect Integrations dialog lists them. Connect what you need, then choose Continue to chat, or choose Skip and continue to try the agent without them. Tools that need a missing account will not work.

As a hosted MCP server#

You can also turn an app’s actions into a Model Context Protocol server that other AI tools connect to. See Hosted MCP servers.

Plans and credits#

Not every app step is on every plan. If you add a step your plan does not include, the editor refuses it with a message naming the plans that can use it. Steps spend credits when they run, like any other step. See Plans and limits and Credits.

Connect before you test

A test in the Run tab uses your real accounts. Connect the account and check which workspace data it can reach before you run steps that write, send or delete.