n8n

n8n's HTTP Request node can POST to a Wexio inbound URL at the end of any workflow. n8n is especially useful as a proxy for providers Wexio doesn't support natively yet (PayPal v2, Discord, SendGrid signed events, etc.) — n8n verifies the provider's signature, reshapes the payload, then forwards to Wexio.

Provider docs: Setting up webhooks in n8n

Setup (Direct)

1. Create an inbound Wexio connection

Settings → Webhooks & API → New connection → Inbound. Auth mode: Shared Secret. Copy the endpoint URL and the signing secret.

2. Add an HTTP Request node in n8n

At the end of the n8n workflow, add HTTP Request.

3. Contact resolution, schema, flow

As with any inbound connection:

1. Configure identifier + path on the Wexio connection.
2. Tap Capture schema, run the n8n workflow once, let Wexio learn the fields.
3. Add a Webhook Received trigger on a flow and pick this connection.

Setup (Proxy for unsupported providers)

Use n8n to accept the partner's webhook, verify their signature locally (n8n has built-in crypto nodes), reshape the payload into a shape Wexio understands, then forward.

Example for PayPal v2:

1. Trigger: n8n Webhook node, listening on a public URL.
2. Verify: a Function node that fetches PayPal's cert from cert_url in the event, verifies the signature, throws on mismatch.
3. Reshape: a Set node that flattens PayPal's nested resource into a Wexio-friendly shape.
4. Forward: HTTP Request node → Wexio inbound URL, with x-webhook-secret header.

Wexio sees a clean authenticated POST with the shape its schema captured; the partner-specific complexity lives in n8n.

Example — Airtable row → Telegram

• n8n trigger: Airtable — on new row
• n8n HTTP Request: POST { "customer": { "email": "{{ $json.email }}", "name": "{{ $json.name }}" }, "record_id": "{{ $json.id }}" } to Wexio
• Wexio connection: Email + $.customer.email
• Wexio flow: Webhook Received → Text "Hi {{webhook.customer.name}}, your Airtable record {{webhook.record_id}} is ready."

Troubleshooting