Platform · Connectors and integrations

Connect your store and the messages handle themselves.

Native connectors for VTEX and Opencart, a generic webhook for any other system and an open API when you want full control. The events in your operation become automation triggers without anyone writing an integration.

Available today
VTVTEXNative connectoravailable

Order created, paid, shipped and abandoned cart, authenticated with App Key and App Token.

order.paidcart.abandonedorder.shipped
OCOpencartOfficial extensionavailable

Order created, paid, status changed and new customer, through an extension installed in the store.

order.createdorder.status_changed
{}Your own webhookAny systemalways

ERP, CRM or legacy system: one signed POST to our URL and the event becomes a trigger.

custom.eventX-CCX-Signature
2
native connectors in production today
1 POST
is all the generic webhook requires
HMAC
signature checked on every event
retries with an increasing wait
Connector activation

Credential, events, variables. Published.

Each connector asks for the minimum it needs to work and validates the credential on the spot. After that it is picking which events become triggers — the variables already arrive ready for the template.

See automations

Native connector using VTEX's own App Key and App Token. It subscribes to the order and cart hooks on the given account, with no app installed in the store.

1App Key and App TokenGenerated in the VTEX admin under Account settings › Application keys, with read permission for orders.
2Account and environmentGive us the account name and the environment; we validate the credential on the spot with a test call.
3Pick the eventsCheck which events become triggers. Each one shows the estimated frequency for your store.
4Wire it to the automationsThe event shows up as a trigger when you create an automation, with the variables already available.
VTVTEX · acme-store.myvtex.comconnected
Events we listen to
Payload received
{
  "event": "order.created",
  "orderId": "1493827acme-01",
  "value": 28490,
  "items": 3
}
Variables for order.created5 variables
{{pedido.id}}{{pedido.valor}}{{cliente.nome}}{{cliente.telefone}}{{itens.quantidade}}
No ready-made connector

Any system comes in through a webhook.

We impose no format: you send the JSON your system already produces and the platform maps the keys. Signature checked, idempotency per event and a test button before it counts for real.

01No format imposedWe bend the mapping to your JSON, not the other way around: the keys you already use become variables.
02Signature and idempotencyHMAC-SHA256 in the header and an idempotency key per event — resending to be safe does not duplicate a message.
03Test before it countsOne button fires a sample event and shows what the platform understood from your payload.
See the webhook documentation
curl -X POST \
https://api.ccxmessages.com/v1/hooks/inbound/erp-interno \
-H "X-CCX-Signature: sha256=9f21ac…" \
-H "X-CCX-Idempotency-Key: fat-8842-3" \
-H "Content-Type: application/json" \
-d '{
"event": "fatura.vencida",
"contact": { "phone": "+5541998124410" },
"data": {
"valor": 284.90,
"dias_atraso": 3
}
}'
Roadmap

What comes next.

The connector queue is ordered by customer demand. While yours has not arrived, the generic webhook already solves it — and moving to the native connector does not require redoing the automation.

VTVTEX
Orders, abandoned cart and delivery status.
Available
OCOpencart
Orders, status and new customer through the official extension.
Available
{}Generic webhook
Any system with one signed POST.
Available
SHShopify
Orders, cart and fulfillment.
In development
NSNuvemshop
Paid orders and shipping updates.
In development
BLBling
ERP: orders, invoices and stock.
Planned
TYTiny
ERP: orders and dispatch.
Planned
RDRD Station
Qualified lead and stage change.
Planned
ZPZapier
Bridge to hundreds of apps, with no code.
Planned
Reliability

Integration that does not lose an event.

Signature checked on the way in, idempotency per event, retry with an increasing wait on the way back and a record of everything that went through. Resending to be safe never turns into a duplicate message.

Signature checked

Every event is validated with HMAC-SHA256 before it enters the queue. A payload without a valid signature is refused.

Idempotency per event

A unique key per event: the same trigger sent again is recorded and discarded, with no duplicate message.

Retry with a wait

A failed call back to your system is retried five times, with an increasing interval.

Log of everything that came in

Payload received, processing result and which automation fired — searchable by period.

Frequently asked questions

What people ask before connecting.

Your platform is not on the list? Ask for priority .

For VTEX, no: generate an App Key and an App Token in the store admin and paste them into the dashboard. For Opencart you have to install the extension, which whoever looks after the store normally handles. Only your own webhook requires someone who knows where to configure the dispatch in your system.

Start today with R$ 50 in test credit.

Sandbox wallet released when you create the account, a WhatsApp test number and guided onboarding. No card, no contract.

Book a demoCreate free accountSales reply within 2 business hours
CCX
Brazilian CPaaS platform. WhatsApp, email, SMS, RCS, push and Instagram in a single integration.
All systems operational
© 2026 CCX Digital Solutions LTDA · CNPJ 24.329.191/0001-06 · BrazilTerms of usePrivacySecurityChangelog