Automate surveys and forms with n8n: here's how

Third time today you have checked whether anyone new has filled in your survey? A request lands in your form, you copy the address into your mail client and type a reply? Both of those are handwork, and tools like n8n can take them off your plate.

n8n is a tool for automation: you put together a sequence of steps and it then runs on its own. empirio.ai has its own node at n8n. To automate surveys with n8n, you install the empirio.ai node, connect your empirio.ai account and pick a trigger: either every new response, which starts a workflow straight away, or a schedule that pulls your results together at regular intervals. We will walk you through it, and we have created ready-made templates you can simply import.

📌 Key takeaways

• n8n connects empirio.ai with 1,000+ tools such as Gmail, HubSpot or Slack.
• Every empirio.ai integration is free on every plan.
• Ready-made n8n templates from empirio.ai save you the setup.
• The empirio.ai Trigger starts a workflow on every single response.
• Almost every step can be automated, from creating a survey to analysing it.

What n8n is and why it suits surveys

n8n is a platform for workflow automation. On a canvas you line up individual steps and join them with lines. In n8n those steps are called nodes. The first one sets the workflow off, the rest do something with it: send a message, write a row into a spreadsheet, create a contact in your CRM. No coding needed.

The advantage lies in the sheer number of connections. For the empirio.ai integration, n8n lists over 1,000 apps and services, from Gmail through HubSpot to Slack. For the handful of services that are missing, there is a generic HTTP node. On top of that, n8n bills by workflow execution rather than by individual step (as of September 2026, n8n pricing page). A workflow with twenty steps therefore costs the same as one with three. That suits surveys nicely, because a sensible workflow usually handles several things at once: notify, store, report.

What you can automate around surveys and forms

Every survey goes through the same five phases. Each one holds handwork that a workflow can take over. Once you pull the phases apart, you can see straight away where your own project could run by itself.

• Creating: surveys appear automatically, with nobody setting them up by hand. Your own system can pass information along so the questions fit the occasion exactly.
• Sending: the link to the survey goes out to the right people on its own, through whichever channel you choose.
• Notifying: the moment someone answers, the workflow drops a message wherever you happen to be working.
• Processing: responses travel on into your other systems automatically, so nobody has to retype them.
• Analysing: figures, exports and charts appear on a schedule instead of someone pulling them together every week.

empirio.ai brings two nodes along for this. The Trigger starts a workflow the instant somebody submits the survey, and the action node handles everything else. Spread across the five phases it looks like this:

One caveat: the empirio.ai node does not send invitations and reminders itself. Your email service node does the sending, and empirio.ai supplies the link to the survey.

When automation pays off and when it does not

Automation costs you setup time once and a little maintenance afterwards. Neither pays off unless the task keeps coming back. A one-off survey with thirty responses will be analysed by hand long before your first workflow is even standing.

Three signs point towards an n8n workflow:

1. The survey runs permanently, say as a feedback form on your website or as a recurring satisfaction check.
2. Somebody has to react to a response quickly, because otherwise a complaint or an enquiry sits there untouched.
3. The results belong in another system anyway, because that is where the actual work happens.

What speaks against it is a workflow nobody looks after. One that quietly writes into the void because a question has changed does more damage than none at all.

Automate the task you are doing for the third time. Before that, the effort is not worth it.

empirio.ai in the n8n workflow: the node for surveys and forms

empirio.ai, an online survey tool from Germany, is the point in an n8n workflow where people type something in. n8n connects your systems to one another, and empirio.ai takes care of the part real people actually see: the form, the survey, the feedback question.

That input part is trickier than it looks. A workflow can run perfectly cleanly and still bring in nothing if the form puts people off at the end. Three things decide it:

• How it looks. Every empirio.ai template is free and designed to current standards. On a phone the survey looks just as good as on a desktop, without you adjusting a thing.
• What you can ask. empirio.ai comes with 35+ question types, from single choice through matrix and ranking to the Net Promoter Score, all of them on the free plan.
• Where the data sits. Responses are stored in the EU, and the data processing agreement belongs to the free plan as well. Under Article 28 UK GDPR, that contract is what puts the relationship between controller and processor on a legal footing (ICO guidance on contracts and liabilities). As soon as a company, a charity or a university stands behind the survey, this is the point where the decision gets made.

Whenever your workflow needs data from people, feedback after a purchase, a sign-up, a satisfaction question or a contact form, empirio.ai is the node for it. Everything before and everything after is the job of n8n.

Setting up empirio.ai in n8n: step by step

empirio.ai is listed in n8n as a verified integration and turns up there as two entries. The empirio.ai node is the action node: you tell it what to do and it does it at the point in the workflow where it sits. The package is called @empirio-ai/n8n-nodes-empirio-ai.

The empirio.ai Trigger is the second entry. It always sits right at the start and waits for a response to come in. The action node asks for something, the trigger gets called.

Step 1: install the node in n8n

The empirio.ai node is a community node verified by n8n. It is not part of the standard set, so it gets enabled for your instance once and is available to everyone from then on. You can see what is inside before you install it: one trigger and 16 actions.

1. In n8n Cloud, open the node panel, search for empirio.ai and pick the entry under “More from the community”. “Install” enables it for the whole instance, and only an owner or an admin may do that.
2. On a self-hosted instance, open Settings, then Community nodes, then “Install a community node”, and enter the package name.

Step 2: connect your empirio.ai account

The node offers two routes and both end up in the same place: either you store a key, or you approve the connection once in a window from empirio.ai. The API key takes a minute: sign in to empirio.ai, open the integrations and create a key under “REST API”. The key is shown only once, so copy it straight away and paste it into a new credentials card in n8n.

The second route is OAuth and spares you a permanently stored key. You create the OAuth credentials in n8n, copy the redirect URL it shows you and enter it at empirio.ai in a new OAuth client. Client ID and secret go back into n8n. Finally you click “Connect my account” in n8n, a window from empirio.ai opens, and you approve the connection there.

⚠️ Heads-up

On a self-hosted instance the trigger needs a publicly reachable HTTPS address. empirio.ai does not deliver to localhost and not to private network addresses. The way round it is a public hostname with TLS, and for a test a tunnel is enough. The action node is not affected.

One cost disappears here: the empirio.ai integrations belong to every plan, the free one included. You need no upgrade and no credit card, just an account.

Your first workflow in the n8n editor: two nodes are enough

In the n8n editor you drag the nodes onto an empty canvas and join them with a line. The workflow runs from left to right: whatever sits on the left sets things off, whatever sits on the right gets carried out.

The workflow in the picture is made of two nodes. On the left sits the empirio.ai Trigger with the event “Survey response submitted”. On the right hangs Microsoft Teams with the “Create message” action. The moment somebody submits the survey, the response turns up as a message in the Teams channel, with nobody having to go and look.

“Execute workflow” lets you try the whole thing out once and see immediately whether the message arrives. Only then do you switch it live so that it keeps running.

Three templates that cover nearly every case

Almost everything people create with surveys and n8n falls into one of three groups: notify, store, report. The first two hang off the trigger and run on every response, the third hangs off a schedule and runs by the clock.

empirio.ai provides ready-made templates for all three groups. You import one of them into n8n, enter your credentials and pick your survey. After that the workflow just runs.

Template 1: a notification as soon as somebody has answered

The trigger fires, a message node sends. The shortest workflow worth having needs nothing more. No more checking the dashboard. It pays off most with surveys that run for weeks and only produce the odd response. Three variants are common:

• Every response into a team channel, via Slack, Microsoft Teams or WhatsApp. Sensible when the responses are few but important.
• Only the critical responses by email. An If node sits between trigger and message: anyone giving a 0 to 6 on the Net Promoter Score sets off an email, everyone else passes through quietly.
• Send the open-text answer along with it. The free text sits in plain sight in the message, so nobody has to log in for it.

Template 2: store responses in other systems automatically

The same trigger, a different second node. Instead of a message, the workflow writes the response wherever it gets used next. This pays off the moment somebody would otherwise be retyping the data.

• One row per response in Google Sheets or Excel. Switch the unanswered questions on as well, otherwise your columns shift.
• Create or update a contact in HubSpot as soon as the survey asks for an email address, in a customer survey for instance.
• Sort the free text before you store it. An AI node in between assigns the response to a category.

Template 3: regular reporting on activity

Reports do not need a trigger, they need a schedule. The workflow runs at the time you set, fetches the results and sends them out. If you are pulling the figures together every week anyway, this is where you save the most time.

• The weekly email with the raw data. Schedule, export as CSV or Excel, then send.
• Charts instead of tables. The chart export delivers PowerPoint, PDF or Word, rendered and ready.
• The short set of figures with no attachment: views, started and completed responses, completion rate.

💡 Tip

Let the finished workflow write into an unimportant channel first and push three test responses through the survey yourself. Only when every field arrives correctly do you hang the CRM or the mailing list on the end.

Alternatives to n8n

n8n is one route of several for automating surveys and forms, and depending on your project a different one may suit you better. If your team already uses another automation service, you are best off staying there. If you would rather not create a workflow at all and prefer working in a chat, there is a quicker way to the same place. And if you want to connect a system of your own, go straight to the API.

empirio.ai covers all of these routes, and all of them belong to every plan:

• Other automation services: Zapier and Make work on the same principle as n8n. If you already maintain workflows there, that is the shorter route.
• Connecting AI assistants: the MCP server lets you connect the AI agent of your choice, Claude or ChatGPT for example. The survey is then created in the chat and analysed there too, with no workflow at all.
• Connecting your own IT systems: webhooks and the REST API will connect just about any system, including one you have developed yourself. The empirio.ai developer documentation describes how it is done.

What the route through an AI assistant looks like in practice is set out in the guide to a survey with Claude and in the article on the empirio.ai MCP server. What a chat cannot replace, though, is a workflow that runs without you: a chat waits for your input, a workflow waits for nothing.

Common mistakes when automating

Most workflows do not fail while you are creating them. They fail weeks later, quietly doing the wrong thing. Four trip hazards come up again and again.

• Renamed question, empty field. In the flat output format the question title is the field name. Reword the question and n8n gets nothing back for the old name, with no error message at all. Switch to the complete delivery format, or put an If node in front that checks the field.
• A trigger with no public address. A self-hosted instance that cannot be reached from outside over HTTPS gets no deliveries. Enter the public address in n8n, otherwise n8n registers the wrong one with empirio.ai.
• Too many requests at once. empirio.ai allows 60 read requests and 20 write requests per minute per account (as of September 2026). Go over that and you get turned away. An automatic retry does not help, because it asks again too soon, but a Wait node does.
• Export without the second step. The export returns a signed download address and not a file. Without a node that fetches it, you end up sending a link instead of an attachment.

Conclusion

For surveys that keep coming back, n8n is the most direct route: set it up once and notifying, storing and reporting carry on without you. For a one-off study the effort does not pay. If you only want to work in a chat, the MCP server gets you there faster. Start with the shortest workflow you can think of and only extend it once it has run quietly for a fortnight.

Where to go next

• Want to know which other survey tools are worth a look? Survey tools compared
• Want to make the survey cleverer before you send it out? Logic and branching in surveys
• Are you asking for personal data? Data protection in surveys
• Want to show the survey on your own site? Embedding a survey in a website

Want to set your survey up now so that it can be automated later on?

With empirio.ai you create it for free, send out the link and hang n8n on the end as soon as you need it.

Create your free survey now