Webhooks and API

Webhooks are the primary way to connect Wexio to any other system - payment providers, e-commerce platforms, CRMs, no-code tools, and your own backend. Wexio speaks both directions:

• Inbound - external systems POST JSON to a Wexio URL and your flows run in response.
• Outbound - Wexio POSTs JSON to your URL whenever something happens (contact created, message sent, flow reached a custom event).

Access the Webhooks Page

Open Settings, then Webhooks and API, then Webhooks. The same group holds API keys and MCP, each on its own page.

The list shows every inbound and outbound connection with its direction, status, schema version, how many flows use it and when it changed. Use All, Inbound and Outbound to filter, or search by name or endpoint. Click New connection to create one, Open to go to its page, or the row menu for Edit details and Copy (the endpoint URL of an inbound connection).

Owners and Admins can create and change connections. Other roles can view them. On a plan below Pro the page shows a blurred demo with an upgrade prompt.

Connection Limit

Your plan caps how many connections you can have. Inbound and outbound connections count together, and so do paused ones.

On a plan with a limit, the header of the page shows how many you use, for example 7 of 10 connections.

At the limit, Create connection fails and a message appears as a toast: Your plan allows up to 10 webhook connections. Delete one or upgrade to add more. Delete a connection you no longer need, or move to Enterprise.

Inbound vs Outbound

Combine directions freely, and wire the same inbound connection into multiple flows.

The Two Setup Paths

Inbound Path

1. Create an inbound connection - Wexio generates a unique URL and a signing secret.
2. Configure authentication - pick Shared secret (default), or a provider-specific mode (Stripe, Slack, Svix, Paddle, Revolut, HubSpot, Mailgun, Zendesk, Paystack, Vercel, GitLab, Generic HMAC).
3. Configure contact resolution - how to map the incoming payload to a Wexio contact (Chat ID, Phone, Channel User ID, or Email).
4. Capture a sample payload - click Capture schema and send one test request; Wexio learns the field shape and populates the variable picker.
5. Bind a flow trigger - add a Webhook Received trigger on any flow and pick the connection.

See Inbound Webhooks for the full walkthrough.

Outbound Path

1. Create an outbound connection - paste the URL you want Wexio to POST to.
2. Configure authentication - none, Bearer token, Basic auth, or HMAC signing.
3. Subscribe to events - pick which domain events (contact.created, message.outbound.created, flow.*) you want delivered.
4. Optional - emit custom events from flows - drop an Outbound Webhook Event card into any flow to emit flow.<your-name> events mid-flow.

See Outbound Webhooks for the full walkthrough.

Platform Integrations

Many providers connect directly: a chip under Provider presets prefills the auth fields so you paste your signing secret and go. The few providers Wexio cannot verify yet go through an n8n or Zapier proxy.

Observability

Every inbound request and every outbound delivery attempt is logged for 7 days. See Webhook History - open it with Logs on the connection page.

Limits & Defaults

Was this page helpful?

😞😕😐🙂🤩

Related

• Inbound webhooks - connect a provider and bind it to a flow.
• Outbound webhooks - send Wexio events to your endpoint.
• Platform integrations - step-by-step guides per provider.
• Delivery history - inspect inbound requests and delivery attempts (view-only).