Enrich domain snapshots on demand with Apify, Slack, and Google Sheets
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 8 nodes and runs when an HTTP POST request hits its webhook URL (plus 1 other trigger). Along the way it connects Google Sheets, Slack and Apify (community).
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 1 other trigger).
- Read the domain (Code): runs custom JavaScript code
- Sample request for testing (Code): runs custom JavaScript code
- Inspect the domain (Apify): run actor and get dataset (actors)
- Shape the answer (Code): runs custom JavaScript code
- Optional: log every lookup (Google Sheets): append
- Optional: ping Slack on a miss (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 Inspect the domain).
Nodes used (6)
- Manual Trigger
n8n-nodes-base.manualTrigger - Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - Apify
@apify/n8n-nodes-apify.apify - Google Sheets
n8n-nodes-base.googleSheets - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow exposes a POST webhook that normalizes a domain, URL, or email input, runs the Apify Domain Inspector actor, and returns a consistent JSON snapshot of DNS and email routing signals such as MX hosts, mail provider, and…