Integrations & inbound sources

The CDP is only as good as what flows into it. The integrations module manages the pipes.

Creating an integration

Settings → Integrations → New, or:

curl -X POST https://api.wezend.com/v1/integrations \
  -H "X-API-Key: $WEZEND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "type": "shopify", "name": "Main store", "config": { "shop_domain": "acme.myshopify.com", "access_token": "shpat_…" } }'

An integration defines what connects (CRM, shop, custom system), which events flow, and how contacts map to profiles. Credentials are encrypted at rest.

Importing an existing audience

POST /v1/integrations/:id/import-audience starts a background job that pulls the connected system's contacts (with consent state where the source provides it), deduplicates against existing profiles and reports progress — poll GET /v1/integrations/import-jobs/:jobId or watch the progress bar in the dashboard. Big audiences import without blocking anything else.

Testing the wiring

Before trusting an integration, click Send test event (POST /v1/integrations/:id/test). A synthetic event runs the full pipeline and shows you exactly what arrived and how it mapped — debugging with a flashlight instead of guessing in the dark.

Custom systems: the events firehose

Anything that can send an HTTP request is an integration. Stream behavioural events from your backend or site to POST /v1/events (see Tracking events), and expose the inbound webhook to receive replies in your own tools. Between those two and the reverse-ETL activation out to ad platforms, WeZend sits in the middle of the stack rather than at the end of it.