Alerts and automation
CueScout in Slack
Once a week, into the channel: your share of AI answers, which way it moved against the previous window, and the competitors that appeared for questions you are absent from. The same reading as the digest email, cut to the length a channel will actually read.
It is deliberately weekly. A share-of-voice number over eight questions moves several points when one answer flips, so a daily version of this would be a channel full of noise that everybody mutes inside a fortnight — and a muted channel takes the email's attention with it.
Where the URL comes from: A Slack app with Incoming Webhooks turned on, then Add New Webhook to Workspace
Setting it up
1.Create the incoming webhook in Slack
api.slack.com/apps → Create New App → From scratch, pick the workspace, then Incoming Webhooks → Activate → Add New Webhook to Workspace and choose the channel. Slack gives you a URL ending in a long token; that is what you paste.
2.Paste it into CueScout
Settings → Webhook, with the format set to Slack. That is what switches the body to Block Kit — sending the plain JSON to a Slack URL posts either nothing or an unreadable code block, and both look like the integration is broken.
3.Send a test
The test button runs the real delivery path, so a message in the channel means the weekly one will arrive too. If Slack rejects it, its own error text is shown — invalid_token almost always means the webhook was revoked.
What this does not do
- The Slack URL is a secret. Anybody who has it can post to that channel, which is why it is never shown anywhere in CueScout after you save it.
- One channel per product. Routing the same product to two channels needs two destinations, which is not something this supports.
- 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 not a Slack app I can install?
An incoming webhook needs no OAuth, no scopes and no review, and it does exactly what is needed here: post a message. An installable app would be more work for you and for us to do the same thing.
Can I get an alert the moment we drop out of an answer?
No, and it would mislead you if you could. A single answer flipping moves the number by several points on a normal question set — the weekly reading is smoothed enough to mean something, and the instant one would not be.
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
Discord
A channel webhook and the plain JSON body, once a week.
Alerts and automationZapier
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.
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.