With Zapier, you can send product feedback from other apps directly into your Harvestr inbox, no code required.
A few examples of what you can set up:
send survey responses (from Typeform, for instance) to your inbox as new feedback
push conversations from support tools we don't integrate natively, like Help Scout or Front
bring in reviews from platforms like Trustpilot
Check for a native integration first. Slack, Zendesk, Intercom, Freshdesk, Microsoft Teams, Jira, Linear, GitHub, GitLab, Trello, HubSpot, Salesforce and our call-recorder integrations all connect directly, with no Zapier account needed and richer features than a Zap can offer.
See the full list in Integrations. For bulk historical data, our Excel and CSV import is a better fit than a Zap.
Prerequisites
a Zapier account
a Harvestr Editor account
an account with the app you want to connect
How Zapier works with Harvestr
A Zap is made of two parts:
Trigger — an event in one app (a new spreadsheet row in Google Sheets, for example)
Action — what Zapier does in response (create feedback in Harvestr)
Harvestr provides a Zapier action: Create Message, which sends a new piece of feedback to your inbox.
Harvestr does not provide a Zapier trigger. You can send feedback into Harvestr with a Zap, but you can't start a Zap from a Harvestr event through the app.
To trigger something when feedback arrives in Harvestr, use a webhook pointing at a Catch Hook trigger in Zapier. Pushing new feedback to a Slack channel shows that pattern end to end.
How to create a Zap between Harvestr and another app
You can either build your own Zap, or start from one of our pre-built templates.
Method 1: build your own Zap
Step A — Create a new Zap
Start a new Zap in your Zapier dashboard.
Step B — Choose your trigger app and event
Connect the app where the feedback originates and choose a trigger. For example:
Google Sheets: New Spreadsheet Row, or New/Updated Row
Help Scout: New Conversation
Typeform: New Entry
Webhooks by Zapier: Catch Hook, for any tool that can send a webhook
Step C — Set Harvestr as the action
Search for the Harvestr app in the action step and select Create Message.
Then map the data from your trigger app onto the Harvestr fields.
Field | Required? | Description |
Source type | ✅ | Choose a source. If unsure, select "Note". |
Requester name, email, or company | ✅ (at least one) | The customer who gave the feedback |
Submitter name and/or email | Optional | The teammate who submitted it |
Content | ✅ | The main body of the feedback |
Title | ✅ | A short title summarizing the feedback |
Labels | Optional | Labels to help categorize the feedback |
Discoveries | Optional | Link the feedback to an existing discovery |
Message URL | Optional | A link back to the source, for traceability. Worth filling whenever you can. |
Required fields must be filled, either with data from the trigger app or with a custom value. If one is left blank, the Zap fails.
Map the real customer as the requester whenever the trigger app gives you one. Using a generic placeholder collapses every item onto a single fake customer, which makes customer segments and Rollup fields meaningless for that channel.
Step D — Test and turn your Zap on
Run a test to check everything works, then turn the Zap on. New feedback will flow into your inbox automatically.
Method 2: use our pre-built templates
To save time, start from a ready-made Zap template.
Go to your Zapier integration settings in Harvestr and click Use this workflow on any suggested integration.
This opens the Zap editor with some fields pre-filled. You just connect your accounts and review the field mappings as described in Method 1.
Step-by-step recipes
We've documented several Zaps end to end:
Recipe | Direction |
Into Harvestr | |
Into Harvestr | |
Out of Harvestr | |
Status sync | |
Status sync |
For anything beyond what the Zapier action covers, see our API documentation or Zapier's Help Center.

