A marketing manager spends an average of 16 hours per week on repetitive tasks: copying data between tools, compiling reports, following up with prospects, scheduling social posts. n8n can reduce that time to a few minutes through automated workflows.
Here are seven concrete workflows, tested in real conditions, that you can replicate in your n8n instance. For each scenario: the trigger, the nodes required and the measurable outcome.
Workflow 1: Automated GA4 Reporting Every Monday
Compiling a weekly report from Google Analytics 4 takes 30 to 45 minutes manually. This workflow eliminates that recurring task.
Workflow architecture:
- Trigger: Cron (every Monday at 8:00 a.m.)
- Node 1: Google Analytics 4 > Retrieve sessions, conversions, traffic sources, page views (last 7 days)
- Node 2: Code (JavaScript) > Calculate week-over-week variations, format percentages
- Node 3: Google Sheets > Archive raw data in a historical spreadsheet
- Node 4: Slack > Send a formatted summary to the #marketing channel
Outcome: report delivered every Monday at 8:02 a.m. with zero human intervention. History accumulates in Google Sheets for trend analysis. This workflow connects directly to the data configured in your GA4 instance.
Workflow 2: Real-Time Google Ads Budget Alerts
A campaign that goes off track can burn hundreds of euros in a few hours. This workflow monitors your spend and alerts you immediately when anomalies appear.
Workflow architecture:
- Trigger: Cron (every 2 hours, 6 a.m. to 10 p.m.)
- Node 1: Google Ads API > Retrieve daily cost per campaign
- Node 2: Code > Compare current cost to daily budget, calculate spend ratio
- Node 3: IF > If ratio exceeds 80% of budget before 2 p.m. (abnormal pace)
- Node 4: Slack + Email > Dual notification with campaign name, amount spent and remaining budget
Outcome: budget overruns detected within 2 hours instead of being discovered the following morning. For teams managing active Google Ads campaigns, this safety net is indispensable.
Workflow 3: Email Nurturing After Lead Magnet Download
A prospect downloads a guide, an ebook or a checklist. Without structured follow-up, 70% of these leads go cold within 48 hours (source: InsideSales, 2023). This workflow activates an automatic sequence.
Workflow architecture:
- Trigger: Webhook (download form on WordPress)
- Node 1: Wait 24 hours (Wait node)
- Node 2: Email (Mailgun/SMTP) > Send email 1: "Have you had time to review [resource]?"
- Node 3: Wait 72 hours
- Node 4: HTTP Request > Check whether the lead opened email 1 (via Mailgun API)
- Node 5: IF > If opened: send email 2 (relevant case study). If not opened: send a variant with a different subject line.
- Node 6: Wait 5 days
- Node 7: Email 3 > Meeting proposal with a Calendly link
Outcome: a three-email sequence over 9 days, fully automated. The sales rep only steps in if the prospect books a meeting. Observed response rate: 12 to 18% on email 3 (vs 3-5% without nurturing).
Workflow 4: Multi-Channel Distribution From a Blog Post
Publishing a blog article is 20% of the work. Distributing that content across LinkedIn, X, Facebook and by newsletter accounts for the remaining 80%. This workflow automates distribution.
Workflow architecture:
- Trigger: RSS Feed > Detect a new article published on your WordPress blog
- Node 1: HTTP Request > Retrieve the full article content
- Node 2: OpenAI/Claude API > Generate 3 adapted summaries: LinkedIn (professional format, 200 words), X (short format, 280 characters), Facebook (conversational format)
- Node 3: LinkedIn API > Publish the LinkedIn post
- Node 4: X API > Publish the tweet
- Node 5: Facebook API > Publish the Facebook post
- Node 6: Notion > Archive the article and publications in an editorial tracking database
Outcome: one published article automatically generates 3 social posts in under 2 minutes. Tone adaptation for each platform is handled by AI. The editorial calendar updates without manual intervention.
Workflow 5: Inbound Lead Qualification and Routing
A contact form generates leads of varying quality. This workflow sorts, enriches and routes each enquiry to the right person.
Workflow architecture:
- Trigger: Webhook (Contact Form 7 or Gravity Forms)
- Node 1: HTTP Request (data enrichment API) > Enrich with industry sector, company size and revenue
- Node 2: Code > Calculate a qualification score (0-100) based on declared budget, sector and size
- Node 3: Switch > Route by score:
- Score above 70: priority prospect > Slack #hot-leads + CRM set to "Urgent"
- Score 40-70: standard prospect > CRM set to "To process" + confirmation email
- Score below 40: cold prospect > Automated email with helpful resources (guides, FAQ)
- Node 4: HubSpot/Pipedrive > Create or update the contact with enriched data
Outcome: the sales team receives only qualified leads with full context. Lead processing time drops from 15 minutes (manual) to 8 seconds (automated). A detailed use case is available in our article on AI-powered lead qualification.
Workflow 6: Bidirectional CRM Synchronisation
CRM data and website data often live in silos. This workflow maintains consistency between your WordPress site, CRM and marketing tools.
Workflow architecture:
- Trigger: Webhook (contact update in HubSpot) + Cron (full daily sync at 2 a.m.)
- Node 1: HubSpot > Retrieve the modified contact (or the complete list for the daily sync)
- Node 2: Code > Map HubSpot fields to your internal data schema
- Node 3: MySQL/PostgreSQL > Update your local database
- Node 4: Mailchimp > Synchronise segments and tags
- Node 5: IF > If status changes to "Client," trigger a separate onboarding workflow
Outcome: a single source of truth. Mailchimp segments reflect CRM data in real time. No more duplicates, no more existing clients receiving prospecting emails.
Workflow 7: Automated Competitive Intelligence
Monitoring competitor activity (new content, pricing changes, new pages) takes time. This workflow automates collection and synthesis.
Workflow architecture:
- Trigger: Cron (daily at 7 a.m.)
- Node 1: RSS Feed (x3-5) > Retrieve latest articles from competitor blogs
- Node 2: HTTP Request > Scrape competitor pricing pages (via scraping API)
- Node 3: Claude/OpenAI API > Summarise detected changes in 5 lines or fewer
- Node 4: Google Sheets > Log each change with date and source
- Node 5: Slack > Send a morning digest to the #intelligence channel
Outcome: every morning, a summary of competitive activity awaits the team. No risk of missing a strategic move. Data accumulates in Google Sheets for spotting trends over several months.
How to Get Started With These Workflows
The temptation is to automate everything at once. Resist. Start with the workflow that eliminates your most time-consuming task. For most SMEs, that means reporting (workflow 1) or lead qualification (workflow 5).
A logical progression in three phases:
- Weeks 1-2: Install n8n (cloud or self-hosted), create your first workflow (reporting or alerts)
- Weeks 3-4: Add the nurturing or qualification workflow, test for 2 weeks
- Months 2-3: Deploy remaining workflows, connect your CRM, train the team
Each workflow described here takes between 2 and 6 hours to set up. For a guided implementation, our consultants in AI and automation support SMEs from design through deployment, with team training included.
Frequently Asked Questions
Do I need technical skills to create these workflows?
Workflows 1, 2 and 4 are accessible to a marketing professional after 2-3 days of n8n training. Workflows 3, 5 and 6 require familiarity with data manipulation (JSON, expressions). Workflow 7 calls for basic scraping knowledge.
How much does the OpenAI or Claude API cost in these workflows?
AI calls in these workflows (summaries, qualification, content adaptation) cost between 0.01 and 0.05 EUR per execution. For 100 articles distributed per month, the AI cost is under 5 EUR. The cost-to-time ratio is highly favourable.
Do these workflows also work with Make or Zapier?
The logic is transferable. n8n nodes have equivalents in Make (modules) and Zapier (actions). The difference: n8n offers more flexibility on custom code and execution volumes. Consult our n8n vs Make vs Zapier comparison to decide.
What server specs are needed to run all 7 workflows?
A VPS with 2 GB of RAM and 1 vCPU (around 5-10 EUR/month from Hetzner or OVH) handles 20-30 active workflows with hourly executions. For real-time webhooks and high volumes, move up to 4 GB of RAM.
