Integrations · MessagingConnect WhatsApp to Well
Pull thread, attachment, sender, and business account out of WhatsApp threads into structured workspace records, with the original conversation linked.
What Well pulls from WhatsApp
WhatsApp feeds thread, attachment, sender into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke WhatsApp’s access.
| From WhatsApp | In Well | Relation | |
|---|---|---|---|
| Thread | Audit trail | Captures as | |
| Attachment | Document | Extracts as | |
| Sender | Person | Resolves to | |
| Business account | Workspace context | Groups under |
- Sync mode
- on-demand
- Refresh
- queried on request
- Direction
- WhatsApp → Well
What Well does with your WhatsApp connection
Connect
Connect WhatsApp over WhatsApp Business token: there is no server credential to WhatsApp; the browser extension captures only what you send from the page you trigger it on.
Sync
Well brings thread, attachment, and sender in from WhatsApp on demand, only when a question or an agent asks for them. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each WhatsApp entity into audit trail, document, and person, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from WhatsApp lands in the workspace as audit trail, document, and person you can search, chart, and automate.
Questions WhatsApp unlocks
Ask in plain language. Well answers from your connected WhatsApp connection, resolved against the rest of your stack.
Ask anything about your WhatsApp connection
Ask about your WhatsApp connection…
Connect WhatsApp in three steps
- 01
Install the Well browser extension
Install Well's extension from the Chrome or Edge store and pin it to your toolbar. The extension is the connector, there's no per-WhatsApp API authorisation. When you browse to a WhatsApp page or thread, click the extension to capture the content into Well.
- AuthWhatsApp Business token
- Capture modeon-demand
- 02
Map your entities
Captured payloads land in your workspace with the source URL, timestamp, and extracted fields preserved. Well structures them into vendor / amount / participant / context, depending on what the page contained.
- Mappingpreconfigured by Well
- 03
Use the data
Use captured records in conversation or in records tables. There's no background sync, WhatsApp sees only the captures you explicitly trigger.
- First syncstarts as soon as connect completes
The extension only sends data when you click capture. Uninstall any time; in-flight captures still land, no new ones queue up.
How WhatsApp stays secure with Well
Well captures WhatsApp thread, attachment, sender, and business account through your browser extension. No persistent server-side auth to WhatsApp; the extension sends data only when you click capture, and only what's on the page you triggered it from.
- granted
Read WhatsApp records
Endpoints the WhatsApp API token grants, scoped by your consent.
- granted
Resolve thread, attachment, sender, and business account across your stack
Match identifiers in WhatsApp against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete WhatsApp records
Not granted; WhatsApp is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store WhatsApp passwords or session cookies
Authentication runs through WhatsApp Business token tokens we never see.
Frequently asked questions about WhatsApp and Well
WhatsApp doesn't expose a public connector API for this use case. Well's browser extension captures structured content as you browse, sends it to your workspace, and links it to the relevant WhatsApp thread or page. Install the extension once, pin it to the browser toolbar, and capture on demand.
Well brings in thread, attachment, sender, and business account from WhatsApp and reshapes each entity into your workspace: thread becomes audit trail; attachment becomes document. Every record arrives with the source identifier preserved, so WhatsApp stays the source of truth while Well lets you query the data alongside the rest of your stack.
Conversations in the channels you watch get parsed for commitments, deadlines, and decisions. Each surfaced action item becomes a workspace record with the original WhatsApp thread linked, the assignee resolved to a team member entity, and a due date when one's stated. Asking "what did we promise customers in WhatsApp last week" returns the open commitments as a queryable list.
Yes. WhatsApp business accounts are indexed in your workspace as workspace context, so questions like "show me last week's business accounts from WhatsApp" return them with the original WhatsApp link, the workspace context, and any related records (counterparty, period, attached document) joined inline.
WhatsApp is queried on demand when you ask a question that needs thread, attachment, sender, and business account, or when an agent in your workspace requests them. There's no background polling, so WhatsApp sees only the traffic your team's queries generate.
Uninstall the Well extension from your browser. Already-captured thread, attachment, sender, and business account stay in your workspace; the extension stops sending new captures the moment it's removed.
WhatsApp records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.
Pairs well with WhatsApp
More in Messaging
Popular cross-category
Ready to connect WhatsApp?
Connect once. Every thread, attachment, sender from WhatsApp becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.