Skip to content

Website Change Alerts in Make: Custom Webhook Scenario

Send AyeWatch website change alerts into a Make scenario with the Custom webhook module. Covers setup, what Make replies to AyeWatch, the signature limit and what each alert costs.

By AyeWatch Team5 min read

Short answer: To get website change alerts into Make, create a scenario that starts with the Webhooks module's Custom webhook, paste the address Make generates into AyeWatch's webhook settings, and add the module that should act on the alert. Make replies 200 Accepted once it queues a delivery. Webhooks need a paid AyeWatch plan.

How a Make scenario receives an AyeWatch alert

Make's Webhooks app has a Custom webhook module. When you add one and save it, Make generates a URL and starts listening for requests. AyeWatch posts a JSON body to that URL each time a monitor detects new content. Each AyeWatch account has one webhook that receives updates from every monitor, so one scenario sees them all. Add a filter on topic_id if a scenario should act on only one monitor.

AyeWatch sends nothing when a check finds no change, so a quiet page costs you no scenario runs.

The module settings that matter

  • Data structure: Make can learn it from the first delivery, or you can define it yourself. Letting Make learn it from a real alert is quicker. Use Detect new values later if a field such as trigger shows up for the first time.
  • Get request headers: under Advanced settings, select Yes if a later module needs a header. Make reserves the x-make-apikey name.
  • API key authentication: leave it off. Make's key arrives in an x-make-apikey header, and AyeWatch sends only the content type and its signature header.

The payload fields are the ones in the webhook docs: topic_id, topic_name, update_id, headline, content, created_at and optional extras such as evidence.

A sample rule and the alert Make receives

Sample rule: Alert me when Cobalt Freight's service notices page adds a delay, a cancelled route or a new port closure. Ignore holiday greetings and office address changes.

{
  "topic_id": 6013,
  "topic_name": "https://cobaltfreight.example/service-notices",
  "update_id": 102877,
  "headline": "Cobalt Freight suspends the Rotterdam to Leeds service",
  "content": "A new notice says the Rotterdam to Leeds weekly service is suspended from 4 December because of a vessel refit. Bookings move to the Hull route.",
  "created_at": "2026-11-27T14:10:00Z",
  "evidence": [
    { "quote": "Rotterdam to Leeds suspended from 4 December", "source_url": "https://cobaltfreight.example/service-notices" }
  ]
}

Map headline and content into the next module: a message, a spreadsheet row or a ticket. The Google Sheets guide shows the row layout.

What Make replies, and what AyeWatch does about it

AyeWatch treats any non-2xx reply or a timeout as a failed delivery, retries with exponential backoff up to 10 attempts and does not follow redirects. Its time limit is 10 seconds. Make's documented replies fit that well in the normal case: it answers 200 with the body Accepted once the request is queued, and 400 with "Queue is full." when the queue has no room. The 400 is a failed delivery, so AyeWatch tries again later and the alert is not lost.

The one setting to avoid is a Webhook response module that waits for a slow scenario. Make's own timeout for that reply is 180 seconds, and AyeWatch gives up after 10.

Signatures and the address as a secret

AyeWatch's signature is an HMAC-SHA256 over the exact bytes it sent. In the standard Make setup the scenario receives parsed fields, not those bytes, so a byte-exact check is not part of it. Treat the generated address like a password: do not paste it in chat or commit it to a repository, and if it leaks, create a new webhook in Make and save the new address in AyeWatch. AyeWatch emails the account owner whenever the webhook URL is set or changed.

If you need to verify every request, use n8n, where a Crypto node can check the signature, or the raw hook in Zapier.

When Make is the wrong tool

  • You must verify every request. Use n8n or a small relay that checks the signature.
  • The destination is Slack. AyeWatch's own Slack connection needs no scenario. See the Slack guide.
  • Replies that depend on later steps. AyeWatch's 10-second limit is shorter than a long scenario.
  • 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. Make meters usage by the modules a scenario runs, so one alert that passes through a webhook module and a Sheets module counts more than one module run. Check Make's pricing page for the unit and the plan limits. The scenario takes a few minutes to build once you have a real alert to learn from.

Set up the scenario in six steps

  1. In Make, create a scenario and add Webhooks, then Custom webhook. Select Add, name the webhook and select Save. Copy the address.
  2. In AyeWatch, create the monitor and write the rule. Open Notification settings, Webhook, paste the address and select Save Webhook.
  3. Back in Make, select Run once so the module waits for a request. AyeWatch has no test button, so the next real update teaches Make the data structure.
  4. Add the module that acts on the alert, such as Google Sheets, Add a Row, and map headline, content and the other fields from the webhook output.
  5. Add a filter on topic_id if the scenario is for one monitor only.
  6. Switch the scenario on, then use its History to confirm each alert ran.
Make replyMeaningWhat AyeWatch does
200, body AcceptedMake queued the requestCounts it as delivered
400, body Queue is full.The webhook queue has no roomRetries with backoff, up to 10 attempts
No reply within 10 secondsA Webhook response module is waiting on a slow scenarioTreats it as failed and retries
3xx redirect set in a Webhook response moduleMake can answer with a Location headerDoes not follow it, so the delivery counts as failed

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 days

The bottom line

Add the Custom webhook, select Run once and save the address in AyeWatch. When the first real alert arrives, build the one module you need and switch the scenario on.

FAQ

Which Make module receives an AyeWatch alert?

The Webhooks module's Custom webhook trigger. Make generates the URL you paste into AyeWatch's webhook settings.

Does Make check the AyeWatch signature?

Not in the standard setup, because the scenario receives parsed fields rather than the raw bytes the HMAC covers. Use n8n or Zapier's Catch Raw Hook if you need that check.

Should I turn on API key authentication on the Make webhook?

No. Make expects its key in an x-make-apikey header, and AyeWatch cannot add custom headers to a delivery.

What happens if Make's queue is full?

Make replies 400 and AyeWatch retries with exponential backoff for up to 10 attempts.

Why does my scenario not get anything after I save the webhook?

AyeWatch sends a request only when it detects new content, and it has no test button. Run the scenario once and wait for the next real update.

website change alerts makemake.com webhook website changemake custom webhook website monitormonitor a website and trigger a make scenario

Related articles