Website Change Alerts in n8n: Webhook Node Setup
Receive AyeWatch website change alerts in n8n with the Webhook node. Set the node, check the X-AyeWatch-Signature header with the Crypto node and send each alert on.
By AyeWatch Team4 min read
Short answer: To get website change alerts into n8n, add a Webhook node set to POST, paste its Production URL into AyeWatch's webhook settings, and publish the workflow. Add a Crypto node to check the X-AyeWatch-Signature header before any other step. Webhooks need a paid AyeWatch plan.
The workflow in four nodes
A workable layout is short. A Webhook node receives the POST. A Crypto node computes the HMAC of the raw body. An IF node compares it with the header. Whatever you want to do with the alert comes after the IF node's true branch: send a message, add a row or create a ticket. The false branch stays empty, so a forged request goes nowhere.
AyeWatch sends a request only when it detects new content for a monitor, and each account has one webhook that receives updates from every monitor. If you run several monitors, add a Switch node on topic_id after the check.
Webhook node settings
- HTTP Method: POST, the method AyeWatch uses.
- Path: n8n generates a random path by default. Keep it. It is a second barrier, because AyeWatch cannot send a custom auth header.
- Respond: Immediately. n8n answers with a success code and the text "Workflow got started", which keeps you inside AyeWatch's 10-second limit even when later nodes are slow.
- Options, Raw Body: on. The signature covers the exact bytes AyeWatch sent, and a parsed copy can differ from them.
The node has two URLs. The Test URL listens after you select Listen for Test Event. The Production URL registers when you publish the workflow, which older n8n versions call activating it. Paste the Production URL into AyeWatch. Production runs do not show data in the editor, so read them under Executions.
Check the signature
AyeWatch sends X-AyeWatch-Signature: sha256= followed by the HMAC-SHA256 of the raw body in hex. In n8n, add a Crypto node with these settings, then an IF node.
Crypto node
Action: Hmac
Binary File: on (the Webhook node's raw body)
Type: SHA256
Property Name: signature
Encoding: HEX
Credential: Crypto credentials, Hmac Secret = your AyeWatch secret
IF node (string, equals)
Value 1: {{ $json.headers['x-ayewatch-signature'] }}
Value 2: {{ 'sha256=' + $json.signature }}
Copy the secret from the Signing Secret box on the AyeWatch webhook screen, using Reveal and Copy. Node.js lowercases header names, so the header key is written in lowercase. With Raw Body on, the JSON arrives as binary data, so add an Extract From File node set to JSON after the IF node to turn the bytes back into fields. Test it once with a real alert and look at the IF node's output.
Sample rule and the alert n8n receives
Sample rule: Alert me when Pinewave's API changelog adds a breaking change or a deprecation date. Ignore new features and spelling fixes.
A made-up delivery for that rule looks like this:
{
"topic_id": 5120,
"topic_name": "https://docs.pinewave.example/changelog",
"update_id": 91344,
"headline": "Pinewave deprecates the v1 events endpoint",
"content": "The changelog lists /v1/events as deprecated with removal on 2027-03-01. The v2 endpoint is the replacement.",
"created_at": "2026-11-27T13:20:00Z",
"trigger": "breaking change or deprecation date"
}
When n8n is the wrong tool
- Retries after a later failure. With Respond set to Immediately, AyeWatch sees a 2xx before your later nodes run. If the Notion or Sheets step fails, AyeWatch will not resend. Check the Executions list often, or answer with a Respond to Webhook node after the steps that must succeed.
- A server on your laptop. AyeWatch rejects private, loopback and internal addresses and needs a public HTTPS URL.
- You would rather not host anything. The Slack integration is built in on paid plans and needs no workflow.
- Pages behind a login. AyeWatch reads public pages and cannot sign in.
Cost and effort
AyeWatch Pro is $9/mo with 50 topics and hourly checks; Pro+ is $19/mo with 200 topics and ASAP mode. Every plan starts with a 7-day free trial. Most checks use 1 credit. n8n can be self-hosted or used as a hosted service, and its plans and limits change, so check n8n's pricing page. The four-node check takes about half an hour the first time.
Build the receiving workflow
- Create a workflow and add a Webhook node. Set HTTP Method to POST, Respond to Immediately, and turn on Raw Body.
- Select Listen for Test Event so the node waits for a request and shows its Test URL.
- Open Notification settings, Webhook in AyeWatch, paste the URL and select Save Webhook. Reveal the signing secret and store it in a Crypto credential.
- Add the Crypto node and the IF node from the settings above. Add your action after the true branch.
- Publish the workflow, copy the Production URL from the Webhook node and paste it into AyeWatch in place of the test one.
- Wait for a real update, then open Executions and confirm the run passed the IF node.
| Node | Setting | Value |
|---|---|---|
| Webhook | HTTP Method | POST |
| Webhook | Respond | Immediately |
| Webhook | Options, Raw Body | On |
| Crypto | Action, Type, Encoding | Hmac, SHA256, HEX |
| IF | Compare | x-ayewatch-signature header with sha256= plus the computed value |
| Your action | After the true branch | Slack, Telegram, Sheets, Notion or anything else |
Start a monitor in under a minute
Describe a topic or paste a URL. Cancel before the trial ends and you pay nothing.
Try it free for 7 daysThe bottom line
Build the Webhook node first and send yourself one real alert before you add the signature check. Add the Crypto and IF nodes next, and only then connect the action you care about.
FAQ
Which n8n node receives an AyeWatch alert?
The Webhook node, set to the POST method. Paste its Production URL into AyeWatch's webhook settings and publish the workflow.
Can n8n check the X-AyeWatch-Signature header?
Yes. Turn on Raw Body in the Webhook node, compute an HMAC with SHA256 and HEX encoding in the Crypto node, and compare it with the header in an IF node.
Why does my workflow not run from the Test URL after I publish it?
The Test URL only listens while the editor waits for a test event. Once the workflow is published, use the Production URL in AyeWatch.
Can I run n8n on localhost to receive alerts?
No. AyeWatch needs a public HTTPS URL and rejects private, loopback and internal addresses.
What does AyeWatch do if my workflow is down?
AyeWatch retries failed deliveries with exponential backoff for up to 10 attempts. Update_id stays the same on a retry, so use it to skip repeats.