Request an integration
Ask for a tool that isn't connected yet, and what to do while you wait.
The available list in Settings → Integrations has a Request button on every integration that isn't connected. Requesting one tells us you need it and which workspace needs it.
Make the request useful
A request that says what you'd do with it gets built for the right shape. Worth including:
- The workflow. "Score every support call" is more actionable than "connect Zendesk".
- Read or write. Reading records is a different piece of work from writing back.
- The objects you need. Deals and contacts, or tickets, or campaign members.
- Volume. A few hundred records a month and a few hundred thousand are different problems.
While you wait
Three routes that often get you there sooner.
1. An MCP server
If the system has an MCP server — or your team can stand one up — connect it under Settings → MCPs and agents can use its tools directly. See MCP connections.
This is the fastest path for internal systems, which are never going to be in a public catalog.
2. Route through something already connected
Often the data already flows somewhere you can connect. Support conversations exported to Drive, calls recorded through a connected provider, records synced into your CRM by an existing tool. One hop through a connected system beats waiting.
What not to do
Don't paste exported data into an agent's instructions as a workaround. It goes stale immediately, it inflates every run's cost, and it lands in the run logs. Use a document store for reference material instead.