Skip to main content
Two directions, and they are independent:
  • Connectors are things an agent can call - a search API, a mailbox, an issue tracker.
  • Channels are surfaces an agent can be triggered from - a Slack channel, a Telegram bot, a WhatsApp number, the in-app playground.

​
Connectors

Connect a service once in Integrations; its operations then appear as tools any agent can reference. Credentials are stored encrypted per workspace and are validated before they are saved, so a bad key fails at connect time rather than mid-run. Available today: Tavily, Exa, Gmail, Google Calendar, Slack, GitHub, Linear, Notion, Databricks, Salesforce, Apollo, LinkedIn, and Aurora (Solana portfolio). ElevenLabs is the one connector that gives agents no tools. It powers voice in your hosted apps: turn on Voice in an app’s settings and its chat gets a mic button (ElevenLabs speech-to-text, which handles mixed Hindi and English) and a button to hear each reply. ElevenLabs bills your account for both. Gmail and Google Calendar connect over OAuth using your workspace’s own Google OAuth app, not a shared platform one - so consent, scopes, and revocation stay under your control. Several connectors (GitHub, Linear, Notion) are backed by the vendor’s MCP server, which means their tool surface tracks the vendor rather than being reimplemented here.

​
Channels

Inbound webhooks are verified before they run anything - Slack by signing secret, Telegram by a secret token echoed in the request header, WhatsApp by Meta’s signature over the request body. An unverified call never reaches the agent. A channel run is an ordinary run: it appears in AI Monitoring with a full trace. When an agent stops to ask a question or to get an approval, the channel sends the question, and the person’s next message is taken as the answer.

​
WhatsApp on Cruq’s number

You can talk to any of your agents from your own WhatsApp without setting up anything in Meta. Open the agent, press Chat on WhatsApp in its Channels section, and send the code it shows (link CRUQ-7KD2QX) to Cruq’s number. Scan the QR code from your phone, or use the link. The code works once, for 10 minutes. After that, your messages run that agent as you: in your workspace, under your name in AI Monitoring, and against your plan’s run quota. Linking a new code moves your WhatsApp to that agent. On WhatsApp, send:
  • new to start a fresh conversation
  • agent to see which agent you’re linked to
  • unlink to disconnect
  • help for this list
The agent’s page lists the WhatsApp users linked to it, with a Remove button. If you leave the workspace, your link is removed the next time you send a message. This is for you and your team talking to your own agents. For an agent your customers talk to, connect your own WhatsApp Business number (below), so the conversation happens under your business’s name.

​
WhatsApp on your own number

WhatsApp connects through your own Meta app and WhatsApp Business number. You need four values from Meta:
  1. In the Meta developer dashboard, create a Business app and add the WhatsApp use case.
  2. From WhatsApp > API Setup, copy the phone number ID and the WhatsApp Business Account ID.
  3. In Meta Business settings, create a system user, give it the app and the WhatsApp account, and generate a token with whatsapp_business_messaging and whatsapp_business_management, expiry Never. The token on the API Setup page expires within a day.
  4. From App settings > Basic, copy the app secret.
Add a WhatsApp channel to an agent (or a hosted app) with those four values. Cruq checks the number with Meta and subscribes your app to its messages, then shows a callback URL and verify token. Paste both into WhatsApp > Configuration > Webhook in your Meta app, press Verify and save, and subscribe to the messages field. How it behaves:
  • Each person gets their own conversation. On a hosted app they also appear in the app’s Users table.
  • Replies use WhatsApp’s formatting (bold, italic, lists, code). Headings become bold lines and links show their URL. A reply longer than 4,096 characters is split into several messages.
  • Approvals arrive as Approve and Reject buttons.
  • The agent reads text only, for now. Send it a voice note, photo or document and it asks you to type instead.
  • Meta bills your WhatsApp Business account per message, not Cruq. From 1 October 2026 replies are billed too, after the first 1,000 per number each month. Without a payment method in WhatsApp Manager, replies past that stop being delivered.

​
Subagents

An agent can be exposed to another agent as a tool. Delegation is then a normal tool call, so it shows up in the trace like any other step and the child’s run is metered on its own. Use it to keep one agent focused - a router that hands specialised work to specialists - rather than growing a single agent’s tool list until the model loses track of it.