Integrations
Connected to the systems that already hold your customers
The official WhatsApp Cloud API for messages, connectors for the stores and CRMs teams actually run, signed webhooks you can debug yourself, and a versioned REST API for everything else.
Channel
WhatsApp Cloud API
The official Meta Cloud API, connected through Meta’s own embedded signup. Not a shared number, not an unofficial bridge, and not something that stops working when Meta tightens a rule.
Connector
Shopify
Catalogue and orders, so a conversation about an order knows what the order is and what state it is in.
Connector
WooCommerce
The same catalogue and order sync for a WordPress store.
Connector
Zoho CRM
Contacts and conversation activity, so the CRM stops keeping a separate and worse account of the same customer.
Connector
Any REST service
A generic connector for a service with a REST API: map its fields to ours once and it behaves like a first-party integration, including the retry and the delivery log.
Connector
Outbound webhooks
Signed, retried, and inspectable: a delivery log with the response your endpoint actually gave. Debugging a webhook should not need our support team.
Build your own
Public REST API and SDKs
Contacts, conversations, messages, templates and campaigns over a versioned REST API with API keys, request IDs and idempotency. The SDKs are generated from the same OpenAPI document the product is built against, so they cannot describe an endpoint that does not exist.
Need something that is not here? The generic REST connector covers most services without a release from us, and an outbound webhook covers the rest. Tell us what you need.
What an integration includes, whichever one it is
The unglamorous half, which is the half that decides whether an integration is trustworthy.
A delivery log you can read
Every call out and every call in, with the status, the response and the retry attempts. When a sync is wrong you look, rather than open a ticket.
Retries with a circuit breaker
A failing endpoint is retried with backoff and then stopped, so one broken integration cannot take the rest of your automation down with it.
Signed payloads, both ways
We sign what we send and verify what we receive, and the signing secret is never shown again after you create it.
Credentials that are not in a log
Integration credentials are encrypted with a key version recorded beside them, and never written to a log line or an error message.
Connect it during the trial
Integrations, webhooks and API keys are all available while you are evaluating, so you can find out whether it works before you pay for it.