Connectors

Connecting one

1. Open Automations → Connectors, or press the plug button in the flow editor, or the + in the chat box.
2. Pick a ready-made connector and sign in with that app, or choose Add custom connector and paste the MCP server URL. Some servers ask for an API key instead of a sign-in.
3. The connector appears in all three places at once. Switch it off there when you want it out of the way; delete it to forget it.

Each connector shows its state: connected a moment ago, never used yet, or could not connect with the reason. A connector whose sign-in expired shows Reconnect; nothing else changes, so your flows and agents keep working once you reconnect.

Where connectors are used

• Chat — the AI can call the connector’s tools while it works for you. Tools that change data ask before running.
• Flows — in the flow editor’s Add Tool panel, the Connectors tab lists your connectors; open one and click a tool to add it as a step. Fill in its fields like any other step, with {{#2.field}} references to earlier steps. A connector step runs when the flow reaches it; there is no approval pause.
• AI agents — give an agent the Connections capability and pick which connectors and tools it may use. The agent lists them with connections_list and calls them with connections_use, asking for your approval before an irreversible action as it does for everything else.
• Functions — backend and account functions see connectors in ctx.connections.list() next to built-in connectors, marked kind: 'connector'.

// Inside a backend or account function
const all = await ctx.connections.list();            // [{ id, name, server, kind: 'app' | 'connector', tools }]
const notion = all.find((c) => c.kind === 'connector' && c.name === 'Notion');
const result = await ctx.connections.call(notion.id, 'search', { query: 'Q3 launch plan' });

Tools and what they do

Next to each tool you see what kind it is: Reads from the app (search, list, get), Changes data in the app (create, update, send) or Deletes data in the app. The list comes from the app itself. If a connector shows no tools yet, press Refresh tools on it, or use it once in a chat.

How careful the AI is with connected apps

In the chat, the menu next to Build has a second part, Action approval. It says how much the AI may do with your connectors before asking you. It is separate from Build and Discuss, which say what the AI works on.

• Ask before every action (the default): every connector action shows a card with what it wants to do; you press Allow or Deny.
• Only ask before changes: reads (search, list, get) run on their own; anything that writes or deletes still asks.
• Don’t ask: everything runs on its own. You still see every action that ran under the reply.

On any card, Always allow this tool whitelists that one tool on that connector, whatever the mode. The choice is remembered on your account. Flows never ask (a step runs when the flow reaches it); AI agents have their own approval setting.

Turning single tools off

On the Connectors page, click a connector to see everything about it: its tools, when you connected it, and buttons to reconnect, refresh the tool list or update its key. Each tool has a switch. A tool that is off is not offered anywhere: not in chat, not as a flow step, not to your AI agents, not to functions. Turn the whole connector off with the switch on its row; the heading counts the active ones.

Serenities’ own actions, without connecting to yourself

The first entry in the flow editor’s Connectors tab is Serenities, its tools grouped by area (Sites, Base, Drive, Flows, AI Agents and so on; open an area or search inside it): everything the platform can do (sites, pages, tables, files, flows, agents, functions, marketplace, sharing) as steps, exactly the tools Claude or ChatGPT get when you connect your own AI. Nothing to sign in to: a step runs as you, on your own things only. The same connection is there for AI agents (connections_list shows “Serenities”) and for functions (ctx.connections.call('Serenities', 'tables_createRow', {…})). The chat does not list it because the chat already has these tools built in.

Good to know

• Sign-ins and API keys are encrypted at rest and never shown again, not to you, not to the AI.
• Only servers reachable on the public internet can be connected; private or local addresses are refused.
• A connector is yours alone. A flow that uses one cannot be sold on the marketplace with your connection inside; buyers connect their own.
• built-in connectors still power the built-in apps in the flow editor’s Tools tab. New integrations arrive as connectors.