This tutorial shows how to use Zapier and the Harvestr API to notify your team in Slack whenever new feedback is created in Harvestr.
This is the outgoing direction: Harvestr → Slack.
If you want the opposite — sending feedback from Slack into Harvestr — use our native Slack integration instead. It's a proper integration, not a Zapier recipe, and it also handles feedback loop notifications back to the thread.
The two are complementary and can run side by side.
Prerequisites
a Zapier account on a paid plan (webhook triggers aren't available on the Free plan)
a Harvestr Editor account
a Harvestr API Access Token with the
read_feedbackscope — andread_customerif you want to show who submitted the feedback
Step 1: Create the Zap and get your webhook URL
In Zapier, create a new Zap with Catch Raw Hook as the trigger, from Webhooks by Zapier.
Copy the Webhook URL that Zapier gives you.
Step 2: Create the webhook in Harvestr
Go to the Webhooks section of Harvestr and create a new FEEDBACK_CREATED webhook.
Paste the Zapier webhook URL into the Request URL field and create the webhook.
The webhook payload doesn't contain the feedback content. To send the content, the customer, or any other attribute to Slack, you have to fetch it from the Harvestr API in a later step. That's what the rest of this tutorial covers.
Here's the finished Zap, for reference:
Step 3: Parse the webhook data
This step converts the raw webhook payload into a format you can reference in later steps.
Step 4 (optional): Filter out feedback that came from Slack
Without this, feedback submitted from Slack gets posted straight back to Slack. These filter steps prevent that loop.
Skip them if you don't use the native Slack integration.
Step 5: Fetch the feedback content from the API
Add a webhook GET step to retrieve the feedback.
Configure it as follows:
URL:
https://rest.harvestr.io/v1/feedback/followed by the variable holding the feedback ID you parsed earlierHeader name:
X-Harvestr-Private-App-TokenHeader value: your API token
To create the token, go to your Harvestr API settings and create one with the read feedback scope.
The feedback content comes back as HTML. Slack doesn't render HTML. Add a Formatter by Zapier step to convert it to Markdown before posting.
Step 6 (optional): Fetch the requester
If you want to show who submitted the feedback, add another GET step on the same principle as step 5, this time with a token carrying the read customer scope.
You can add a further step to fetch the title of the linked Discovery if you want that in the Slack message too.
Step 7: Post to Slack
Add a Slack action and build your message from everything you gathered: feedback content, requester, linked Discovery, and so on.
Test the Zap, then turn it on.
Full API reference at developers.harvestr.io, including the webhook event list and required scopes.










