Connectors and connections

A connector describes how to talk to an API: base URL, auth options, headers. A connection is your authenticated instance of one, with credentials encrypted inside your workspace.

The catalog

The connect wizard (on the Connections page) searches a shared catalog of curated connectors, including Slack, GitHub, HubSpot, Notion, and Google Sheets, plus http-generic, the escape hatch for any HTTP API you can authorize with a header. A "Popular right now" rail shows what other workspaces are connecting.

Ways to authenticate

• OAuth. You register your own OAuth app with the vendor, store its client credentials under Settings, Connector OAuth apps, and the wizard sends you through the vendor's consent screen. Tokens refresh automatically; if a refresh fails the connection is marked Disconnected and you can reconnect from its detail page.
• API key. The wizard shows a form for exactly the fields the connector declares, and stores what you submit encrypted.
• Credential login. Some connectors sign in with a username, password, and one-time code to obtain a session token.

AI-drafted connectors

If the wizard finds nothing for your search, it offers to draft a connector with AI for a price shown before you confirm ($0.50 on this deployment). A successful draft joins the global catalog flagged AI drafted, unverified so everyone benefits; platform review can verify it later, and every AI-drafted connector is automatically rechecked monthly. Failed drafts are refunded. Agents can do the same over MCP with generate_connector, or bring their own definition for free with create_connector.

Connection lifecycle

Connections are Pending until authentication completes, then Active. A Disconnected connection (for example after a revoked vendor token) offers reconnect and re-entering credentials on its detail page. Archiving a connection hard-deletes its credentials immediately.

Fixing a broken connector

A connector that 404s or rejects auth (wrong base URL, wrong path prefix, wrong header format, common with a fresh AI draft) never forces you to archive and start over. On the connection's detail page, Fix with AI re-drafts the definition from what you say went wrong plus the connector's recent failed-run errors, for the same price as a draft (a failed fix is refunded by default); Edit definition lets you correct the JSON by hand for free. Either way the change is validated as strictly as at creation, your connections pick up the corrected base URL automatically, and you can retest in the Playground immediately. A failed Playground request even offers the fix dialog directly.

Editing a connector you own applies in place. Editing a shared catalog connector makes a private copy for your workspace; the copy takes over here and the shared one is untouched. Agents close the same loop over MCP: get_connector to read the definition, update_connector (free) or fix_connector (paid) to repair it, then act to retest.