Connect a CRM or Slack
WCKD Forms does not include a “Connect HubSpot” button inside the dashboard. Instead, your server sends outbound HTTPS webhooks with JSON payloads. A middle tool — Zapier, Make, n8n, or your own endpoint — receives that JSON and talks to HubSpot, Salesforce, Slack, Google Sheets, or any other destination.
The pattern (always the same)
- Middle tool first: create a Catch Hook / Custom webhook / Webhook trigger and copy its
https://URL. - WCKD Forms: paste that URL under Settings → Operations → Outbound webhooks, choose when to send, save.
- Destination: add a HubSpot, Salesforce, or Slack action in the middle tool and map
fields.*from the JSON.
OAuth for HubSpot or Salesforce lives in Zapier/Make/n8n — not in WCKD Forms.
Which webhook event?
| Goal | Dashboard setting |
|---|---|
| Push every new form fill to Slack or a spreadsheet immediately | Check When a submission is received |
| Send to HubSpot/Salesforce only after a human marks the lead Won | Check only Won under When status changes to |
The lead is always saved in your database first. If the webhook or CRM step fails, the row remains in Inbox.
Step-by-step guides by destination
The full payload reference, field mapping examples, and troubleshooting live on one page so they stay in sync with the product UI:
- Webhooks — HubSpot, Salesforce, Slack, Pipedrive, Sheets
- Webhooks — setup checklist
- Webhooks — JSON payload reference
- Inbox — change lead status to trigger
status_changed
WhatsApp and other messaging apps
WCKD Forms webhooks are plain HTTPS POST requests. They do not connect directly to WhatsApp. Route through Make, n8n, or your own service that calls the WhatsApp Business API (or a provider such as Twilio) after receiving the JSON.
Related
- Webhooks — complete reference
- Notifications — staff email (separate from webhooks)
- Troubleshooting — webhook POST never arrives