Integrations

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.

Dataset to Airtable — Reliable Field Mapping

Export any Apify dataset into an Airtable table, mapping each field to the correct field type — with a per-item report of what mapped and what was skipped. Batched, rate-limit aware, no silent data loss.

Dataset to Google Sheets — Reliable Export

Append any Apify dataset to a Google Sheet via a service account, with a stable header, column union across ragged rows, and flattened nested values. Honest errors (e.g. share-the-sheet reminder). Pure logic.

Dataset to Notion — Reliable Field Mapping

Export any Apify dataset into a Notion database, mapping each field to the correct Notion property type — with a per-item report of exactly which fields mapped and which were skipped. No silent data loss.

MCP Output Router — Send Any Dataset to Your Own Apps

Write a dataset into Notion, Slack, Supabase, a CRM or anything else you have connected as an Apify MCP connector. Your credentials never touch the Actor: the platform injects them server-side. Dry run by default, and every row reports whether the destination accepted it.

Webhook Inbox — Catch Every Webhook, Lose Nothing

Point any service's webhook at this inbox and every delivery is stored as a dataset row you can read, schedule against, or relay onward. Retries are flagged as duplicates, never dropped, and a body that will not parse is kept rather than thrown away.

Dataset Digest — Merge Datasets Into One Readable Summary

Turn several Apify datasets into one markdown digest a person will actually read: a source table, the merged rows, and an honest count of anything collapsed or dropped. Put it on a schedule and it becomes the weekly summary of a whole pipeline.

MCP Enricher — Look Up Every Row in Your Own Apps

Enrich every row of a dataset by calling a tool on an app you connected as an Apify MCP connector — a CRM, a project tracker, an internal database — and merge the reply back into the row. Your credentials never touch the Actor. Dry run by default.