Webhooks From Basic
Responses to any address
A webhook sends each completed response as an HTTP request with a JSON body to the address you set: your backend, a CRM or an automation tool. Choose the questions, the method and the headers.
From Basic. The address must be public.
- Your method and headersPOST, PUT, PATCH or GET, with any headers, such as a token.
- Several per surveySend one survey to several systems at once.
- Delivery logsEvery request with the server's answer. Retry one or all failed.
- Incomplete responsesOptionally, every 1, 6, 12 or 24 hours.
Where teams send responses
Anything that accepts an HTTP request.
- Your own backendSave responses next to your users and orders.
- A CRMCreate a lead or update a contact through the CRM's API.
- Automation toolsStart a scenario in a tool that accepts webhooks.
- Scores and promo codesQuiz scores and issued promo codes come with the response.
How to set it up
To try it without a server, use a test endpoint from a service like webhook.site.
- 1
Create a webhook
In the survey, open Integrations, then Webhook, and click Create a Webhook.
- 2
Set the address
Enter the Call Back URL and the method. Most services expect POST.
- 3
Choose the data
Add headers if needed, pick the questions and hidden variables, and give them short names.
- 4
Turn it on
A new webhook is saved switched off. Turn on the switch to start sending.
What the request contains
- AnswersEach selected question with its title, type and answers, keyed by the question ID.
- Hidden variablesIn extra_params, keyed by the variable name.
- Scores and codesMaximum and earned score with a breakdown by question, the promo code and order number.
- RetriesResend failed requests one by one, or up to 1,000 for a period at once.
Agent skills
Do this with your AI assistant
Free agent skills for Claude Code, Codex, Cursor and Gemini CLI that do this job in your SurveyNinja account.
All agent skills- Webhook setup Set up a webhook to send responses to our server Sends survey responses to your own address and checks that the receiver accepted them
- Why responses are not delivered Responses stopped arriving in our Google Sheet. Find out why Finds why responses never reach your Telegram, Google Sheet, Zapier or webhook, and what to do about it
Questions and answers
Which plan includes webhooks?
Basic and every plan above it, and the 14-day trial.
Can I send to a local or internal address?
No. The address must be public. Internal and local addresses are not allowed.
Can a webhook get responses that were not finished?
Yes. Turn on Send incomplete responses and choose an interval: 1, 6, 12 or 24 hours. If the respondent finishes later, the response comes again as completed.
How do I know a request failed?
Open the webhook's Logs: they show the total, failed and queued deliveries, and each request with the server's answer. Retry from there.
Do I need to write code?
Only on the receiving side. In SurveyNinja you paste an address and pick the questions.
More integrations
-
From Basic
Zapier
Each completed response starts a Zap: CRM, email tools, chats, task managers.
Built in -
From Basic
HubSpot
Contacts from quiz and form answers, through Zapier or a webhook.
Through Zapier -
From Basic
Salesforce
Leads and records from survey answers, through Zapier or a webhook.
Through Zapier
Send your responses anywhere
Use it free for the 14-day trial, then keep it on Basic.
Google Forms Limits: Responses, File Uploads, Timers and Logic, With Workarounds