Connect a service

An integration connects an outside service to Flow XO. Model integrations let an agent use the provider’s models. MCP integrations provide tools that an agent can call. Workflows can also use connected accounts for steps such as Google Sheets.

Choose where to connect

Open Integrations in a workspace to share a connection with its projects. Open it inside a project for a connection owned by that project. The connect button names the destination: Connect to workspace or Connect to project.

An account can also come from the organization. Read the account’s scope in the integration details before replacing or disconnecting it. A project can use its own account instead of a shared account. Manage an inherited connection at the level that owns it.

Sign in

Find the service in the catalog, open its card, and choose the connection route. For OAuth, continue to the service’s sign-in page. Check the account and requested permissions before approving access.

Return to Flow XO and check the connection status. Don’t close the setup as soon as the service’s sign-in page finishes.

API key

Open the integration and choose Connect to project or Connect to workspace. Use View API key documentation to find the provider’s key page. Paste the key into API Key, then choose Connect.

Model requests made with your provider key are charged to that provider account.

Smithery

Choose the service’s Smithery route. If setup asks for a Smithery API key, use a key from Smithery. A saved Smithery key can be reused for gateway connections. Complete any service sign-in that follows.

Choose each service’s tools from its own integration. The Smithery account card stores the gateway key.

Reconnect or disconnect

Open the connected integration and read its status. If it offers Re-authorize, follow the sign-in flow for that existing connection. API-key connections offer a key update instead. Check the resulting status before using its tools again.

Choose Disconnect to stop using a connection. Read the confirmation: it names what goes to trash and which accounts or projects are affected. If an account overrides a shared account, the action can be Revert to workspace, Revert to project, or Revert to organization. Read which account will take over.

For custom MCP servers, use Move to trash in the server details. Restore archived items from Settings → Trash at the scope that owns them.