Automate with Zapier¶
The withfeedback Zapier app lets you react to feedback as it arrives, push submissions in, and look things up — with no code. Typical Zaps: post approved testimonials to Slack, open a ticket on a detractor, add a survey respondent to a Google Sheet, send a thank-you from Gmail.
Zapier uses the API, so it needs a plan that includes API access — Pro and above.
Connect your account¶
When you add a withfeedback step, Zapier sends you to a consent screen. It lists exactly what the connection may do:
- read your profile, teams, feedback and surveys;
- create feedback;
- moderate submissions (this is what lets the Approve and Reject actions work — e.g. "approve from a Slack reaction");
- read and manage webhook endpoints (how instant triggers subscribe).
Approve it and you are connected. The connection is tied to your account; pick the team and project in each Zap step.
If a Zap says to reconnect
Two things cause it: the connection sat idle for more than 90 days, or a security event revoked it (for example, a refresh token was replayed). Reconnect the account in Zapier and the Zap resumes.
Triggers (instant)¶
Every trigger asks for a Team and a Project first.
| Trigger | Fires when | Extra filter |
|---|---|---|
| New Submission | Any submission arrives (still pending) | Kind |
| New Testimonial | A testimonial is created | — |
| Submission Approved | A submission is approved | Kind |
| Submission Rejected | A submission is rejected | Kind |
| New Survey Response | A survey/NPS response is recorded | Survey |
| Low NPS Score | An NPS answer is a detractor | Survey |
| Follow-Up Answered | A respondent answers the AI follow-up on a low score | Survey |
New Submission also fires for survey responses
A survey response is a submission, so it triggers New Submission too. Use New Survey Response when you want the survey-specific fields.
Each event's output is one flat object — the submission's text, rating, score,
tags, contact fields, dashboard_url, and more — plus event_id. Follow-Up
Answered also carries the question and answer.
Actions¶
- Create Submission — create a testimonial or feedback from any other app. It enters the review queue like any other submission.
- Approve Submission / Reject Submission — moderate from a workflow. Map the Submission ID from a trigger.
Searches¶
- Find Submission — the newest submission matching a text search.
- Find Project — a project by its exact name.
Find Submission also offers find or create: look up a submission by text and create one if none matches.
Delivery is at-least-once¶
Instant triggers are delivered at least once — occasionally a Zap runs twice
for the same event. Every trigger output carries event_id; if a downstream
step must run exactly once, dedupe on it (a Filter or the built-in Digest step),
or make the downstream action idempotent.
For Create Submission, map a stable id from your trigger into the optional Idempotency key field (for example, the form response id). Then a retried Zap will not create a duplicate; reusing a key with a different body is rejected.
What data leaves your account¶
An instant trigger sends us the event, then reads back the submission's fields to
build the Zap's output — text, rating, score, tags, the contact's name/email/
title/company, consent state, dashboard_url, and (for video) the transcript.
Metadata is not exported. Follow-Up Answered additionally includes the
respondent's question and answer, which travel in the event itself.
Delivery logs on our side are redacted after 30 days and deleted after 90.
Turning a Zap off¶
Turn a Zap off in Zapier and its subscription is removed for you. If you instead delete the endpoint on the Settings → Webhooks page, the Zap goes quiet without Zapier knowing — turn it off in Zapier too.