Every survey response is a small to-do. Someone has to save it, read it and decide whether it needs a reaction. Done by hand, that works for a few weeks, until the week somebody is on holiday.
This article shows how to hand those jobs to an automation platform, so every new response is taken care of the moment it arrives. You set it up once. After that, it runs on its own.
👋 You don't need to be a developer. The tools in this article are made for people who don't write code: you connect ready-made blocks, a bit like building with LEGO. And if you'd rather have it built for you, click Get expert setup on the Webhooks page of your survey, or write to techsupport@survio.com.
How it works: two pieces that work together
Two things do the work here:
A webhook is Survio's delivery service. The second someone submits your survey, Survio sends the full response to an address you choose. How to add one is explained in Webhooks: send responses to your other tools in real time.
An automation platform decides what happens next. Tools like n8n, Make or Zapier let you build a workflow from blocks: when a response arrives, save it here, check the score, send this person a message. No code needed.
Put the two together, and every response starts a small chain of events that runs without anyone touching it.
💡 One webhook is enough. You don't need a separate webhook for every tool. Send your responses to the automation platform once, and let it pass them on to your spreadsheet, CRM and team chat. That's especially handy on plans with a limited number of webhooks per survey.
Why it's worth it: set it up once, and it runs on autopilot
Most feedback work isn't difficult. It's just repetitive, and repetitive work is the first thing to slip when a team gets busy. Here's the same job, done both ways:
What changes once it's running
Nothing gets forgotten. Every response is handled, including the ones that arrive on a Friday evening.
You react faster. An unhappy customer can hear from you the same day, while there's still time to put things right.
Answers show up where your team already works. In the CRM, the spreadsheet or the team chat, not in one more dashboard someone has to remember to check.
It grows with you. 20 responses a week or 2,000, the workflow does the same job with no extra effort.
Workflow 1: save every response and get a weekly AI report
The simplest workflow, and a great first project. Every response is saved to a Google Sheet as it comes in. Once a week, an AI step reads everything that arrived and emails you a short summary.
How it runs
Save. Each response becomes a new row in a Google Sheet in your Drive: one row per response, with the date, the score and every answer.
Wait for Monday. A second workflow is set to run on a schedule, for example every Monday at 8:00. (Automation platforms can start a workflow on a timer, not only when new data arrives.)
Review. It takes last week's rows and hands them to an AI step, for example ChatGPT, Claude or Gemini, connected with your own account. You decide what it should look for.
Send. The summary is emailed to you and your team.
Here's what such a report can look like:
Brief the AI step the way you'd brief a colleague. The clearer the instruction, the more useful the report. For example:
“Summarise last week's survey responses in five bullet points. List the three most common complaints and how often each came up. Quote every response with a rating of 2 or lower, with the respondent's name.”
Workflow 2: send responses to your CRM and follow up on low scores
Your CRM is the system where you keep your customer data, like HubSpot, Pipedrive or Salesforce. This workflow puts every response on the right customer's record and makes sure no unhappy customer is left waiting.
How it runs
Check. The automation reads the score and the comment.
Save to the CRM. It finds the customer, usually by email address, and adds the score to their record. Everyone who opens that record now sees how the customer feels.
Low score? Create a task. For a score of 0 to 6 (on a 0 to 10 scale), it also creates a task with the comment attached, assigned to the person who looks after that customer.
Reach out. That person calls or emails the customer, ideally within 24 hours.
High scores are simply saved. They're still useful: your sales team sees a happy customer before the next conversation.
For this to work, the response needs to know who the customer is. Ask for an email address in the survey, send the survey through email invitations, or add a customer ID to the survey link (see tip 3 below).
💡 Check before you create a task. If the customer already has an open task or support conversation, add the new score there instead of opening another one. Nobody enjoys being contacted twice about the same problem.
More ideas for what to do with each score are in Put your feedback on autopilot: automation, CRM integration, and alerts.
Workflow 3: feedback after every support call, credited to the right agent
Support teams want to know how each conversation went, and every agent deserves feedback on their own work. The trick that makes it possible: put the agent's name into the survey link.
How it runs
The call ends. Your helpdesk or phone system marks the call or ticket as finished. That starts a workflow in your automation platform.
The survey goes out. The automation emails the customer your short feedback survey. The link carries the agent's name at the end, for example
…?agent=petra. This is called a URL parameter: extra information that travels with the link.The customer answers. Two questions are plenty: “How satisfied are you with the help you got?” and “Is there anything we could have done better?”
The answer comes back. The webhook delivers the response, including
agent=petra.Credited and shared. The automation adds a row to Petra's scorecard and posts the result to your team channel in Slack or Microsoft Teams. Low scores can go straight to the team lead.
After a few weeks, every agent has a fair picture of their work, based on real customer answers rather than the few cases someone happens to remember.
URL parameters are available on PRO Business plans.
How to set it up
Webhooks are a premium feature, available on Mini and higher plans. The number of webhooks per survey depends on your plan.
The steps are almost the same in every automation platform:
Create a workflow and start it with a webhook trigger. In n8n it's the Webhook node, in Make the Custom webhook module, and in Zapier the Catch Hook trigger from Webhooks by Zapier. The trigger gives you a URL. Copy it.
Paste the URL into Survio. Open your survey, go to Get responses → Webhooks, click Add a webhook, paste the URL and save. The full walkthrough with screenshots is in the Webhooks article.
Send a test response. Fill in your own survey once. Your automation platform now sees what a real response looks like, and you can pick the parts you need (score, email, answers) in the next steps.
Add the steps and switch it on. Add the blocks you need (sheet, CRM, Slack…), test the whole workflow, then activate it.
Using n8n? The Webhook node has a Test URL and a Production URL. The test one only works while you're editing. Before you go live, paste the Production URL into Survio and activate the workflow.
Tips and tricks
1. Start with one workflow
Workflow 1 is a good first project: it's hard to break anything, and you get something useful every Monday. Add the next workflow once the first one has run smoothly for a couple of weeks.
2. Always test with your own response first
Submit the survey yourself and check that every step did what you expected before you switch it on. Do it again whenever you change the survey, because a new or renamed question changes what arrives.
3. Put useful details into the survey link
With URL parameters you can add a customer ID, an order number or an agent's name to the link, for example …?customer=4521&agent=petra. They arrive with every response, so your automation knows who answered and what it's about, without asking the respondent.
4. Save a copy of every response first
Make saving to a sheet the first step of your workflow, before anything else happens. If a later step fails, nothing is lost.
Responses that arrive while a webhook is paused or deleted can't be resent. Don't switch a webhook off “just for a moment” while you edit your workflow.
5. Get an alert when something breaks
Automation platforms can tell you when a workflow fails: n8n has an Error Trigger, Make has error handlers, and Zapier emails you about errors. Set this up, so a broken step doesn't go unnoticed for weeks.
6. Keep a person in the loop for sensitive replies
Let the automation save, sort, summarise and alert. Let a person decide how to answer an unhappy customer. An automatic apology rarely lands well.
7. Remember your response quota
Webhook deliveries count against your plan's response quota. If you run out, deliveries pause until your next billing period. Your responses are still saved in Survio either way.
8. Share only what each tool needs
When responses are linked to a person (through an email address or a customer ID), say so in the survey. And send each tool only the answers it really needs.
Where to start
Pick one survey that gets responses regularly.
Choose the workflow that would save your team the most time.
Create the webhook trigger in your automation platform and add the webhook in Survio.
Send a test response and check every step.
Switch it on, and look at the results after one week.
🙌 Prefer not to build it yourself? Click Get expert setup on the Webhooks page, tell us what you'd like to happen, and our team will build and test it with you. Or write to techsupport@survio.com.