Monitor weekly AI crawler access to your sites with Apify and Slack
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 6 nodes and runs on a schedule (every week at 08:00). Along the way it connects Slack and Apify (community).
How it runs
Trigger: On a schedule (every week at 08:00).
- Websites to watch (Edit Fields (Set)): sets 2 fields: websites, monitorName
- Check AI crawler access (Apify): run actor and get dataset (actors)
- New or changed? (If): checks a condition and branches into true / false
- Build Slack message (Code): runs custom JavaScript code
- Send to Slack (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 Check AI crawler access).
Nodes used (6)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Apify
@apify/n8n-nodes-apify.apify - If
n8n-nodes-base.if - Code
n8n-nodes-base.code - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow runs every Monday to check whether AI crawlers can access a list of websites using the Apify AI Crawler Access Checker actor, and posts a single Slack alert only when access rules or signals change. How it works 1. Runs every…