Integrations

Open Integrations

Open Integrations from Cheqq. The catalog has five tabs:

Tab	What lives there
Apps	Providers you sign in to — Google, Microsoft, and the managed MCP catalog
Channels	The Cheqq bot in Slack, Telegram, or Discord — see Channels
MCP Servers	The MCP catalog, plus any server you add by URL
Connections	REST APIs you call from a workflow step or from chat
Mail servers	SMTP logins for sending from your own address

The MCP Servers tab is a browsable catalog of 40+ providers — Linear, Notion, GitHub, Stripe, Atlassian, Airtable, and more. Each connects per-user through the provider's own authorization screen; Cheqq never sits between you and the provider with a shared client. Open servers like Hugging Face and DeepWiki need no account at all and connect in one click.

The full list, and what Cheqq can do with each service, is in the Integrations reference.

Connect a service

Choose an integration from the catalog and open its detail card.

Select Connect.

For OAuth integrations, a popup opens the provider's authorization screen — review what it's requesting and approve it there. For API-key or MCP integrations, fill in the inline form Cheqq shows instead.

Return to Cheqq and confirm the integration shows as Connected.

Only grant access you're comfortable using in chat, Wapps, and automations. If your browser blocks the popup, or you close it before finishing, the connect attempt simply resets — reopen it and allow the popup to try again.

A sign-in has 15 minutes to finish, which leaves room for switching accounts or passing two-step verification. If it opens in a tab rather than a popup, the tab says whether the connection worked and what to do next.

Call any REST API with a Connection

A Connection is one saved way of calling an API — its base URL, how it authenticates, and any fixed headers it needs. The same connection is used by a workflow's API call step and by your agent in chat, so anything you can automate you can also just ask for.

Open the Connections tab and select New connection — or start from a preset, which fills in a known provider's URL and auth for you.

Give it a base URL and choose how it signs requests: an OAuth app you register, a stored key (bearer, basic, or API-key header), or nothing at all for an open API.

Optionally import an OpenAPI spec — Cheqq reads the endpoints and lets you pick the ones you want, rather than typing paths by hand.

Test an endpoint from the detail view before saving it.

Saved endpoints load as tools your agent can call, so "how many open tickets do we have in that system?" works without building a workflow first. You can also ask in chat to test a saved endpoint, remove one, or disconnect the API; removing and disconnecting ask you first. When Cheqq connects an API in chat, it can use a key you've already saved, such as one an API step uses, so the key never goes into the conversation. For a new key, see the next section.

Add an API key from chat

Ask Cheqq to connect a service it doesn't have a key for — "pull last week's payments from Stripe" — and a key form appears in the conversation instead of a request to paste it.

Read what the key is for. When there's a link, Where to find your … key opens the page in that service's dashboard where you create or copy it.

Paste or type the key. It stays hidden as dots; Show key reveals it while you check it.

Press Enter or select Save key. Cheqq carries on with the request using the saved key.

The key is stored encrypted with your other keys, under a name like "Stripe API key". The AI never sees it, and it never appears in the conversation or its history: Cheqq only learns which saved key to use. Choose Cancel (or press Esc) if you'd rather not add one now, and Cheqq tells you what it can do without it. The form works the same in the phone app.

In Slack, Telegram, Discord or WhatsApp there's no form to fill in, so Cheqq asks you to add the key under Integrations in Cheqq instead, then picks it up from there. Never paste a key into a chat message.

Connections are read-only until you say otherwise

A new connection can read but not write. Turn on Allow writes in its detail view to permit anything beyond GET. In chat, each request that changes something then goes through tool approval: Manual asks you before it runs; Auto runs it without asking.

A connection's key is rotated from that connection's own detail view. A workflow step that authenticates with a bare key can create one in place rather than sending you to another page first.

Send from your own address

Mail servers holds SMTP logins — the one secret that isn't an API's key. Add a mail server here and a workflow's Send Email step can send from your real address instead of a cheqq.ai one. Your settings are verified when you save them, so a wrong host or password fails in the form rather than days later inside a run. See Send email.

Connect your own OAuth app or MCP server

Beyond the built-in catalog:

Custom App — register your own OAuth 2.0 client: app name, authorize/token URLs (must be HTTPS), client ID and secret, and optional scopes. Cheqq shows you the exact redirect URI to register with your provider. Changing the client secret later invalidates the existing connection and requires reconnecting. You can register one directly from the connection form when a connection needs it, rather than leaving to set it up first.
Custom MCP — add a server by name and URL. Cheqq probes it, discovers its tools, and starts an OAuth or API-key flow automatically if the server requires one. A server that can't be reached says why. A server that isn't active can be removed. In chat, Cheqq can list your MCP servers with their status and tools, and remove one you connected after asking you.

Reconnect or disconnect

Open the integration detail when a connection shows Reconnect — this happens when a token expires or the provider revokes it — and connect it again from there to renew authorization. Use Disconnect (or Remove, for MCP servers, which also deletes the registration) when Cheqq should no longer access the connection; its tools stop being available immediately.

Use a connection

Connected services make relevant actions available where the product exposes them. The tools available to a chat or automation depend on its current context and configuration — a connected service does not make every provider action available everywhere.

With Gmail connected and allowed to send, the agent can email from your own address in chat and in Slack or Telegram threads, with each email waiting for your review first. See Send email from your Gmail.

Web research needs no connection at all: the agent can always search the web and read public pages.

If authorization does not complete, allow the provider popup and see Troubleshooting.