Skip to content

Connect Zapier to Your Testimonial Workflow Without Code

When a customer submits a testimonial, the next steps — filing it, notifying your team, or thanking the customer — should not need manual copying. This guide shows how a no-code automation connects a testimonial collection page to other apps through Zapier, using a new-testimonial trigger and an API key for authentication.

Why connect the two tools?

Zapier is built around automating multi-step workflows without writing code, while a testimonial tool focuses on collecting and managing customer praise in one place. Together, they let a submission in one system start work in another — for example, filing the testimonial in cloud storage or sending a thank-you email — instead of leaving it as a manual follow-up.

Step-by-step setup checklist

  1. Open the dashboard and go to the integrations area, then the Zapier tab. 2) Select Generate API Key and copy the generated key. 3) In Zapier, open the testimonial app and paste the key to authenticate. 4) Create a new Zap and set the app event to New Incoming Testimonial. 5) Choose a wall from the Wall URL dropdown, or leave it blank to cover every wall. 6) Choose text, video, or All for testimonial type, or leave it blank. 7) Test the trigger, add your next task, save, and publish.

Choosing the right filter settings

Use the wall and type filters as a routing decision, not just setup options. A single-wall, video-only Zap suits a campaign page where you want immediate filing or alerts. A blank wall with All types suits a general inbox where every submission should reach storage, email, or a team channel. If a Zap fires unexpectedly, check those two filters first — they are the most likely reason a testimonial was included or excluded.

Example: from submission to filing

Worked example: a customer submits a video testimonial through a collection page. With the trigger set to New Incoming Testimonial, no wall restriction, and All types, the Zap starts. The next task saves the testimonial to Google Drive, as in the captured walkthrough. A different Zap could instead send a thank-you email. The testimonial itself still lives in the testimonial tool for display on your website; Zapier handles the downstream action.

Trigger filter decision table
SettingChoose this whenEffect
Wall URL: specific wallYou run separate campaigns or pagesOnly testimonials from that wall start the Zap
Wall URL: blankYou want one central workflowTestimonials from any wall start the Zap
Testimonial type: text or videoYou handle formats differentlyOnly that format starts the Zap
Testimonial type: All or blankYou want complete coverageEvery type starts the Zap

Filters as described in captured walkthrough; confirm current field labels in Zapier before publishing.

Frequently asked questions

Where do I get the API key for Zapier?

Open the dashboard integrations area, find the Zapier tab, and use Generate API Key. The captured workflow notes the key is visible on a paid plan; confirm your current plan eligibility before relying on it.

Which trigger starts the automation?

Choose New Incoming Testimonial as the app event, authenticate with the copied key, then narrow the trigger by wall and by text, video, or all types.

How do I limit a Zap to one wall or one testimonial type?

Select a specific wall to watch only that wall, or leave the wall field blank to receive testimonials from any wall. Similarly, pick a type or leave it blank / choose All for no type filter.

What happens after I publish the Zap?

Test the trigger, add the next task — for example saving the testimonial to Google Drive or sending a thank-you email — then publish. The Zap then runs whenever a matching testimonial arrives.