Send Webhook via JS
Send selected form variables to a webhook URL directly from the browser — no Calcopolis backend hop.
In the builder: select a widget → On Click or On Change → Add action → Send Webhook via JS
Behavior
When the action runs, the embed issues an HTTP request from the visitor's browser to your endpoint.
- Client-side — faster to wire up, but URL and auth are visible in the page.
- Endpoint must be reachable from the browser (CORS if cross-origin).
- Payload is a flat JSON object of selected variables.
- Does not require a Calcopolis webhook integration record.
Setup fields
Connect Send Webhook via JS and configure URL, method, authentication, and payload variables in the action / integration dialog.
| Field | Description |
|---|---|
| Webhook URL | Target endpoint for the POST (or chosen method). |
| Authentication | None, Header Auth, or Basic Auth. |
| Payload | Form variables to send as JSON fields. |
Action name
Internal label in the builder action list. Use distinct names when the same widget runs multiple actions.
FAQ
When is client-side webhook OK?
- Public Zapier / Make / n8n catch hooks
- Internal tools on the same domain
- Non-sensitive data (lead name, score, product choice)
Avoid for passwords, API keys, or PCI-related data.
Why does the browser block the request?
| Symptom | Check |
|---|---|
| CORS error in console | Your server must return Access-Control-Allow-Origin for the embed domain |
| 401 Unauthorized | Header / Basic auth must match what the endpoint expects |
| Network failed | URL typo or endpoint down — test with curl first |
Send Webhook via JS vs Send Webhook?
Prefer Send Webhook (server) when credentials must stay private. Use Send Webhook via JS for quick, low-risk automations.