Send answers to n8n
Start an n8n workflow with every answer a campaign receives, or from a Polzy workflow step — on n8n Cloud or your own server. Connect n8n once, then give each campaign its workflow's URL.
On this page
n8n is a workflow tool you can run in its cloud or on your own server. With n8n connected, every answer a campaign receives starts an n8n workflow of yours, and a Polzy workflow can start one too. At the end of this guide you will have an n8n workflow receiving your answers, and — if you add an API key — a list of your workflows to pick from instead of addresses to paste.
n8n is on Business. Only Admins can connect it and choose where a campaign's answers go.
Before you start
You need:
- A workspace on Business, and the Admin role in it.
- Integrations switched on for the workspace, under Settings → General → What this workspace does.
- An n8n workflow that starts with a Webhook node accepting
POST, published so that its production URL works. - An n8n reachable from the internet over HTTPS. Polzy refuses addresses inside a private network.
- Optionally, an n8n API key, so Polzy can list your workflows by name. n8n does not offer its API during its free trial.
Prepare the workflow in n8n
- In n8n, start the workflow with a Webhook node and set its method to
POST. - Under the node's Respond setting, choose Immediately, so Polzy is answered at once while the rest of the workflow runs. Polzy waits 30 seconds at most.
- Publish the workflow, and copy the node's Production URL — not the test URL, which works only while you are listening in the editor.
n8n describes the node in n8n: Webhook node.
Connect n8n to Polzy
- In the sidebar, under Automate, open Integrations and choose the Available tab.
- Find n8n and choose Connect.
- To pick workflows by name, fill in both n8n Instance URL — the address you open n8n at — and API Key. To paste workflow addresses instead, leave both empty: they go together or not at all.
- Choose Test connection. With both filled in, Polzy answers Connected to n8n; with neither, Connected. Each step names the n8n workflow it starts.
- Choose Connect.
To make an API key, in n8n open Settings → n8n API and choose Create an API key — see n8n: API authentication. The key is stored encrypted.
Give a campaign its workflow
- Open Campaigns, then the campaign, and its Integrations tab.
- Under Add a connection, find n8n and choose Connect. If the button reads Set up, n8n is not connected to the workspace yet.
- Under Workflow URL, paste the production URL of the workflow these answers should start.
- Choose Save changes.
n8n then appears under Connected to this campaign, with its switch, Edit configuration, Disconnect, and how many answers were sent.
What n8n receives
Each answer is one POST with a JSON body:
| Field | What it holds |
|---|---|
event | survey.response for a campaign's answer, workflow.step from a Polzy workflow. |
timestamp | When the request was sent. For an anonymous answer, the day it was given. |
data.survey.id, data.survey.title | The survey's ID and title. |
data.response.id | The answer's ID in Polzy. Empty for an anonymous answer. |
data.response.submittedAt | When the answer was finished. For an anonymous answer, the day alone. |
data.response.answers | One item per question answered, each with questionId, questionText and value. |
data.response.score | The overall score, if it was worked out by the time the request was sent. |
When the connection has an API key and the workflow's URL is on the same host as the n8n Instance URL, the request also carries the key in the X-N8N-API-KEY header. A workflow on any other host is called without it.
An anonymous answer carries what it said, its score and its day, and nothing that could name or time its author. Polzy waits for each answer's safety reading, up to 10 minutes, before it sends it. The privacy floor does not hold single answers back.
Start n8n from a Polzy workflow
- Open Workflows and the workflow, or start a new one.
- Under Connectors in Installed steps, drag Trigger an n8n workflow · n8n onto the canvas.
- Under Workflow URL, pick one of your active workflows that start with a Webhook node — listed when the connection has an API key — or paste its production URL.
- Leave Payload empty to send everything the run knows, or write the JSON you want, with
{{to insert values from the run. - Choose Send a test to send one request filled from a sample response, then look at it in n8n's Executions.
The step leaves n8n's answer as {{connector.statusCode}} and {{connector.response}} — with Respond set to When Last Node Finishes, that is your workflow's result.
No Business plan? A workflow's Outbound webhook step posts to any address, an n8n Webhook node included, without connecting n8n. Workflows are on Team. See Workflows.
Check that it works
On the campaign's Integrations tab, the activity line counts the answers sent and those that failed. n8n's own page in Polzy lists each delivery under Activity, with Worked or Failed and the reason, and n8n's Executions tab shows each run on its side.
Troubleshooting
- The instance URL and the API key go together. Only one of the two is filled in. Fill in both, or empty both.
- n8n refused this API key. The key is wrong, expired or deleted. Make a new one under Settings → n8n API.
- n8n answered, but its public API is switched off. Enable it in n8n's settings. On your own server, the API is turned off — see n8n: Disable the public REST API. Turn it back on, or connect without a key.
- private addresses are not allowed. The address points inside a private network. Polzy can only reach an n8n that is on the internet.
- only https endpoints are allowed. The URL must start with
https://. - Request failed with status code 404 (under Activity). The workflow is not published, or the URL is its test URL. Publish it and use the Production URL.
- The Workflow URL list is missing your workflow. Only active workflows that start with a Webhook node are listed. Publish it, or paste its URL instead.
Answers given before the URL was saved, or while the switch was off, are not sent later. Export them from the survey's Responses instead.
Good to know
- Does a slow workflow fail? A request n8n has not answered within 30 seconds counts as failed and is tried again, up to three times in all. Respond Immediately to avoid it.
- Can n8n check that a call comes from Polzy? The API key travels only to your own instance. To protect a Webhook node on its own, n8n offers header authentication; Polzy's n8n connection sends no other header.
- Can n8n send data back into Polzy? Not through this connection. A Polzy workflow can start from an Incoming webhook — see Webhooks.
Useful links
Related articles
Signed-in members can ask Polzy or message the team from Support. How fast we reply depends on your plan.