Alerts and automation
CueScout in Make
Make's Custom Webhook module gives you a URL and infers the data structure from the first request it receives. CueScout's payload is flat, so the structure Make derives is usable without any further shaping.
Send the test before you build the rest of the scenario. Make will not show you the fields until it has seen a real request, and building against a guessed structure is how a scenario ends up mapping fields that never arrive.
Where the URL comes from: A scenario starting with the Custom Webhook module
Setting it up
1.Add a Custom Webhook module
New scenario → Webhooks → Custom webhook → Add. Copy the URL it generates.
2.Paste it into CueScout, then press test while Make is listening
Settings → Webhook, generic format. Make's "Determine data structure" state waits for one request — the test button sends it, and Make then knows every field.
3.Branch on the numbers
A router with a filter on delta separates "we lost ground" from "nothing much happened", which is the difference between a scenario worth having and a weekly no-op.
What arrives
One POST a week. Every field is top-level, because a nested object costs you a mapping step for no benefit. visibility_pct and delta are the two worth building a filter on.
Request body
{
"event": "weekly.moved",
"sent_at": "2026-08-14T09:00:00Z",
"product_id": "5f0e…",
"product": "Acme",
"headline": "You are in 41% of AI answers, down 6 points on the previous window.",
"detail": [
"Rival turned up for \"best tool for x\", where you are absent.",
"Your page \"The guide\" is now being cited."
],
"url": "https://cuescout.com/insights/geo",
"visibility_pct": 41,
"delta": -6,
"questions": 8,
"answers": 11,
"low_sample": true
}What this does not do
- Make queues incoming webhook data. If the scenario is off, the message waits in the queue rather than being lost — which is also how a switched-off scenario accumulates a month of them.
- The test event has event: "test". Filter on it if that matters to your scenario.
- One destination per product, and one event: the weekly what-moved reading. There is no per-event subscription list.
- It fires once a week, with the digest email. This is not a real-time feed.
- No retries. A failed delivery is recorded with the destination's own error text on the settings screen, and the next attempt is next week.
- Delivery history is the last attempt only. There is no log to page through.
Frequently asked questions
Why does Make show no fields?
It has not received a request yet. Put the webhook module into its listening state and press the test button in CueScout.
How often does it fire?
Once per week per product, at the same time the digest email goes out. The email decides there is something worth saying and the webhook rides that decision, which is also why it cannot double-send.
How do I know it is really CueScout?
Every request carries an X-CueScout-Signature header: an HMAC-SHA256 of the exact body, under a secret shown on the settings screen. Verify it if your endpoint is public — otherwise the URL is the only thing protecting your numbers from anybody who guesses it.
What happens if my endpoint is down?
The delivery is recorded as failed, with whatever your server said, and nothing is retried. You will see it on the settings screen; the next message is next week.
Related
Zapier
Catch Hook, then map visibility_pct and delta into whatever you already run.
Alerts and automationn8n
A Webhook node, and the one place signature verification is worth actually doing.
Alerts and automationDiscord
A channel webhook and the plain JSON body, once a week.
Run the checks on your own site
The readiness check is free, needs no signup, and takes about half a minute. It works out what your site is built on and gives you the fixes written for it.