Feedback Guardian

Acme Coffee Co.

Demo

Overview

Dashboard19AnalyticsLocations

Feedback Points

Downtown Cafe

Front Counter5Drive-Through4Outdoor Patio2

Eastside Roastery

Order Counter4Bathroom4

Manage

TeamBillingAccountBrandingIntegrationsAudit Log

Support

DocumentationGuidesFAQSupport
Theme

Sarah Johnson

Owner

sarah@acmecoffee.com

Start Free Trial
Feedback Guardian
You're exploring with sample data — some features are disabled. Start a free trial for the full experience.
Try Feedback FormStart Free Trial →

Integrations

Send new feedback to Slack, Microsoft Teams, Zapier, Make, or n8n. This demo uses sample data. Connecting a real address happens in your account.

Add a connection

Paste a webhook address, name it, and choose which feedback to send. You can add five.

Destination

Paste the address from Zapier, Make, or n8n. It must start with https://.

A name only you see, so you can tell your connections apart.

Events

All ratings, or only the low scores. Happy ratings can stay in the dashboard.

Locations

Leave every box unchecked to send events from all locations.

Zapier to Slack

Custom webhook

On · response.created, response.comment_added · 3 stars and below

Zapier, Make, and n8n do not need this. Copy it only if your own server checks that each request really came from Feedback Guardian.

Recent deliveries

Sample deliveries from the demo cafe. Replay sends that same delivery again.

  • response.created · succeeded · HTTP 200 · Today, 2:14 PM
  • response.comment_added · succeeded · HTTP 200 · Today, 2:14 PM
  • ping · succeeded · HTTP 200 · Yesterday, 9:02 AM

Front desk Slack

Slack

On · response.created, response.comment_added · 3 stars and below

Recent deliveries

  • response.created · succeeded · HTTP 200 · Today, 2:14 PM
  • response.comment_added · succeeded · HTTP 200 · Today, 2:14 PM
  • ping · succeeded · HTTP 200 · Yesterday, 9:02 AM

Setup guide

Open a section while you connect a service. The form stays on the left.

How this page works▾

A connection is a destination for new feedback. It can be Slack, Microsoft Teams, or a webhook address from Zapier, Make, or n8n. Choose what to send, and Feedback Guardian posts each matching response there. You can add up to five.

  • Webhook URL. The address the other service gives you. It has to start with https://. Keep it private. Anyone with the address can send fake data into that Zap, scenario, or workflow.
  • Label. A name only you see, such as “Zapier to Slack”.
  • New response. Sent the moment a guest saves a rating, even if they have not written a comment yet.
  • Follow-up comment. Sent a moment later if a low rating gets a comment on the follow-up screen. It is the same visit, so both messages share the same response id.
  • Ratings. Leave this on all ratings, or send only the low ones. A restaurant often sends 1–3 stars to Slack and leaves the happy ratings in the dashboard.
  • Locations. Shown when you have more than one. Leave them all unchecked to include every location.
  • Send test. Posts a small ping so you can confirm the connection before a real guest responds.
  • Recent deliveries. What we tried to send, and whether it arrived. Replay sends that same delivery again.
  • Turn off. Pauses delivery without deleting the connection. If an address keeps failing, we turn it off and email the account owner.
Connect Slack▾
  1. In Slack, open the channel that should receive feedback.
  2. Open the channel’s Integrations, then Incoming Webhooks, and add one if the channel does not have one.
  3. Copy the webhook address. It starts with https://hooks.slack.com/services/.
  4. On this page choose Slack, paste the address, and name it.
  5. Leave both events on, or limit the ratings. A restaurant often sends only 1–3 stars.
  6. Click Add connection, then Send test. The channel should show “Feedback Guardian is connected.”
Connect Microsoft Teams▾
  1. In Teams, open the channel that should receive feedback.
  2. Open Workflows and choose the template Post to a channel when a webhook request is received.
  3. Copy the address the template shows. Use that template. A blank HTTP trigger will not understand the card.
  4. On this page choose Microsoft Teams, paste the address, and name it.
  5. Click Add connection, then Send test. The channel should show “Feedback Guardian is connected.”
Connect Zapier▾
  1. In Zapier, create a Zap. For the trigger, choose Webhooks by Zapier, then Catch Hook.
  2. Continue until Zapier shows a custom webhook URL. Copy it.
  3. Paste that URL here, give it a label, leave both events checked, and click Add endpoint.
  4. Back in Zapier, click Test trigger. If it is waiting for a sample, click Send test on this page, then test the trigger again.
  5. Add the action you want, such as Slack, Google Sheets, or email. Map the rating, comment, contact name, phone, location, and feedback point.
  6. Publish the Zap. Zapier does not ask for the signing secret.
Connect Make▾
  1. In Make, create a scenario. Add Webhooks, then Custom webhook.
  2. Add a webhook and copy the address Make shows.
  3. Paste it here and click Add endpoint.
  4. In Make, click Run once. Then click Send test on this page. Make reads the fields from that test.
  5. Add the next module and map those fields. Save the scenario and turn it on.
  6. Make does not ask for the signing secret.
Connect n8n▾
  1. In n8n, create a workflow and add a Webhook node. Set the method to POST.
  2. Click Listen for test event and copy the Test URL.
  3. Paste that Test URL here, add the endpoint, and click Send test. n8n shows the fields it received.
  4. Build the rest of the workflow from those fields.
  5. When you are ready to leave it running, copy the Production URL from the same Webhook node. Edit the endpoint on this page and replace the Test URL with the Production URL.
  6. Activate the workflow. The Test URL only works while you are listening. n8n does not ask for the signing secret.
What a message looks like▾

A guest rates Table 4 at Downtown a 2 and leaves a phone number. The first message has no comment yet:

New feedback at Downtown, Table 4: 2 stars (Sad). Alex Rivera asked to be called at 555-0100. No comment yet.

Twenty seconds later they add a comment. The second message uses the same response id:

Follow-up from the same visit: “The fries were cold.”

In Zapier, Make, and n8n the fields arrive inside data. The useful ones are data.rating, data.rating_label, data.comment, data.contact.name, data.contact.email, data.contact.phone, data.location.name, and data.feedback_point.name. Match the two events on data.id.

Sample: new rating
{
  "id": "evt_8f3c1a0e9b2d4f6a8c0e1b2d3f4a5c6d",
  "type": "response.created",
  "created_at": "2026-09-26T15:04:00.000Z",
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "rating": 2,
    "rating_label": "Sad",
    "comment": null,
    "is_follow_up_comment": false,
    "contact_requested": true,
    "contact": {
      "name": "Alex Rivera",
      "email": "alex@example.com",
      "phone": "555-0100",
      "preference": "call"
    },
    "feedback_point": { "id": "a1b2c3d4e5f6", "name": "Table 4" },
    "location": { "id": "8c1d2e3f-4a5b-6c7d-8e9f-0a1b2c3d4e5f", "name": "Downtown" },
    "created_at": "2026-09-26T15:04:00.000Z",
    "url": "https://feedbackguardian.com/dashboard/feedback/a1b2c3d4e5f6"
  }
}
Sample: follow-up comment
{
  "id": "evt_1a2b3c4d5e6f708192a3b4c5d6e7f809",
  "type": "response.comment_added",
  "created_at": "2026-09-26T15:04:20.000Z",
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "rating": 2,
    "rating_label": "Sad",
    "comment": "The fries were cold.",
    "is_follow_up_comment": true,
    "contact_requested": true,
    "contact": {
      "name": "Alex Rivera",
      "email": "alex@example.com",
      "phone": "555-0100",
      "preference": "call"
    },
    "feedback_point": { "id": "a1b2c3d4e5f6", "name": "Table 4" },
    "location": { "id": "8c1d2e3f-4a5b-6c7d-8e9f-0a1b2c3d4e5f", "name": "Downtown" },
    "created_at": "2026-09-26T15:04:00.000Z",
    "url": "https://feedbackguardian.com/dashboard/feedback/a1b2c3d4e5f6"
  }
}
Sample: test ping
{
  "id": "evt_test_ab12cd34ef56",
  "type": "ping",
  "created_at": "2026-09-26T15:05:00.000Z",
  "data": { "ok": true }
}
What the signing secret is▾

The signing secret is a password for that endpoint. Feedback Guardian uses it to stamp every request. You can see it, copy it, and replace it. Replacing it turns the old stamp off immediately.

Zapier, Make, n8n, Slack, and Teams ignore the stamp. They trust the URL. Leave the secret on this page unless you are sending feedback to a server you run yourself.

On your own server, recompute the stamp and ignore the request if it does not match. That stops someone who finds the URL from posting a fake review. The stamp is in the header X-FeedbackGuardian-Signature, after v1=. It is the HMAC-SHA256 of the timestamp, a period, and the raw body, using this secret. The timestamp is in X-FeedbackGuardian-Timestamp. Reject anything older than a few minutes.

© 2026 Feedback Guardian