WATI

WATI

This connector calls the WATI API v1 on your workspace's own API Endpoint with its access token: message templates, contacts and their attributes, chat history, operator assignment, and sending template, session and interactive messages.

Writes need a yes. Messages go straight to the customer's WhatsApp and template messages are charged by Meta per conversation. Before wati_send_template_message show the template, the number and the parameter values and wait for the user's confirmation; do the same before wati_add_contact and wati_update_contact_attributes. wati_send_session_message, wati_send_interactive_buttons and wati_send_template_broadcast (one template to up to 1,000 numbers per call) are installed switched off: an admin turns them on deliberately, and even then confirm every send. wati_assign_operator only changes the shared inbox.

Setup (about 2 minutes)

1. Sign in to WATI and open API Docs in the menu (newer workspaces: Connector, API).
2. Copy the API Endpoint, e.g. https://live-mt-server.wati.io/123456, into WATI_API_ENDPOINT. The number at the end is your workspace (tenant) id.
3. Copy the Access Token into WATI_ACCESS_TOKEN without the word Bearer in front: WATI shows it as Bearer eyJ..., paste only the part from eyJ on. The token is sent as Authorization: Bearer ... and only to your API Endpoint.

Numbers and targets: WhatsApp numbers are in international format with the country code and without + or spaces, e.g. 919876543210. Where a tool asks for a target you can also pass a WATI contact id.

Templates vs session messages: outside the 24-hour window after the customer's last message WhatsApp only allows approved templates (wati_list_message_templates, then wati_send_template_message); inside the window free text (wati_send_session_message) and buttons (wati_send_interactive_buttons) are allowed. Template parameters are {name, value} pairs whose names match the template's placeholders ({{1}} or {{name}}).

Workflow

• Find people: wati_list_contacts (filter by name, attribute or creation date); read the chat with wati_get_messages. A contact who never chatted answers Can't find Conversation, reported as not found.
• Keep the CRM tidy: wati_add_contact, wati_update_contact_attributes.
• Run the inbox: wati_assign_operator hands a chat to a team member, or back to the bot.
• Reach out: wati_list_message_templates, wati_send_template_message; bulk with wati_send_template_broadcast.

Rate limits: contacts and messages about 10 requests per 10 seconds; template sends 30 to 100 per 10 seconds by plan. A 429 means wait and retry.

Common errors: 401 means the token is wrong, expired or still starts with Bearer; 403 means the token or your plan does not allow this call; 404 usually means a wrong API Endpoint. WATI also answers some failures with HTTP 200 and result: false or ok: false (an invalid number, a template that is not approved); the connector turns those into errors with WATI's text. A successful send means WATI accepted the message, not that it was delivered.

Out of scope here: WATI's newer API v3 (conversation tags and status, channels, campaigns, credits) needs a token that the API Endpoint screen does not give, so it is not used. Also out of scope: creating or deleting templates, scheduled campaigns and CSV sends, media and file messages, list and CTA messages, chatbots, segments, webhooks, WhatsApp Pay, and rotating the token.