Skip to main content
All CollectionsIntegrations
Send all new feedback to a Slack channel
Send all new feedback to a Slack channel

How to leverage our API and Zapier to notify your team in Slack when new feedback is created in Harvestr.

Marina Salmon avatar
Written by Marina Salmon
Updated over 2 months ago

This tutorial explains how you can leverage Zapier and the Harvestr API to notify your teams by sending new feedback created in Harvestr to a Slack channel of your choice.

1. In Zapier, create a new Zap with "Catch Raw Hook" as the Trigger from Zapier Webhooks.

Copy the Webhook URL provided by Zapier.

2. Go to the Webhooks section of Harvestr and create a new FEEDBACK_CREATED webhook.

Copy the Zapier Webhook URL into the Request URL field of your Harvestr webhook and create the webhook.

If you want to send the feedback content, the associated customer, or other attributes to Slack, you'll need to fetch this information using the Harvestr API, as it's not directly available in the webhook response.

You'll therefore need to enrich your Zap with a few additional steps summarized here:

3. The next step allows you to convert the webhook data into a format that you can use later.

Steps 3 and 4 prevent sending notifications to Slack for feedback already sent from Slack. They are therefore optional.

Step 5 then allows you to fetch the feedback content via the API.

For the URL field, you must enter "https://rest.harvestr.io/v1/feedback/" followed by the variable corresponding to the feedback ID you retrieved earlier.

In the Headers field, you need to put "X-Harvestr-Private-App-Token" in the first box and your API token to read feedback in the second box.

To obtain this token, go to the Harvestr API settings.

Create a token of type Read feedback.

Copy the token, then paste it into Zapier.

The feedback retrieved from Harvestr will be in HTML format. If you want to convert it to Markdown format, which is readable by Slack, you can add an extra step and use Formatter by Zapier, which will handle the conversion.

Step 6 is also optional. It allows you to fetch the "Requester" if needed and display it in Slack. It works on the same principle as step 5, but this time with the "Read customer" API token.

You can also add another step to fetch the discovery title linked to the feedback if you would like to send it to Slack.

In step 7, you can construct the message you'll send to Slack using the information you retrieved in the previous steps: feedback content, requester, etc.

Did this answer your question?