Skip to main content
Agents

How to connect your agent to apps with MCP integrations

Connect apps like Google Calendar, Gmail, Supabase or WhatsApp Business to your AI agent, choose which actions it can use, understand what each action costs, and solve common problems.

Last updated 20 days ago

MCP integrations connect your agent to apps you already use, like Google Calendar, Gmail, Google Sheets, Supabase or WhatsApp Business. Once an app is connected, the agent can use its actions during a conversation: check free slots, create an event, read a row, send a message.

This guide has four parts: how to connect an app, what it costs, a technical reference, and answers to common problems.

Before you start: Have access to the account of the app you want to connect. Some apps connect by signing in; others ask for an API key or a token that you generate in that app.

Step 1: Open Integrations (MCP)

In the left menu, open Agents and select your agent. Open Integrations, then Integrations (MCP). Find the app with Search integrations... or filter by category.

The connections you make here are also available for your automations.

Step 2: Connect the app

Click Connect on the app, for example Google Calendar. In Connect to Google Calendar, click Authorize. You're taken to Google to sign in with the account whose calendar the agent will use and to allow access, and then you come back.

Some apps don't connect by signing in. Their window shows an Authentication method and asks for data like an API key, a token or an account ID. Each field explains where to find it. Fill them in and click Connect.

Step 3: Turn on the actions

When the app connects, Configure opens. Turn on the actions your agent can use, use the search to find them, and click Save. The counter shows how many actions the agent has out of 50.

Important: Connecting the app isn't enough for the integration to work: the agent only uses the actions you turn on. Turn on only the ones it needs, especially actions that change or delete data.

Step 4: Tell the agent when to use it, and test it

In your agent's prompt, say when to use the app. For example: "Before offering a time, check availability in Google Calendar". Then open Test Agent and ask something that needs the app: the chat shows each action the agent runs and its result.

Manage a connected app

Connected apps appear first, under Connected. On each card:

  • Configure: turn actions on or off.

  • Disconnect: unlink the app from this agent. The agent loses access to its actions, and you can reconnect at any time.

Tip: Disconnect is on the card, next to Configure, not inside Configure. To change the authentication method or the connected account, disconnect first and connect again.

What it costs

Each action that runs successfully deducts credits from the wallet that pays for the agent. If there aren't enough credits, the action doesn't run and the agent continues the conversation.

As an agency, you set the price your clients pay per action. In the left navigation panel, open Settings, then go to the Integrations tab. The Marketplace Tool Pricing section shows:

  • Platform base rate: what the platform charges per execution.

  • Your rate per execution: what your customers pay. It must be equal to or higher than the base rate.

  • Your margin: the difference, which you keep per each execution.

Type your rate and click Save changes. If you don't set one, the platform rate is used.

Technical reference

  • Per agent: each agent has its own connections. Connecting an app to one agent doesn't connect it to the others, and an agent can have only one active connection per app.

  • Up to 50 actions per agent, adding up all its connected apps.

  • Permissions: actions run with the permissions of the account you connected. If that account can't do something in the app, the agent can't either.

  • If the app fails: if the app doesn't answer or returns an error, the agent receives the error and continues the conversation.

  • Long responses: the agent reads up to 50 KB of each response.

  • Credentials: keys and tokens are stored securely. Disconnecting revokes the connection.

Common problems

  • Open Configure and check that the actions it needs are on, then click Save.

  • Say in the prompt when the agent should use the app.

  • Check that the wallet has credits.

Use the whatsapp_auth method, not whatsapp_oauth2. The sign-in method can link the wrong account. If you already connected with it:

  1. Click Disconnect on the WhatsApp Business card.

  2. In Meta Business Settings, go to Users › System users, create or choose a system user and generate a token with WhatsApp Business management and messaging permissions. It starts with "EAA".

  3. Copy your WABA ID, a 15–16 digit number, from your Meta app under WhatsApp › API Setup, or from Business Suite under Settings › Accounts.

  4. Click Connect on WhatsApp Business, choose whatsapp_auth, paste the System User Token and the WABA ID, and click Connect.

Tip: This integration is for actions like sending messages from automations. It doesn't replace or change your agent's WhatsApp channel. See How to connect WhatsApp, Instagram and Facebook to your agent.

An agent can have only one active connection per app, so a new connection isn't created while the old one is active. Disconnect the app from its card first, then connect it again.

To let the agent insert or update rows, turn on Execute project database query. Execute read-only database query only reads. Because that action runs any SQL, take care:

  • Connect with a database role that can only update the tables and columns the agent needs.

  • Turn on Row Level Security on those tables.

  • Keep the project administration actions off, like changing passwords or API keys.

  • Tell the agent in the prompt exactly what it can update, and never to delete.

A safer option is an HTTP tool that calls a function of your own with only the allowed update. See How to connect your agent to other systems with an HTTP tool.

Some apps have limits set by the provider, or need data the connection doesn't ask for. Check the error in Test Agent. If it continues, contact support with the app name and the exact time of the attempt.

Done

Your agent can now use the apps you connected. Test it after every change to its actions or its prompt.

Need help? Contact support from your platform's home view. Include the app name, the action and the time of the attempt.

Was this helpful?

Still need help? Share an idea