Automate weekly SEO report with GPT-4 insights and Slack delivery
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 38 nodes and runs on a schedule (every week at 08:00). Along the way it connects OpenAI Chat Model, Slack and Pdforge (community).
How it runs
Trigger: On a schedule (every week at 08:00).
- Configuration (Edit Fields (Set)): sets 5 fields: site_url, date_start, date_end…
- HTTP Request: calls an HTTP API (POST)
- HTTP Request: calls an HTTP API (POST)
- HTTP Request: calls an HTTP API (POST)
- HTTP Request: calls an HTTP API (POST)
- HTTP Request: calls an HTTP API (POST)
- HTTP Request: calls an HTTP API (POST)
- HTTP Request: calls an HTTP API (POST)
- HTTP Request: calls an HTTP API (POST)
- HTTP Request: calls an HTTP API (POST)
…plus 26 more steps. 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 n8n-nodes-pdforge is verified or supports 3.0 (used in Pdforge).
Nodes used (10)
- Edit Fields (Set)
n8n-nodes-base.set - Pdforge
n8n-nodes-pdforge.pdforge - HTTP Request
n8n-nodes-base.httpRequest - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Code
n8n-nodes-base.code - Slack
n8n-nodes-base.slack - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Split Out
n8n-nodes-base.splitOut - Merge
n8n-nodes-base.merge - AI Agent
@n8n/n8n-nodes-langchain.agent
From the author
What this workflow does - Runs automatically every Monday morning at 8 AM - Collects your Google Search Console from the last month and the month before that for a given url (date range is configurable) - Formats the data, aggregating it by date, query, page,…