Integrations
What systems does Eva connect to?
The question behind this page is rarely "how many integrations do you have". It is "will it quote from the prices that live in my system, or will it make one up?" A wall of logos does not answer that. It says somebody, once, connected something.
Here is what Eva connects to, with an honest label on every row. Native means the connector exists in the product today and is switched on from configuration. Custom means it gets built during your implementation, on the same primitive other customers already run on. Nothing on this list is decorative.
What the labels mean
Native: the connector already exists in Eva and is set up from your account or agent configuration. No development in between: you grant access and it is done.
Custom: there is no ready-made card, but there is the piece that builds one. If your system has an API, you configure the base URL, the authentication and the actions Eva may call. It is assembled during onboarding, not after months of waiting.
Integrations
Native
WhatsApp Business
Your WhatsApp Business number becomes an agent channel: Eva receives and answers there, and your team can take the conversation over from the inbox. Outside WhatsApp's window, reopening needs an approved template.
Native
Direct messages from your Instagram account reach the same agent and the same inbox. Outside the window Instagram has no compatible reactivation path: the send is skipped and the event is recorded.
Native
Messenger
Messages from your Facebook page reach the same agent, with the same catalog and CRM tools. As with Instagram, outside the window the send is skipped with a visible event.
Native
Website widget
Eva's chat embedded in your site, with history, attachments and streamed replies. The site origin is validated against the allowed configuration, and the composer takes up to ten files of ten megabytes each.
Native
API channel
If you have your own application, the agent's conversations are consumed as an API. Delivery defaults to polling the events endpoint; if you prefer push, you configure a signed webhook from the agent's deploy screen.
Native
Shopify
You connect your store over OAuth and it becomes the agent's catalog source, with product webhooks and media from active, published products. A Shopify-sourced catalog is read-only inside Eva: the store is in charge.
Native
Google Calendar
The agent checks real availability, suggests times and books. Whatever is already busy in Google Calendar blocks the slot through Free/Busy, so Eva does not stack a booking on top of something that already existed.
Native
Stripe
It powers Eva Pay: a Stripe Express account per agent creates the SPEI bank-transfer payment link in Mexican pesos inside the conversation and records the payment cycle. This version does not create card payments.
Native
Facturapi
A confirmed payment triggers the Mexican CFDI invoice for eligible charges, and the PDF and XML are kept. It needs a complete tax profile, a valid Facturapi and CSD configuration, and SAT data on the line items.
Native
Dropbox
A Dropbox folder syncs into the agent's knowledge base, with retries when a file fails. The cap is 300 MiB per file, inside a per-agent quota of 20 GB and 20,000 files.
Native
Gmail
You connect a Gmail account over OAuth and inbound mail syncs into the email inbox, where it shows up as a conversation your team reads and answers without leaving Eva.
Native
Tokko Broker
For real-estate teams, Tokko Broker connects as the agent's external CRM from the account catalog. The link is one agent per connection: there is no multi-agent assignment from settings.
Custom
Your ERP or internal system
The custom API primitive covers private ERPs, internal systems and your own APIs. You configure the base URL and the authentication — none, bearer or a key in a header — and then the actions Eva may call.
Custom
Actions on your CRM
Each action defines method, path, body and response mapping, and can read CRM context. Opportunity actions appear as pipeline stage buttons.
Custom
Your catalog by API or file
If your catalog does not live in a connectable store, it is ingested from an endpoint of yours or from a file. API sources sync every 24 hours; file sources refresh on a new upload. If an update fails, Eva keeps serving the last good version.
Custom
The agent's HTTP tools
Beyond the actions your team triggers, the agent can call external endpoints as a tool inside its own reasoning. Only the tools registered and configured for that agent exist.
Eva connects to any system with an API. That is a stronger claim than a wall of logos, and a more demanding one on our side: the integration primitive is generic, built for no single industry and no single customer, which is why the same piece serves a steel distributor and a real-estate brokerage. What you will not find here is an integration count or the logo of a system Eva does not talk to yet. If yours is not on the list above, the right question is not whether it is in the catalog, but whether it has an API and who can give us the documentation. That is what a quote is built on; without it, we promise nothing.
If you are switching
If you are coming from another platform, two answers almost nobody gives: we handle the number's migration inside Meta ourselves, the same way we handle your company's verification. On contacts we would rather understate it — your catalog does come in by file or by API, and a contact is created and updated on its own the moment the person writes — but we publish no contact-list import today, so we are not going to promise you one. Ask your current vendor for the export and we go through it with you during setup.
Put Eva to work.
Tell us what you use today for catalog, payments, scheduling or invoicing and we will say plainly whether it is native, whether it gets built custom, or whether it cannot be done yet.
Message us on WhatsAppUpdated