CRMEspoCRM WhatsApp Integration
Open-source CRM in the inbox sidebar and in the chatbot builder.
EspoCRM is supported in two ways at once. It runs as a mini app in the team inbox, docking the matching lead, contact or opportunity beside the conversation for agents to read and edit. And it is available as a chatbot-builder node, so a flow can push or retrieve records in real time without an agent involved. Because EspoCRM is open source and usually self-hosted, the data stays on infrastructure you control.
Libromi Connect
WhatsApp Business Platform
EspoCRM
Two-way connection
Where it shows up
- Inbox sidebar mini app
- Chatbot builder node
- Team inbox
- Webhooks & REST API
You chose a self-hosted CRM, then bolted a cloud chat channel onto it
Teams run EspoCRM precisely because they want the customer database on their own infrastructure. Then the busiest channel — WhatsApp — sits outside it, and the compromise begins: exported spreadsheets, manual re-entry, or a middleware script nobody maintains. The integration exists so the channel reaches the CRM without any of that.
What moves, and which way
EspoCRM to WhatsApp
Leads, contacts and accounts
The matching record opens in the sidebar, keyed to the conversation's phone number.
Opportunities and cases
Agents see open opportunities or support cases before they reply.
Values a flow can read
A chatbot node retrieves record fields and branches on them mid-conversation.
WhatsApp to EspoCRM
Record creation
A flow creates a lead, contact or case from the answers it collected, in real time.
Field updates
What the customer says updates the record while the conversation is still open.
Notes and activity
Conversation outcomes are written back so the CRM history is complete.
The sidebar app and the chatbot node act on the same EspoCRM instance — yours.
What you get
Sidebar mini app
The EspoCRM record for the person you are chatting to opens beside the conversation, ready to read and edit.
Chatbot-builder node
Push and retrieve EspoCRM records from inside a flow, so automation does not depend on an agent being present.
Your own instance
EspoCRM is typically self-hosted, so the customer database stays on infrastructure you control.
REST for anything custom
Custom entities and fields that go beyond the standard actions are reachable with a REST block.
What you can build with it
Support cases opened from chat
When a customer reports a problem, a flow creates the case in EspoCRM with the details and links it to the right account.
Lead capture without data entry
The chatbot qualifies and writes the lead directly, so the sales team starts from a populated record.
Answers drawn from the CRM
A flow retrieves the account's plan, renewal date or open case and answers from that rather than routing the question.
A services firm running EspoCRM on its own servers
The company keeps its client database in-house for compliance reasons, but client requests arrive on WhatsApp. Requests were being emailed internally and re-entered into EspoCRM by an admin, adding a day to every ticket.
The result
Requests reach the CRM the moment they are made, with no admin in the middle and no data leaving the company's own servers.
- 1
A client messages the company number; the flow identifies them from the phone number in EspoCRM.
- 2
It asks what the request concerns and creates a case in EspoCRM against the right account.
- 3
The conversation is routed to the team that owns that case type.
- 4
The agent works the case in the sidebar app while replying, and closes it without leaving the inbox.
How to connect it
- 1
Connect your instance
Point Libromi Connect at your EspoCRM installation and authorise it with an API user.
- 2
Map entities and fields
Decide which EspoCRM entities the sidebar opens and which fields the flow reads and writes.
- 3
Use both surfaces
Enable the mini app for your agents and add EspoCRM nodes to the flows that create or fetch records.
Frequently asked questions
Related integrations
Teams that connect this one usually connect these too.
Connect your own CRM
Bring EspoCRM into the inbox and the chatbot at the same time.