Skip to content
polzyHelpGo to Polzy

Send answers to Zapier

Start a Zap with every answer a campaign receives, or from a workflow step, and pass it on to thousands of other apps. Connect Zapier once, then give each campaign its Zap's catch hook.

Polzy team6 min readUpdated 31 Oct 2026Business and up
On this page
  1. 1Before you start
  2. 2How it works
  3. 3Connect Zapier to Polzy
  4. 4Create the Zap
  5. 5Give a campaign its Zap
  6. 6What Zapier receives
  7. 7Start a Zap from a workflow
  8. 8Check that it works
  9. 9Troubleshooting
  10. 10Good to know
  11. 11Useful links

Zapier passes what happens in one app on to thousands of others. With Zapier connected, every answer a campaign receives starts a Zap of yours — to add a CRM note, post a message or open a ticket — and a workflow can start one too. At the end of this guide you will have a Zap that receives your answers, and know exactly what each one contains.

Zapier 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.
  • A Zapier account on a plan that includes Webhooks by Zapier. Zapier lists the plans in Zapier: Trigger Zaps from webhooks.

How it works

  • Connected once. Connecting Zapier in Polzy holds an optional secret that signs each request. There is no Zapier sign-in.
  • One Zap per campaign. Each campaign names the catch hook of the Zap its answers start, so two campaigns can start two different Zaps.
  • From a workflow. The Send to Zapier step starts a Zap with whatever the run knows.

Connect Zapier to Polzy

  1. In the sidebar, under Automate, open Integrations and choose the Available tab.
  2. Find Zapier and choose Connect.
  3. If you want to be able to check that requests come from Polzy, enter a long random value in Secret Key (Optional). Otherwise leave it empty.
  4. Choose Connect. The test answers Connected. Each survey and step names the Zap it starts.
Connecting Zapier: only an optional secret, used to sign each request.

Create the Zap

  1. In Zapier, create a Zap and choose its trigger: the app Webhooks by Zapier, with the event Catch Hook.
  2. Continue to the trigger's Test tab and copy the webhook URL. It starts with https://hooks.zapier.com/hooks/catch/.

Keep the Zap open: it learns the fields of an answer from the first request it receives.

Give a campaign its Zap

  1. In Polzy, open Campaigns, then the campaign, and its Integrations tab.
  2. Under Add a connection, find Zapier and choose Connect. If the button reads Set up, Zapier is not connected to the workspace yet.
  3. Paste the webhook URL into Zap catch hook.
  4. Choose Save changes.
  5. Answer the campaign's survey once, or wait for its first answer.
  6. Back in Zapier, choose Test trigger and pick the request that arrived. Then add your Zap's actions, map the fields, and publish it.
A campaign's destination: the catch hook of the Zap its answers start.

The campaign's Integrations tab then lists Zapier under Connected to this campaign, with its switch, Edit configuration, Disconnect, and how many answers were sent.

A campaign's Integrations tab: what each answer is sent to, and what could be added.

What Zapier receives

Each answer arrives as one request with a JSON body:

FieldWhat it holds
eventAlways survey_response.
timestampWhen the request was sent. For an anonymous answer, the day it was given.
survey.id, survey.title, survey.uniqueIdThe survey's ID, its title and its short code.
response.idThe answer's ID in Polzy. Empty for an anonymous answer.
response.submittedAtWhen the answer was finished. For an anonymous answer, the day alone.
response.answersOne item per question answered, each with questionId, questionText and value.
response.scoreThe overall score, if it was worked out by the time the request was sent.
response.respondentThe respondent's ID in Polzy. Absent for an anonymous answer.

With a Secret Key (Optional), each request also carries the header X-Zapier-Signature: the HMAC-SHA256 of the request body, made with your secret, written in hexadecimal. Catch Hook does not check it itself; Zapier's Catch Raw Hook passes headers on, for a step of yours that can.

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, so every answer reaches the Zap however few there are.

Start a Zap from a workflow

  1. Open Workflows and the workflow, or start a new one.
  2. Under Connectors in Installed steps, drag Send to Zapier · Zapier onto the canvas.
  3. Paste the Zap's URL into Zap catch hook. Each Zap has its own.
  4. Leave Payload empty to send everything the run knows, or write the JSON you want, with {{ to insert values from the run.
  5. Choose Send a test. Polzy sends one request filled from a sample response, so the Zap can learn its fields before the workflow has ever run.
The Send to Zapier step, with Send a test for the Zap to learn its fields.

The step leaves Zapier's answer as {{connector.statusCode}} and {{connector.response}}.

No Business plan? A workflow's Outbound webhook step posts to any address, a Zap's catch hook included, without connecting Zapier. 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. Zapier's own page in Polzy lists each delivery under Activity, with Worked or Failed and the reason. In Zapier, the Zap's history shows each run.

The connector's page: its status, the last seven days, and every delivery.

Troubleshooting

  • Zapier receives nothing. Check the campaign's switch, and that the answer was given through the campaign: answers to the survey outside it do not use the campaign's destinations.
  • only https endpoints are allowed. The catch hook must start with https://. Copy it again from Zapier.
  • Request failed with status code and a number (under Activity). Zapier refused the request — usually because the Zap was deleted or its hook changed. Copy the current URL into Edit configuration.
  • Fields are missing in Zapier. The Zap learned from a request with fewer answers. Send another test and choose Test trigger again.
  • The same answer arrived twice. A request that takes Zapier longer than 10 seconds to accept counts as failed and is tried again, up to three times in all.

Answers given before the Zap's hook was saved, or while the switch was off, are not sent later. Export them from the survey's Responses instead.

Good to know

  • Does Polzy need my Zapier password? No. A catch hook is all it needs. Treat it like a password: anyone who has it can start your Zap.
  • Can one answer start several Zaps? One per campaign through its Integrations tab. A workflow can start as many as it has steps.
  • Can Zapier send data back into Polzy? Not through this connection. To send people or events in, see Webhooks and the API keys.

Useful links

Was this helpful?

Related articles

Still stuck?

Signed-in members can ask Polzy or message the team from Support. How fast we reply depends on your plan.

Ask PolzyContact support