Capture social DMs with purchase intent using FanBase, Apify 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 AI workflow has 12 nodes and runs on a schedule (every 15 minutes). Along the way it connects MCP Client, Google Sheets and Apify (community).
How it runs
Trigger: On a schedule (every 15 minutes).
- Retrieve Watermark Data (Data table): get
- Fetch Direct Messages (MCP Client): uses MCP Client
- Identify Intent in DMs (Code): runs custom JavaScript code
- Store Watermark Data (Data table): create or update
- Process CRM Page (MCP Client): uses MCP Client
- Process CRM Page (MCP Client): uses MCP Client
- Merge: merges the data from its input branches
- Resolve Social Handles (Code): runs custom JavaScript code
- Execute Actor for Lead Data (Apify): run actor and get dataset
- Assemble CRM Data Row (Code): runs custom JavaScript code
…plus 1 more step. See the full node list below.
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 Execute Actor for Lead Data).
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Data table
n8n-nodes-base.dataTable - MCP Client
@n8n/n8n-nodes-langchain.mcpClient - Code
n8n-nodes-base.code - Merge
n8n-nodes-base.merge - Google Sheets
n8n-nodes-base.googleSheets - Apify
@apify/n8n-nodes-apify.apify
From the author
Quick overview This workflow runs every 15 minutes to scan your socials with FanBase Copilot DMs for purchase-intent messages, enriches matched fans by resolving their social handle via FanBase CRM and scraping their Instagram profile with Apify, then writes…