Messaging

AI agents that use WAHA (WhatsApp)

UtilitySpaces gives an AI agent scoped access to WAHA (WhatsApp) through its own encrypted connection, not your password. The agent can call 3 named WAHA (WhatsApp) tools, and the 2 that write wait for a person's approval unless an admin has set the connection to run without asking. Every call is written to a hash-chained audit log with its arguments and its result.

What an agent can do in WAHA (WhatsApp)

Send and check WhatsApp messages via a self-hosted WAHA session. An agent calls these by name, and matching is exact.

Every tool a WAHA (WhatsApp) connection exposes, and whether it writes, which waits for approval by default
Tool	What it does	Waits for approval by default
Session status	Check WhatsApp session connection status.	No — read only
Send text message	Send a WhatsApp text message.	Yes — it writes
Send image	Send a WhatsApp image with an optional caption. `file` is {mimetype, filename, url} or {mimetype, filename, data} where data is base64.	Yes — it writes

1 read tool, 2 write tools. Generated from the connector catalogue the product runs on, so it cannot list a tool that does not exist.

What teams hand an agent in WAHA (WhatsApp)

Teams that live on WhatsApp hand an agent the sending half of the job: the agent writes the message, checks the session is connected with Session status, and sends it. Send text message and Send image are both writes. A WAHA connection made before write policies existed was kept on Run without asking, so there a message reaches a customer's phone without a person reading it first; a new connection starts on Ask a person first, and an admin can switch either one.

Confirm the WhatsApp session is still connected each morning with Session status, and raise it in the channel before the team starts relying on it.
Send the order confirmation or delivery update to the customer's number when the matching event happens (unattended only if the connection runs without asking)
Send an image such as an invoice or a product photo with a caption to a customer who asked for it (after a person approves it, unless the connection runs without asking)

Before you let it write, or keep out: WAHA drives a real WhatsApp account through an unofficial client, and numbers that message people who never asked get banned. On a connection set to run without asking, sends go out without review, so never point an agent at a list of numbers that did not opt in.

What waits for a person

Reads run on their own. These do not — each one waits in Approvals for an owner or admin unless an admin has set this connection to run writes without asking, and every call toWAHA (WhatsApp), approved, rejected or unattended, is logged.

Send text message POST
Send image POST

What connecting WAHA (WhatsApp) takes

WAHA (WhatsApp) uses an API key you create in WAHA (WhatsApp) and paste in once. A workspace admin sets the connection up; the fields are:

WAHA URL
API Key
Session name

Credentials are encrypted and bound to your workspace, never read back, and every outbound call passes one guarded fetch — the connector security posture sets out exactly how, and the security page covers the platform around it.

Where WAHA (WhatsApp) fits

Give an agent WAHA (WhatsApp) work by writing a message in the inbox, or put its tools in a scheduled flow. What the run cost is on the cost breakdown.

Other messaging integrations: Chatwoot, Discord, Gmail. Or see every application agents can connect to.

See it doing your actual work

Open a demo workspace, connect one app, and give an agent a real job. No card, no sales call.

Try the demo See pricing

We reply to every message within one business day.