Integrations / Sending data out
Webhooks
The app POSTs its own events to a URL you own: a monitor found new rows, a monitor errored, a run finished. Slack and Discord incoming webhooks are formatted into a readable message for you; anything else — Zapier, Make, your own backend — gets the raw JSON event to do as it likes with.
Where it goesSetting it up
Settings → Notifications takes one URL, an optional second, and has a Send test button. Any single monitor or run can also carry its own URL, which routes that one to its own channel instead of the global firehose.
CostWho bills you
Nothing. A notification is not an action, and the POST leaves from your machine rather than through anything of ours.
Worth knowing
"A scrape or enrichment run completes" is off by default — a busy table would bury the channel. New rows from a monitor, and monitor errors, are on.