Dataset Webhook Notifier — Slack, Discord, Generic

Send an Apify dataset to a webhook — auto-formatted for Slack, Discord, or a generic JSON endpoint, respecting each platform's size limits. The last mile of any pipeline, with per-batch delivery reporting.

Built reliability-first: every row reports what was found and what was missing — you never get a silent blank, and a run summary tells you exactly what happened.

What you get

Field	Description
batch	Batch
rows	Rows
target	Target
status	Status
ok	Ok
error	Error

How to use it

1. Fill in the input (see the example below).
2. Run it once for a snapshot, or schedule it to keep the data fresh.
3. Export to CSV/JSON/Excel, or push straight to Google Sheets, Notion, Airtable, Zapier, Make, or n8n.

Input

{
  "webhookUrl": "https://example.com/item/1",
  "target": "auto",
  "mode": "summary",
  "label": "Dataset",
  "maxRows": 20,
  "items": []
}

Sample output

[
{
  "batch": "example",
  "rows": "example",
  "target": "example",
  "status": "ok",
  "ok": true,
  "error": "example"
}
]

Typical uses

• Scrape → Slack alert — "12 new job postings" every morning.
• Monitor → Discord — push change-detection results to a server.
• Pipe to your API — POST rows to your own generic endpoint in batches.

Pricing

$0.02 per delivery, plus a near-zero start fee. You are never charged beyond your limit, and blocked or failed items are reported honestly — not billed as data.

FAQ & limitations

• Public data only — no login walls, no cookies required.
• Rate limits on the source may require the proxy or a retry on very large pulls.
• Every row reports its own status, so partial results are always labeled, never faked.
• Integrations: output works with Zapier, Make, n8n, and any webhook via Apify's integrations.
• Formats: results export as JSON, CSV, Excel, or HTML from the dataset.

Related actors

• Portfolio Health Monitor
• Format Converter
• URL Metadata Extractor

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• Dataset Webhook Notifier — Slack, Discord, Generic declares all 6 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of Dataset Webhook Notifier include batch, rows, target, status, ok and error.
• Dataset Webhook Notifier needs no API key, login or account of any kind before its first run.
• Every one of Dataset Webhook Notifier's 8 inputs is optional, so it runs with no configuration at all.
• Dataset Webhook Notifier documents batch as: Which batch of the run produced this row. Batches are processed in order.
• Every number published about Dataset Webhook Notifier is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• Dataset Webhook Notifier is filed under integrations and automation so that it is found by the people looking for that job, not by its internal name.

Limitations

• Dataset Webhook Notifier reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.