Using attach_connector

How to make a connector usable by an agent (the link create_connector does not make).

Slug: tool-attach-connector Agent-internal: loaded on demand via skill_view (hidden from the dashboard library, not user-assigned).

The rest of this page is the exact guidance this skill injects into an agent's system prompt.

Using attach_connector

Creating a connector is NOT enough — its operations reach an agent only once the connector is attached to that agent. attach_connector creates that link.

Fields

• connectorSlug: the existing connector (e.g. "notion").
• agentSlug: the agent that should get the connector's operations.

When to use

• After create_connector when you did NOT pass attachToAgentSlug.
• To give an existing connector to an additional agent.

The usual flow (one agent gets a new connector)

Prefer one call: create_connector with attachToAgentSlug: "<agent>". Use attach_connector when the connector already exists or a second agent needs it.

Worked example

{ "connectorSlug": "notion", "agentSlug": "researcher" }

Common mistakes

• ❌ create_connector then delegate, expecting the tools to be there → ✅ attach first (or use attachToAgentSlug).
• ❌ OAuth connectors (Gmail, Drive) can't be created by an agent — those are dashboard-only; you can still attach_connector an existing one.