Introduction
Webhooks let SmartSurvey notify your systems automatically when something happens, like a response being completed, updated, or disqualified. Instead of polling for changes through the API, SmartSurvey sends an HTTP request to an endpoint you provide whenever the event occurs.
You can use webhooks to:
- Trigger automations in tools like Zapier/Make/n8n
- Sync response activity into CRMs or data warehouses
- Kick off internal workflows (e.g., Slack alerts, case creation, follow-up emails)
Webhook types in SmartSurvey
SmartSurvey supports two webhook types, depending on how broad and how custom you need the integration to be:
Global webhooks (account-level)
Global webhooks are managed at the account level and can apply across your SmartSurvey account. They're ideal when you want a consistent integration pattern across many surveys.
You can configure a global webhook to:
- Target all surveys on the account, or
- Target specific surveys
Global webhooks use the standard SmartSurvey event payload format and are designed for “set-and-forget” integrations.
Global webhooks support batching, so payloads are always delivered as an array. If multiple events occur within a short period (for example, a surge of responses), SmartSurvey may include several events in a single request rather than sending one request per event.
Read more about global webhooks
Survey webhooks (survey-level)
Survey webhooks are created inside a specific survey (Automate → Webhooks). They’re designed for cases where you need more control over the outgoing request per survey.
Survey webhooks support advanced request customisation, including:
- Per-webhook HTTP method (e.g., POST/PUT/PATCH)
- Custom headers
- Custom Content-Type
- Custom body (send exactly what you define)
- Piping in the URL, headers, and custom body (so values can be dynamic per response)
Survey webhooks are ideal when:
- Each survey needs to send to a different system or endpoint
- Your endpoint expects a specific schema or authentication header
- You want to include piped values in routing (e.g., different URLs per collector or survey)
Updated 10 days ago

