Zapier & Make

Send ResponseDock responses to thousands of other apps with Zapier or Make. Zapier uses the ResponseDock Zapier app, which subscribes to responses through REST hooks. Make uses a plain ResponseDock webhook pointed at a Make custom webhook.

ℹ️

Both need a plan that includes API keys and webhooks. Zapier connects with a workspace secret API key (sk_…) from the API keys page; treat it like a password.

Zapier

⚠️

The ResponseDock Zapier app is private and invite-only for now; it is not listed in the Zapier app directory, so searching for it in Zapier finds nothing until you accept an invite. To get access, request an invite at support@responsedock.com with the email address of your Zapier account. Make needs no invite.

Connect your workspace

Accept the Zapier invite we email you; the ResponseDock app then appears in your Zapier account.
On the API keys page, create a secret key (sk_…).
In Zapier, add the ResponseDock app and paste the secret key when asked to connect an account.
Zapier checks the key and labels the connection with your workspace name.

Triggers and actions

Name	Type	What it does
New Response	Trigger	Fires when a response is completed (`survey.response.completed`), optionally for one survey only. The trigger fetches the full response, including the answers.
Response Started	Trigger	Fires when a respondent starts a survey (`survey.response.started`).
Create Respondent Link	Action	Creates a personal survey link for one of your users, identified by your own user ID (`externalUserId`).

While you set up a trigger, Zapier loads recent real responses as samples, or a static example when the survey has none yet.

What a New Response contains

{
  "id": "resp_aaaa",
  "responseId": "resp_aaaa",
  "surveyId": "survey_yyyy",
  "surveyTitle": "Customer feedback",
  "completedAt": "2026-10-14T10:30:00.000Z",
  "isAnonymous": false,
  "answerCount": 2,
  "answers": [
    { "questionId": "q_1", "question": "How likely are you to recommend us?", "value": 9 },
    { "questionId": "q_2", "question": "What should we improve?", "value": "Faster exports" }
  ],
  "externalUserId": "user_123"
}

Answers to confidential questions are never included. For anonymous surveys the trigger carries only the answer count, never the answers or who responded.

Managing Zaps

Turning a Zap on creates a webhook subscription in your workspace. It is listed on the Webhooks page with a Zapier chip. Turning the Zap off removes the subscription; deleting the subscription on the Webhooks page stops the Zap from receiving responses.

Building your own Zapier integration

The source of the ResponseDock Zapier app lives in integrations/zapier in the repository, with a README on deploying it as a private Zapier integration (useful for self-hosted installations). The endpoints it uses all authenticate with Authorization: Bearer sk_…:

Endpoint	Purpose
`GET /api/v1/zapier/me`	Tests the key; returns `workspaceId`, `workspaceName` and `keyName`.
`GET /api/v1/zapier/surveys`	Surveys for a dropdown: `id`, `title`, `status`.
`POST /api/v1/zapier/hooks`	Subscribes `{ targetUrl, event, surveyId? }`; `event` is `survey.response.completed` or `survey.response.started`. Returns `201 { id }`.
`DELETE /api/v1/zapier/hooks/:id`	Unsubscribes; returns `204`.
`GET /api/v1/zapier/samples/:event?surveyId=`	Sample payloads, each with an `id`.
`GET /api/v1/zapier/responses/:responseId`	One response with its answers, in the shape shown above.
`POST /api/v1/zapier/respondent-links`	Creates a respondent link from `{ surveyId, externalUserId, ttlSeconds? }`; returns `201 { token, surveyUrl }`.

Hooks are delivered with the standard webhook envelope and signature headers described in the Webhooks guide. Webhook payloads carry only the answer count ("answers": { "count": 2 }), so fetch GET /api/v1/zapier/responses/:responseId when you need the answers.

Make

Make receives ResponseDock events through an ordinary webhook:

In your Make scenario, add a Webhooks → Custom webhook module and copy its URL.
In ResponseDock, open Webhooks, add an endpoint with that URL and choose the events, for example survey.response.completed.
Send a test event, or submit a response, so Make can determine the data structure.
Optionally verify the X-ResponseDock-Signature-V2 header with the endpoint's signing secret, as described in Signature Verification.

The payload has the same shape as every ResponseDock webhook: an event name and a data object with workspaceId, surveyId, surveySlug, responseId, completedAt, isAnonymous and the answer count. To get the answers in Make, add an HTTP module that calls GET /api/v1/zapier/responses/{{responseId}} with a secret API key.