v2026.8.19

Release date: August 26, 2026

---

New Features

contact field on the create-chat API

POST /chat/create reads the recipient from customer based on the channel: WhatsApp uses customer.whatsapp (or phone), email uses customer.email, Instagram/Facebook use the matching ID. Name, document, tags, and custom fields also go in that object.

What is it for?

• Simpler Make, n8n, and other automations: just the number (or ID) and channelId
• Avoid a mismatch between the type you send and the channel you pick
• Find the same customer if the CRM stored instagram and inbound stored instagramId

How to use it?

1. Send contact + channelId (plus the usual optional fields)
2. Official WhatsApp, WAPI, Z-API, WAHA, and EVO treat the value as WhatsApp
3. Instagram and Facebook use the contact ID; email uses the address
4. Use customer for email, phone, WhatsApp, and document
5. Docs: Create Chat

---

Benefits

• Smaller payload, aligned with the channel
• New integrations do not need to guess the type enum
• Customers created by inbound (Instagram/Facebook) are reused when opening a chat via API