Communication · Integration
2Chat
Add 2Chat to your product for your customers, and give your AI agents governed access to it.
2Chat's API is at api.p.2chat.io and authenticates with an X-User-API-Key header. The critical constraint is that it drives a real WhatsApp number linked by scanning a QR code, so a number has to be connected and stay connected before any send or read call works, and a dropped session fails at runtime rather than at setup. Sends go to /open/whatsapp/send-message with from_number, to_number and text, plus a url field for media, and both numbers must be in full international format. Inbound traffic is best handled with webhooks subscribed per event, such as whatsapp.message.received, registered against a specific on_number rather than the account as a whole. Message history reads return the most recent hundred by default with a page_number parameter for older pages, so backfilling a long conversation takes several calls. fastn holds each customer's key, tracks which numbers are connected and keeps webhook subscriptions registered as numbers change.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own WhatsApp number through 2Chat so messages go out from their identity, not a shared sender
Push order or appointment updates to customers on WhatsApp and record the delivery outcome against the record in your app
Receive inbound WhatsApp messages by webhook and route them into your existing inbox or ticket queue
Warn an account owner when their connected number drops its session, before sends start failing silently
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent draft a reply to an inbound WhatsApp message and send it only after a human approves
Have an agent pull the last exchange with a contact to give context before a call, with reads audited per tenant
Ask an agent which conversations have had no reply for over a day on a named connected number
Example prompt
What did we last say to +44 7700 900123 on WhatsApp, and has she replied?
Set up 2Chat in 4 steps
- 01Enable the 2Chat connector from your fastn dashboard.
- 02Have each customer authorise their own 2Chat account, so calls run under their credentials rather than a shared key.
- 03Decide which messages, conversations and participants your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the 2Chat integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a 2Chat integration without building it. Your customers connect their own 2Chat account inside your product and work their messages, conversations and participants there, with no per-customer code on your side.
- Handle the part that actually costs time: anything sent is user-visible, so duplicates and misfires are immediately embarrassing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a 2Chat update is not your on-call problem.
- One integration serves your product and your agents. The same governed 2Chat connection powers in-product features and gives AI agents scoped, audited access, so you put the right message in front of the right team automatically without wiring it twice.
Used by these teams
Compare with
Slack
Microsoft Teams
TwilioOften used alongside
Tools the same teams tend to run next to 2Chat, across other categories.
Aircall
Calendly
Gong
Google Calendar2Chat integration FAQ
How do I add a 2Chat integration to my product?
Enable the 2Chat connector in your fastn dashboard, then let each customer authenticate their own 2Chat account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no 2Chat client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own 2Chat account?
Yes. Every connection is scoped to the individual customer, so each authorises their own 2Chat account and only ever sees their own messages, conversations and participants. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this 2Chat integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent draft a reply to an inbound WhatsApp message and send it only after a human approves
Who maintains the 2Chat integration?
fastn does. When 2Chat changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does each customer connect their own 2Chat account?
Yes. Every customer authorises their own 2Chat account, so messages, meetings and notifications originate from their workspace under their permissions. You never proxy through a shared account, which also means a customer revoking access affects only their own connection.
How are duplicate notifications avoided?
Sends are deduplicated per event, so a retry after a network failure does not post the same message twice into a channel people are reading.
What can I build with the 2Chat integration?
A common starting point: let a customer connect their own WhatsApp number through 2Chat so messages go out from their identity, not a shared sender. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the 2Chat integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding 2Chat does not change your per-connector cost. You can start free with 3 connected accounts.
Add 2Chat to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.