We've built hundreds of n8n workflows for B2B revenue teams. Most are variations on the same ten patterns, because the same revenue leaks show up everywhere: slow lead response, dirty data, forgotten follow-ups, and reporting that eats a Friday afternoon.

Here are the ten, in the order we usually build them. Each one is production-tested and typically live within days, not months.

1. Inbound speed-to-lead

Trigger: form submission, chat conversation, or demo request.
Flow: enrich the contact → score against your ICP → route to the right rep → post an alert in Slack with full context → draft a personalised first reply for one-click send.
Why it matters: leads contacted in the first five minutes convert at multiples of those contacted hours later. This workflow makes five minutes the worst case, nights and weekends included.

2. The enrichment waterfall

Trigger: new contact or company record.
Flow: try provider A → if a field is missing, try provider B → then C → validate the email → write everything back with source tags.
Why it matters: no single data provider covers everything. Chaining them by cost means you pay premium rates only for the records cheap sources couldn't fill.

3. AI-drafted follow-ups

Trigger: positive reply to a cold email campaign.
Flow: AI reads the full thread plus CRM notes → drafts a response in your voice with relevant context → rep approves, edits, or rejects in Slack.
Why it matters: reply speed wins deals, but canned replies kill them. Human-approved AI drafts give you both: minutes-fast and actually personal.

4. CRM hygiene bot

Trigger: nightly schedule.
Flow: find duplicates → merge by rule → normalise job titles, countries, and phone formats → flag records missing critical fields → file a summary report.
Why it matters: data quality decays at a few percent per month, silently. A janitor that never sleeps is the difference between a CRM and a junk drawer.

5. Intent-signal watcher

Trigger: daily checks across signal sources.
Flow: monitor target accounts for funding rounds, leadership changes, job postings, and pricing-page visits → when a signal fires, promote the account tier and trigger the matching ABM play.
Why it matters: timing beats persuasion. The same message lands completely differently the week an account starts feeling the problem.

6. Meeting no-show recovery

Trigger: calendar event ends with no rep-marked outcome.
Flow: check attendance → if no-show, send a graceful reschedule note with booking link → nudge again in 48 hours → flag for manual outreach after two misses.
Why it matters: 10 to 20% of booked meetings no-show. Most are recoverable if someone follows up fast, which nobody does manually.

7. Churn-risk early warning

Trigger: weekly health-score recalculation.
Flow: pull product usage, support tickets, invoice status, and champion job changes → recompute account health → alert the CS owner with a save-play checklist when an account turns yellow.
Why it matters: churn is rarely a surprise to the data, only to the team. This closes that gap a quarter early.

8. Content-to-pipeline tracker

Trigger: weekly schedule.
Flow: join CRM deals against first-touch and assisted-touch content (blog posts, webinars, lead magnets) → compute influenced pipeline per asset → publish a ranked digest.
Why it matters: it ends the "does content even work?" debate with numbers, and tells your SEO program exactly what to write more of.

9. Quote-to-cash chaser

Trigger: deal moves to closed-won.
Flow: generate the invoice → notify finance → schedule polite payment reminders at 7/14/30 days overdue → escalate to a human at 45.
Why it matters: revenue isn't revenue until it's collected, and founders are the world's most expensive accounts-receivable clerks.

10. The Monday revenue digest

Trigger: Monday, 8:00 AM.
Flow: pull pipeline created, meetings booked, campaign performance, and deliverability stats from every tool → compile one scoreboard with week-over-week deltas and anomalies highlighted → deliver to Slack and email.
Why it matters: every team "means to" review the numbers weekly. The ones that actually do are the ones where the numbers show up by themselves.

Pattern worth noticing: none of these replace people. They remove the typing, watching, and remembering, so the humans only handle the judgement calls.

Build order, if you're starting from zero

  1. Week 1: Speed-to-lead (#1). Fastest revenue impact, easiest win to sell internally.
  2. Week 2: Hygiene bot (#4) and enrichment waterfall (#2), because everything else depends on clean data.
  3. Weeks 3 to 4: The digest (#10), then whichever of the rest matches your biggest leak.
A note on error handling: the difference between a demo workflow and a production workflow is what happens when an API times out at 3 AM. Every workflow above ships with retries, failure alerts, and a dead-letter path. If you build these yourself, build that part first.
OM
The Omnitics Team We design, build, and maintain n8n automation for revenue teams. Bring us your three most annoying processes.