Connector directory
What your agents can connect to
Every connector below ships with the platform and is reviewed before it can run. Open one to see everything it does - each operation, its inputs, and the safety rules it follows. Consequential operations wait at approval gates.
Slack
Connect your accountPost messages to Slack with your own workspace bot token. Connect a Slack account under Connections, then use this block to send a message to a channel.
1 operation
GitHub
Connect your accountCreate issues and comments on GitHub with your own personal access token. Connect a GitHub account under Connections first.
2 operations
Notion
Connect your accountCreate pages in a Notion database with your own integration secret. Connect a Notion account under Connections and share the target database with your integration first.
1 operation
Airtable
Connect your accountCreate and list records in an Airtable base with your own personal access token. Connect an Airtable account under Connections first.
2 operations
Discord
Connect your accountSend messages to a Discord channel with your own bot token. Connect a Discord account under Connections and invite the bot to your server first.
1 operation
Google Sheets
Connect your accountAppend rows to a Google Sheet using a service-account key. Connect a Google Sheets account under Connections by pasting the service-account JSON, then share the target sheet with the account's client_email.
1 operation
HTTP
Built in - no setupCall an external HTTP API endpoint. Use this when a workflow needs data from, or must notify, a service that exposes a JSON or text HTTP interface. Private, loopback, link-local, and cloud-metadata address ranges are denied by default.
1 operation
Clock
Built in - no setupRead the current instant. Use when a workflow needs a timestamp for records, messages, or time-based branching.
1 operation
Random
Built in - no setupGenerate cryptographically random identifiers. Use for correlation ids, idempotency keys, or unique references.
1 operation
Agent data store
Built in - no setupThis agent's own durable data store. Records persist across runs and belong to the agent, not to a chat transcript — use it to keep expenses, tallies, watchlists, or any working records the agent needs to remember. Data is reachable only through this agent; draft tests and published runs share the same store. Bounded: values up to 8 KiB, 2000 records per agent.
4 operations
More connectors are on the way, including MCP-based ones. Operators can also import community connector manifests, which go through review before agents can call them.