Blog

Send website feedback to Zapier, then anywhere

When a client leaves a comment on a review link, you probably want it somewhere else too: a row in a spreadsheet, a card on a board, a task with someone's name on it. HTMLAnnotate can send every comment to Zapier as it happens, and Zapier can pass it on to almost any app you already use. This guide walks through the setup, shows what each comment looks like when it arrives, and covers a few common recipes.

Website feedback in Zapier: Every comment, sent to the apps you already use.
The short versionOn HTMLAnnotate Pro or Team, paste a Zapier Catch Hook URL into Webhooks on your Integrations page. From then on, new comments, replies, resolved comments, approvals and change requests on your pages are sent to Zapier within seconds, each with the page title, the review link, who wrote it, the comment text, the element it was pinned to and the screen size. In Zapier, add an action such as a Google Sheets row, a Trello card or an Asana task. It takes about ten minutes and no code.

What gets sent

Once it's connected, HTMLAnnotate sends a message to Zapier each time one of these happens on a page you own:

  • Someone leaves a new comment.
  • Someone replies to a comment.
  • A comment is marked resolved.
  • A reviewer approves the page, or asks for changes.

Each message carries the same set of fields, so you can map them once and reuse them. Here is what a new comment looks like when it reaches Zapier:

{
  "event": "comment.created",
  "at": "2026-11-19T06:22:10.000Z",
  "page": {
    "slug": "k3x9q2",
    "title": "Homepage v2",
    "reviewUrl": "https://htmlannotate.com/v/k3x9q2"
  },
  "by": "Maya",
  "comment": {
    "number": 4,
    "text": "Can the button say Book a call instead?",
    "element": "Get started",
    "screen": "mobile"
  }
}

The event field tells you what happened: comment.created, comment.replied, comment.resolved, page.approved or page.changes_requested. The screen field is desktop, tablet or mobile, whichever view the reviewer was in. For approvals and change requests there is no comment, so the comment field is empty. Zapier splits all of this into separate fields you can pick from in later steps, such as Page Title, Comment Text and Page Review URL.

Set it up in five steps

You need an HTMLAnnotate Pro or Team account, a Zapier account, and at least one review link you can comment on.

1. Start a Zap with a webhook trigger

In Zapier, create a new Zap. For the trigger, search for Webhooks by Zapier and choose the Catch Hook event. Leave the "Pick off a child key" box empty and continue. On the Test tab, Zapier shows a webhook URL. Copy it.

2. Paste the URL into HTMLAnnotate

In HTMLAnnotate, open Integrations from the sidebar and choose Webhooks. Paste the Zapier URL into the Webhook URL box and press Save.

3. Leave a real comment

The Send a test button checks that Zapier answers, but its message has no comment in it, so Zapier won't learn the comment fields from it. Open one of your review links instead and leave a short comment, such as "Testing Zapier". That sends a full comment.created message.

4. Test the trigger in Zapier

Back in Zapier, press Test trigger. You should see the comment you just left, with its page title, text and review link. If nothing shows up, check the URL in HTMLAnnotate matches the one in Zapier exactly, leave another comment, and test again.

5. Add an action and turn the Zap on

Add the step that does the work, for example a new row in Google Sheets, then map the fields and publish the Zap. A few recipes follow below.

Only act on new comments

Replies, resolved comments and approvals go to the same URL. If you only want a task for each new comment, add a Filter by Zapier step after the trigger and set it to continue only when Event exactly matches comment.created. You can build a second Zap with a filter on page.approved to tell your team when a client signs off. Filters make a Zap multi-step, which needs a paid Zapier plan.

Common recipes

A running log in Google Sheets

Add a Google Sheets step that creates a spreadsheet row. Make columns for the date, page, reviewer, comment, element, screen and link, and map each one to the matching field. You end up with one sheet that holds every comment across every project, which is handy for retainers and for reporting how many changes a client asked for.

A card or task for each comment

Add a step that creates a card in Trello, a task in Asana or ClickUp, or an issue in Jira. A setup that works well:

  • Title: the comment text, cut to the first line.
  • Description: the reviewer's name, the element, the screen size, and the review link.
  • List, project or assignee: fixed in the Zap, so new tasks don't need sorting by hand.

Put the review link in every task. Whoever picks it up opens the page and sees the comment pinned in place, at the right screen size, instead of guessing from a sentence. For more on running feedback through a task tool, see tracking website feedback in ClickUp or Notion.

A row in a Notion database

Add a Notion step that creates an item in a database. Give the database properties for Page, Comment, Reviewer, Screen and Link, and a Status property you set to "New" in the Zap.

An email when a client approves

With a filter on page.approved, add a Gmail or Outlook step that emails the project lead: "Maya approved Homepage v2", with the review link. It's a small thing that saves someone checking the page every hour on launch day.

Checking messages are really from HTMLAnnotate

The Webhooks panel on your Integrations page shows a signing secret under the address box. Each message carries an x-htmlannotate-signature header, which is a SHA-256 HMAC of the message body made with that secret. Zapier doesn't need it, since the Catch Hook URL is private to you. If you send webhooks to your own server instead, check the header before trusting the message. Keep the URL private either way, and if it leaks, make a new Zap and paste its URL in.

Good to know

  • Webhooks start from the moment you save the URL. Older comments aren't sent, but you can export them as a CSV.
  • New comments marked team only stay inside HTMLAnnotate and aren't sent.
  • Each account has one webhook URL. To send comments to several apps, add more actions in the same Zap, or use Zapier's Paths.
  • Messages are sent once. If Zapier is down or the Zap is off at that moment, that message isn't retried, so a spreadsheet log is a log of what arrived, and the review link stays the full record.
  • Every step in a Zap uses Zapier tasks. A busy review round with forty comments uses forty runs of the Zap.

Questions

Does HTMLAnnotate have a Zapier integration?

Yes, through webhooks. On Pro and Team you paste a Zapier Catch Hook URL into Webhooks on your Integrations page, and every new comment, reply, resolved comment, approval and change request is sent to Zapier. There is no HTMLAnnotate app to install in Zapier; the Webhooks by Zapier trigger does the job.

Which Zapier plan do I need?

Zapier marks Webhooks by Zapier as a premium app, and its pricing page lists webhooks and multi-step Zaps under the Professional plan, from $19.99 a month. Its help page also lists the webhook trigger on the Free plan, so check what your own account shows when you add the trigger. Checked 19 November 2026.

Which HTMLAnnotate plan do I need?

Pro or Team. Pro is $15 a month, or $12 a month billed yearly. Free accounts can see the Webhooks settings but can't save them.

What happens to comments left before I connected Zapier?

They aren't sent. Webhooks only carry what happens after you save the URL. To move older comments, export them as a CSV from the page's comment list, which works on every plan, and import that into your spreadsheet or task tool once.

Can I use Make or n8n instead?

Yes. Any tool that gives you a URL to receive webhooks works the same way: Make's Custom webhook, n8n's Webhook node, or your own server. Paste that URL into the same box.

Can I send comments to Slack as well?

Yes. The Integrations page also connects Slack, Discord and Google Chat. You can use any of them alongside Zapier.

Want feedback that arrives with the page, the element and the screen size attached? Send a review link where clients click the page to comment, with no account.

Start a free review