Webhooks
In funnel settings (Advanced), you can set a Webhook URL. When something happens on your published funnel, web2app sends a POST request to that address with a JSON body.
Use this to plug into Zapier, Make, n8n, or your own server — web2app calls you; you don’t need a custom backend just to receive events.
HTTPS
Use an https:// URL. There is no custom signature header today; protect your endpoint (secret path, IP allowlist, or verification inside your automation tool).
Delivery
- Method:
POST - Header:
Content-Type: application/json - Timeout: about 5 seconds on our side — respond quickly with
2xx. - Retries: delivery is best-effort; transient failures may not be retried. Design your workflow to tolerate occasional misses or pair with periodic exports from Leads / Analytics.
Event: analytics / funnel activity
When visitors move through a published funnel, the product records activity. If a webhook URL is set, we may forward payloads in this shape:
{
"funnelId": "uuid",
"stepId": "uuid or null",
"sessionId": "string",
"eventType": "funnel_view | step_view",
"properties": {},
"timestamp": "2025-01-01T12:00:00.000Z"
}
eventType— todayfunnel_viewon the first step andstep_viewwhen each step is shown; more granular events may be added later.properties— optional extra fields (object), when present.sessionId— stable for one browser session so you can group events.
Event: lead captured
When someone submits an email capture step, we send a dedicated payload:
{
"event": "lead_captured",
"funnelId": "uuid",
"stepId": "uuid or null",
"email": "[email protected]",
"name": "string or null",
"properties": {},
"timestamp": "2025-01-01T12:00:00.000Z"
}
properties contains any extra string fields you configured on that step, when present.
Stripe and payments
Payment events from Stripe are handled on the platform side (your administrator’s Stripe webhook). You do not configure Stripe webhook URLs inside the funnel editor for core billing — use Subscribers in the dashboard and your finance process for purchase data.