10 marketing workflows in n8n you can implement this week

Nothing teaches you more about automation than seeing real workflows in action. This guide presents ten marketing workflows in n8n that are running in real companies, with the logic behind each one explained so you can replicate or adapt them.

For each workflow: what it solves, how it is built and what result it produces.

Workflow 1: Notification to the sales rep when a lead visits the pricing page

The problem: the sales team doesn’t know when a lead is actively considering a purchase.

The solution: Google Analytics 4 has a configurable trigger for when a user visits a specific page. With the GA4 → n8n → Slack integration, when a lead from the CRM (identified by email via UTM parameter or identification cookie) visits the pricing page, the assigned sales rep receives a Slack notification with the lead’s name, their CRM history, and a link to call them immediately.

Nodes in n8n: Webhook (GA4 trigger) → HTTP Request (CRM query by email) → IF (is lead active?) → Slack (notification with context).

Result: the sales team converts 35% more opportunities because they intervene at the moment of greatest interest.

Workflow 2: Automatic enrichment of web form leads

The problem: leads arrive from the form with only a name, email and company. The sales rep needs more context before calling.

The solution: when a form arrives, n8n automatically queries: LinkedIn (the person’s profile via Apollo or LinkedIn API), the company domain (size, sector, technologies in use with Clearbit or Hunter), and the previous history in the CRM. With that information, it creates the enriched contact in the CRM and notifies the sales rep with the full briefing.

Nodes in n8n: Webhook (form submit) → HTTP Request (Apollo/Clearbit) → HTTP Request (CRM) → HTTP Request (create/update CRM contact) → Email (briefing to sales rep).

Result: the preparation time for each discovery call drops from 20 minutes to 2 minutes.

Workflow 3: Automated weekly marketing report

The problem: preparing the marketing metrics report takes 3 hours every week.

The solution: every Monday at 7:30,n8n collects data from GA4 (traffic, conversions), Google Ads (spend, conversions, CPA), Meta Ads (reach, conversions, ROAS) and CRM (new leads, opportunities created). The data goes to a Claude prompt that generates the narrative executive summary. The report is sent by email to the management team.

Nodes: Schedule Trigger (Monday 7:30) → HTTP Request ×4 (each platform’s APIs) → HTTP Request (Claude API) → Email (report delivery).

Result: 3 hours of manual work eliminated. The marketing team starts Monday with the report already done.

Workflow 4: Automatic reactivation of cold leads

The problem: there are leads in the CRM that have had no activity for more than 90 days and nobody is working them.

The solution: every week, n8n queries the CRM to get leads with last activity > 90 días. For each lead, Claude generates a personalised email mentioning the context of the last interaction. The email is sent from the assigned sales rep’s SMTP account. If there is a reply (IMAP polling), a task is created in the CRM for the sales rep.

Nodes: Schedule Trigger (every Monday) → HTTP Request (CRM query) → Loop: HTTP Request (Claude API) → Email (custom SMTP) → Wait → IMAP (response polling) → HTTP Request (create CRM task).

Workflow 5: Automatic post on LinkedIn from a blog article

The problem: the team publishes articles on the blog but forgets to share them on LinkedIn.

The solution: n8n monitors the blog RSS. When a new article appears, Claude generates the copy for the LinkedIn post (not the same text as the article: a different angle that encourages readers to read the full article). The post is published automatically at 9:00 the following day with the link to the article.

Nodes: RSS Feed Trigger → HTTP Request (Claude API) → Wait (until 9:00 the following day) → HTTP Request (LinkedIn API).

Workflow 6: Automatic response to email enquiries

The problem: 60% of emails arriving at info@ are questions that anyone with access to the website could answer.

The solution: IMAP polling every 30 minutes. For each new email, Claude classifies the intent (price enquiry, service information, complaint, meeting request, spam). If it is an information enquiry, it generates the response with the correct information from the knowledge base and sends it. If it is a meeting request, it adds the Calendly link. If it is a complaint or something that requires judgement, it forwards it to the team with the analysis and suggested response.

Workflow 7: Brand mention alerts on the internet

The problem: the team doesn’t find out when someone mentions the company online.

The solution: Google Alerts has no API, but n8n can scrape search results from site:google.com/alerts using Playwright. Each day, the agent searches for brand mentions on Google News, Twitter/X and Reddit. New mentions are classified by sentiment with Claude and sent to the team: positive ones to one Slack channel, negative ones to another with high priority.

Workflow 8: Generating commercial proposals

The problem: preparing a commercial proposal takes between 2 and 4 hours.

The solution: the sales rep fills in a form in Notion with the client’s details (sector, size, identified needs, approximate budget). n8n collects that information, queries the service catalogue and case studies from the same sector in Notion, and Claude generates the complete proposal document in Google Doc format. The sales rep receives the link to the document to review and send.

Result: preparation time drops from 3 hours to 20 minutes.

Workflow 9: Competitor monitoring

The problem: the team doesn’t know when competitors make relevant changes to their website or their campaigns.

The solution: Playwright takes a weekly screenshot of the main pages of the configured competitors. n8n compares the current HTML with the previous week’s to detect changes. Claude analyses the changes and evaluates their relevance. Relevant changes (new services, price changes, newly detected campaigns) are flagged to the senior team.

To see a more complete version of this workflow, see our Competitive Analysis product.

Workflow 10: Automated post-meeting follow-up

The problem: after sales meetings, follow-ups are delayed or forgotten.

The solution: when the sales rep updates the CRM after a meeting (status "Meeting completed"), n8n extracts the meeting notes, Claude generates the personalised follow-up email with the agreed points and next steps, and sends it as a draft to the sales rep’s email account for them to review and send with one click. If the sales rep has not acted within 24 hours, they receive a reminder.