Waboxapp for AI agents
Waboxapp connects WhatsApp messaging into CRM systems, used by sales and support teams centralizing customer conversations from WhatsApp. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Waboxapp.
Receive an incoming message event
Read an incoming WhatsApp message event as it arrives, a read-only event feed.
Check delivery acknowledgment
Look up whether a sent message was delivered, a read-only status check.
Route a message into the CRM
Pass an incoming WhatsApp message into a CRM record for the right customer.
2 Waboxapp actions, graded by risk.
Every Waboxapp action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
0Look things up. Allowed by default.
- No read actions.
write
2Create and change things. Allow, or ask the user first.
- waboxapp.webhook_ack_eventWaboxapp Webhook ACK Event
- waboxapp.webhook_message_eventReceive incoming WABOXAPP message event
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Waboxapp in three steps.
- 01Your users connect WaboxappThey add their Waboxapp api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “waboxapp Webhook ACK Event” can wait for the user to approve.
- 03Any agent can actYour agent calls Waboxapp through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('waboxapp', { read: 'allow', write: 'ask', // webhook_ack_event destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Waboxapp connects.
Users add their Waboxapp api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Waboxapp connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Waboxapp from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Waboxapp and Arc0, answered.
Can I use Waboxapp with Claude, ChatGPT or Cursor?
Yes. Connect Waboxapp to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Waboxapp actions you allow.
How do users connect Waboxapp?
Users add their Waboxapp api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Waboxapp actions can my agent take?
2 in total: 0 read, 2 write and 0 destructive, such as “waboxapp Webhook ACK Event”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Waboxapp?
Yes. Allow read actions and deny writes in the Waboxapp policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Waboxapp too?
Yes. The same Waboxapp connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Waboxapp into your agent.
Your users connect Waboxapp once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan