monitor.result.found event. The handler checks the signature and posts the page to a Slack incoming webhook.
Recipe prompt
Paste this into your coding agent to have it build the recipe in your project:Recipe prompt
What you build
You need a Keenable API key, a Slack incoming webhook URL and a public HTTPS address for your handler.
When it runs
On everymonitor.result.found event: minutes after Keenable crawls a page that reports something new about the topic. A monitor matches only pages crawled after you create it, so the first message can take minutes to hours. It sends each story once, with the first page that carries it.
Code
This handler verifies each delivery and posts everymonitor.result.found page to Slack. The curl tab checks the Slack webhook, then creates the monitor that points at your handler. Replace https://hooks.example.com/keenable with your handler’s public address:
KEENABLE_WEBHOOK_SECRET to the webhook.secret from the create response. Only the create response carries it. Each handler stops at startup if either variable is missing, and answers 400 to a delivery whose signature doesn’t match.
Example output
Each new page arrives in Slack as one message: the title as a link and the importance from 3 to 5, then the result’s one-linesummary on the second line. With the page from the Monitors example, the first line of the message text is:
Slack message text
200 with the body ok. The handler then answers Keenable with 204.
Production notes
Next steps
- Competitor watch: a scheduled digest from a competitor’s own sites instead of one message per page.
- Verify a webhook: verify without the SDK.
- Webhook events: every event type and its
data. - Recipes: every recipe on one page.