Integrations
A chatbot replies. IgnacIA resolves.
The agents read and write in the systems you already run. They check an order status, book a slot, open a ticket or record a detail while the conversation with the customer is still open.
For companies already running a CRM, an ERP or a booking calendar that don't want one more island to sync by hand.
- Reads and writes in your systems
- Connected over API or webhook
- You define what it can run
- Permissions and a log per action
Types of integration
The systems named here are examples of what can be connected over an API, not certified out-of-the-box integrations. Every connection is built and tested against your own instance.
CRM
Read the customer's history before answering, and create or update contacts, opportunities and notes. Connected through your CRM's API.
ERP and management systems
Check availability, prices, the status of an order or a work order, and record movements straight from the conversation.
Calendars and booking systems
Read real availability, book, reschedule and cancel appointments while respecting each calendar's and each professional's rules.
E-commerce
Look up products, check a shipment's status and handle exchanges or returns on the online store you already have.
Databases
Read-only queries against your databases so answers carry hard facts: balances, reference numbers, statuses, service history.
Your own APIs and webhooks
If your system is custom-built, the agent calls its API or fires a webhook to your backend. That's the path for everything that isn't standard.
From conversation to action
Having the connection isn't enough: you have to define when to use it and how far it can go. Here's how that's set up.
Declared actions, not free rein
Each integration is exposed to the agent as a bounded set of actions — "check order", "book slot", "open ticket" — with their parameters. The agent picks among those; it can't invent one.
Permissions per action
You define what it can read and what it can write in each system, using credentials that belong to the agent. Anything not enabled doesn't run, and every action is logged with its result.
Confirmation and human handoff
Actions that change data are confirmed with the customer before they run. If something fails or the case falls outside what's declared, the agent says so and hands off instead of inventing a result.
The difference between replying and resolving
Conversations that close
The customer leaves with the problem solved, not with "a rep will contact you".
No double data entry
Whatever is agreed in the chat is written to the system right then, without anyone having to copy it over later.
One version of the truth
The agent answers with the information sitting in your systems today, not with a copy someone refreshed last month.
Hard facts, instantly
Checking a status stops being an internal ticket: the agent looks it up and answers in the same conversation.
Integrations serve every channel
The same action — book, quote, look up, record — runs identically from WhatsApp, from the chat on your site or from a phone call.
Don't see your system here? Tell us what it is and we'll review its API with you before promising anything.
Which systems do you want connected?
Tell us what you run today and we'll work out together which actions the agent can take in your operation.