Monitor scraper and endpoint health with Datasource Pulse and Slack alerts
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 4 nodes and runs on a schedule (every 6 hours). Along the way it connects Slack and Apify (community).
How it runs
Trigger: On a schedule (every 6 hours).
- Initiate Datasource Pulse (Apify): run actor and get dataset (actors)
- If: checks a condition and branches into true / false
- Send Slack Alert (Slack): uses Slack
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @apify/n8n-nodes-apify is verified or supports 3.0 (used in Initiate Datasource Pulse).
Nodes used (4)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Apify
@apify/n8n-nodes-apify.apify - If
n8n-nodes-base.if - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow runs every 6 hours to check an Apify scraper’s recent runs and a downstream HTTP endpoint using the Datasource Pulse Apify Actor, and sends a Slack alert for any check that is not healthy. How it works 1. Runs every 6 hours on a…