Alerts and automation
CueScout in Zapier
Zapier's Catch Hook trigger gives you a URL, and CueScout posts the weekly event to it as flat JSON. Every field is top-level and named for what it is, because a nested object costs you a mapping step for no benefit.
The two fields worth building on are visibility_pct and delta. A filter on "delta is less than -5" turns this into an alert about losing ground rather than a weekly log entry nobody opens.
Where the URL comes from: A Zap with the "Webhooks by Zapier" trigger, Catch Hook
Setting it up
1.Create the Zap with a Catch Hook trigger
Webhooks by Zapier → Catch Hook. Zapier gives you a URL immediately; copy it before adding any actions.
2.Paste it into CueScout and send a test
Settings → Webhook, generic format. Then press the test button — Zapier needs a real request before it will show you the fields, and the test sends one.
3.Filter on the move, not the message
Add a Filter step on delta so the Zap only continues when the number actually went somewhere. A Zap that runs every week regardless is a Zap somebody turns off.
Zapier filter step
Filter: delta (number) less than -5
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
- The test event has event: "test" rather than "weekly.moved". Filter on the event field if you do not want tests reaching your production Zap.
- Catch Hook is available on Zapier's free plan; the multi-step Zaps that make it useful mostly are not.
- 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
Is there a CueScout app in the Zapier directory?
No. A published integration is a maintenance commitment we have not earned yet with one event to send. Catch Hook does the same job today.
Which fields should I map?
visibility_pct and delta for the numbers, headline for a sentence a human can read, and answers plus questions if you want the sample size travelling with the figure — which you do, because the number is small-sample often enough to matter.
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
Make
A custom webhook module, then whatever your scenario already does.
Alerts and automationn8n
A Webhook node, and the one place signature verification is worth actually doing.
Alerts and automationSlack
A formatted weekly message: the number, which way it moved, and who turned up where you are not.
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.