Automate trend research to blog content with GPT-4o, DALL-E & Apify to Notion
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 10 nodes and runs on a schedule (every week at 09:00). Along the way it connects OpenAI, Notion, Slack and Apify (community).
How it runs
Trigger: On a schedule (every week at 09:00).
- Workflow Configuration (Edit Fields (Set)): sets 4 fields: searchKeyword, apifyActorId, notionDatabaseId…
- Run an Actor and get dataset (Apify): run actor and get dataset
- AI Editorial Meeting - Generate 3 Article Ideas (OpenAI): uses OpenAI
- Parse Article Ideas JSON (Code): runs custom JavaScript code
- AI Writer - Generate Article Content (OpenAI): work with conversation
- DALL-E Generate Cover Image (OpenAI): work with image
- Save Article to Notion (Notion): work with database page
- Aggregate: combines items into one
- Send Completion Notification 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 Run an Actor and get dataset).
Nodes used (8)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - OpenAI
@n8n/n8n-nodes-langchain.openAi - Code
n8n-nodes-base.code - Notion
n8n-nodes-base.notion - Aggregate
n8n-nodes-base.aggregate - Slack
n8n-nodes-base.slack - Apify
@apify/n8n-nodes-apify.apify
From the author
AI Editor-in-Chief: Trend Research to 3 Notion Blog Drafts This workflow acts as your personal "AI Editor-in-Chief," fully automating the process from trend research to content creation. It scrapes Google Search results and generates three distinct article…