Wati
Wati is a WhatsApp Business API platform that automates marketing, sales, service, and support.
Verdict
Common use cases
- Register new leads from live chat
- Send order confirmations via WhatsApp
- Update customer attributes after support calls
- Retrieve team assignments for routing
- Deliver session messages during active windows
Integration
- Vendor
- Wati
- Category
- other
- Auth
- API_KEY
- Tools
- 5
- Composio slug
wati
Tools
- Add Contact
Tool to add a new contact in wati. use when registering a customer's whatsapp number before sending messages.
- Get Teams
Tool to retrieve a list of teams from wati. use after authenticating when you need to enumerate all available teams.
- Send Session Message
Tool to send a session message to a specified whatsapp number. use when you need to deliver a free-form text within an active 24-hour session window.
- Update Contact Attributes
Tool to update attributes of an existing contact. use after confirming the contact exists and you need to modify its custom attributes.
- Wati update chat status
Deprecated action placeholder for updating chat status.
Setup
Setup guide
- 11. In Switchy, open the Space where you want to use Wati and click 'Add Integration' in the sidebar. 2. Search for 'Wati' and select it from the MCP catalog. 3. You'll be prompted to enter your Wati API key — find this in your Wati dashboard under Settings > API Docs > Access Token. 4. Paste the key and click 'Connect'; Switchy will verify the token and list the five available tools. 5. To test the connection, type '@Wati get teams' in the Space chat — you should see a list of your Wati teams returned inline. 6. To invoke any tool, @mention Wati in a message and describe what you need (e.g. '@Wati add contact for +1234567890 named Jane Doe'); the AI will map your request to the correct tool and parameters.
What teammates see: by default, memories from Wati are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Register New Lead
@Wati add a contact for phone number +14155552671 with the name Sarah Chen and custom attribute 'lead_source' set to 'website_demo'.Open in a Space →
Send Order Update
@Wati send a session message to +14155552671 saying 'Your order #4523 has shipped and will arrive by Friday. Track it here: example.com/track'.Open in a Space →
Update Contact Tier
@Wati update the contact at +14155552671 to set the custom attribute 'account_tier' to 'premium' and 'renewal_date' to '2025-06-15'.Open in a Space →
List All Teams
@Wati get the list of all teams in my Wati workspace and show their names and IDs.Open in a Space →
Bulk Contact Prep
@Wati add three contacts: +14155552671 named Sarah Chen, +14155552672 named Mike Torres, and +14155552673 named Priya Kapoor, all with 'campaign' attribute set to 'spring_promo'.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@wati add a new contact for +1-555-0198 with name Sarah Chen and tag them as 'trial-user' so we can send onboarding messages
Contact created successfully. Sarah Chen (+1-555-0198) is now registered in your Wati workspace with the 'trial-user' tag applied. The contact is ready to receive WhatsApp messages. Note that you'll need an active 24-hour session window to send free-form messages, or you can use approved template messages outside that window. The contact ID has been stored and can be referenced for future attribute updates.
This example shows the prerequisite step before messaging: registering a WhatsApp number in Wati's system. You must add contacts before sending them messages. Be aware that Wati enforces WhatsApp's session rules—free-form messages only work within 24 hours of the customer's last reply.
@wati send a session message to +1-555-0198 saying 'Your trial expires in 3 days. Reply YES to upgrade or HELP for questions.'
Session message delivered to +1-555-0198. The message was sent successfully within the active 24-hour session window. Wati confirms delivery to WhatsApp's servers, though read receipts depend on the recipient's privacy settings. If this contact replies, a new 24-hour session window opens automatically. Outside the session window, you'd need to use a pre-approved template message instead of free-form text.
This demonstrates Wati's core messaging capability, but only works if the contact messaged you in the last 24 hours. Outside that window, WhatsApp blocks free-form messages and you must use template messages approved by Meta. Always check session status before attempting to send.
@wati pull all teams from our workspace, then update Sarah Chen's contact attributes to set 'subscription_tier' to 'pro' and 'renewal_date' to '2025-06-15'
Retrieved 4 teams from your Wati workspace: Sales (12 members), Support (8 members), Onboarding (5 members), and Retention (6 members). Then updated Sarah Chen's contact record with subscription_tier='pro' and renewal_date='2025-06-15'. These custom attributes are now available for message personalization and segmentation. You can reference these fields in template messages or use them to filter contacts for broadcast campaigns.
This example chains two operations: enumerating workspace structure, then enriching contact data with custom attributes. Custom attributes let you personalize messages and segment audiences, but you must define the attribute schema in Wati's dashboard first. Attribute updates are immediate and don't trigger notifications to the contact.
Use-case deep-dives
When Wati wins for customer onboarding sequences
A 6-person SaaS team running onboarding flows over WhatsApp needs to register contacts, send session messages during the 24-hour window, and update attributes as users progress through steps. Wati's MCP handles this if your onboarding logic lives in Switchy and you're already paying for Wati's platform. The session message tool works only within the 24-hour window after a user replies, so this breaks down if your drip needs multi-day gaps or proactive outreach beyond that window. If your flow is tightly sequenced and user-initiated, Wati keeps the contact sync and message dispatch in one place. If you need broadcast or template messages outside the session window, you'll hit the API's limits and need Wati's dashboard anyway.
When this MCP fits support escalation workflows
A 3-person support team triaging tickets in Linear wants to escalate high-priority cases to WhatsApp for faster resolution. Wati's MCP lets you add the contact, retrieve the assigned team, and send a session message without leaving Switchy. This works if the customer has messaged you recently and you're within the 24-hour session window. If the ticket sits overnight or the customer hasn't initiated contact, the session message tool fails and you're back in Wati's UI to send a template. The MCP shines for same-day escalations where the conversation is already warm. For cold outreach or delayed follow-ups, the session constraint makes this a partial solution at best.
When Wati handles event RSVP workflows
A 4-person events team collecting RSVPs over WhatsApp needs to register contacts, confirm attendance, and update custom attributes like dietary preferences. Wati's MCP automates the contact creation and attribute updates from Switchy if your RSVP flow is conversational and happens in real time. The session message tool works for immediate confirmations, but if you need to send reminders days later, you're outside the 24-hour window and the MCP can't help. This setup fits live registration desks or same-day RSVP campaigns. For multi-day event sequences or reminder cadences, you'll need Wati's broadcast features, which aren't exposed in the MCP, making this a day-of-event tool rather than a full campaign manager.
Frequently asked
What does the Wati MCP let me do in Switchy?
It connects your Wati WhatsApp Business account so AI agents can add contacts, send session messages, update contact attributes, and retrieve team lists. Use it when you want agents to handle WhatsApp outreach or customer data updates without switching between tools. The MCP wraps Wati's API so agents can trigger WhatsApp actions directly from chat.
Do I need a Wati API key to set this up?
Yes. You'll generate an API key from your Wati dashboard under Settings → API. Paste it into Switchy when you connect the MCP. No OAuth flow—just the key. Anyone on your team with Wati admin access can create the key; you don't need to be the account owner.
Can the Wati MCP send WhatsApp messages outside the 24-hour window?
No. The Send Session Message tool only works within WhatsApp's 24-hour session window after a customer replies. If the window closed, you'll need to send a template message instead—which this MCP doesn't expose yet. For cold outreach, use Wati's dashboard or a separate template-message integration.
How is this different from just using Wati's dashboard or API directly?
The MCP lets AI agents trigger Wati actions mid-conversation without you writing code or switching tabs. If you're already scripting against Wati's API, this won't add much. If your team wants agents to handle WhatsApp workflows autonomously—adding contacts, updating attributes, sending messages—the MCP saves you from building that glue yourself.
Who on my team should connect the Wati MCP?
Whoever manages your WhatsApp campaigns or customer data in Wati. They'll need access to generate the API key and understand which contacts and teams exist. Once connected, any Switchy user in your workspace can invoke the tools—so decide whether you want that level of access before sharing the integration.