Google Sheets
Connect with Google and name one spreadsheet. The agent can read from it or add to it mid-conversation.
- Read a range to look something up
- Append a row to log a lead or a request
- No update or delete, so nothing is overwritten
Three ways to connect
Every tool is off until you switch it on, and its credentials are encrypted and never shown again.
MCP servers
Connect any app that publishes an MCP server, then pick exactly which of its tools the agent may use.
- Notion, Linear, HubSpot, Stripe, Asana and others
- Refresh the tool list when the app adds more
- Switch on individual tools, not the whole server
Your own API
Describe your endpoints once and the agent can call them. There is no JSON Schema to write.
- A base URL and an auth type: none, bearer, custom header or basic
- Operations as a method, a path and up to 10 arguments
- Test the connection before you rely on it
Nothing to wait for. If your tool publishes an MCP server it already works, and if it has an HTTP API you can describe the endpoints you need yourself.
Four tools that need no setup at all
These are on from the first conversation. Everything else stays off until you enable it.
Search the knowledge base
The agent can go back to your material and try different wording when its first answer comes up short.
Look up the customer
It reads the current contact's record, so it answers with what you already know about them.
Tag the customer
It applies an existing tag from your workspace, so conversations sort themselves for later campaigns.
Escalate to a person
It hands the conversation to your team and stops replying. This tool is never withheld.
The agent still answers from your own material
Tools extend what the agent can do, not what it knows. Answers come from the documents, question-and-answer pairs, web pages and business details you upload, and it sends your fallback message rather than inventing one when nothing matches.
For your developers
Trigger sends from your own systems, and get signed notifications back when something happens.
API campaigns
One endpoint and one workspace key to send an approved template from whatever you already run.
- POST /campaign/api
- A payload shaped like the industry standard, so existing integrations port with little change
- Each send resolves or creates the contact and applies tags and attributes by name
- Clear errors for unapproved templates, blocked contacts, opt-outs and inactive subscriptions
- A ready-to-run cURL command on the campaign page, sized to your template
Webhooks
Four events pushed to your endpoint, signed and retried, with every attempt logged.
- message.received
- message.status_updated
- conversation.assigned
- campaign.completed
- HMAC-SHA256 with the timestamp inside the signed material, the same shape as Stripe and GitHub
- Five attempts over about 21 minutes, with stable event IDs so you can de-duplicate
- A delivery log of every attempt, with a retry button when one fails
The campaign API is the only public API. Contacts, conversations and messages are managed in the app and reach your systems through webhooks.
Put your WhatsApp number to work, free for 7 days
Unlimited seats, contacts, messages, campaigns and forms. 2,000 AI replies a month. One plan, everything included. Start today, no card needed.
