n8n Workflow Examples: 12 Practical Automations for Agencies

The most useful n8n workflow examples for an agency are the boring ones that run every day: a webhook that turns a new lead into a Slack alert and a CRM record, a schedule that builds a weekly client report, an onboarding flow that creates folders and projects from one form, and an AI agent that answers questions from your own docs. Each n8n workflow starts with a trigger node, such as Webhook, Schedule Trigger or an app trigger, then passes items through nodes that transform data, call APIs and send results. Below are twelve examples with the nodes in order, so you can build them or use them as a spec.

All of these follow the same habits: name every node, filter early, set up an error workflow that posts failures to Slack, and test with realistic data.

Before you start: two n8n habits

An error workflow

Create one workflow that starts with the Error Trigger node and posts the workflow name, node name and error message to a Slack channel. Then set it as the error workflow in each workflow's settings. This one step prevents most silent failures.

Test vs production webhooks

The Webhook node has a test URL that only listens while you are in the editor, and a production URL that works when the workflow is active. Use the production URL in other apps. This catches out almost everyone once.

Lead and sales workflows

1. Form lead to CRM and Slack

1. Webhook node receives the form submission.
2. IF node checks that email or phone exists.
3. CRM node or HTTP Request searches for an existing contact by email.
4. IF node branches on found or not found.
5. CRM node creates or updates the contact and creates a deal.
6. Slack node posts to the sales channel with the lead details and a link to the CRM record.

2. Positive cold email reply alert

1. Webhook node receives reply events from your cold email tool.
2. IF node, or an AI classification step, keeps only positive replies.
3. Slack node pings the sales team with the reply text.
4. Google Sheets node appends the lead to the outreach sheet.
5. ClickUp node creates or updates the lead task.

I run this pattern in production as the positive-reply sales alert, built in Make. The n8n version uses the same steps. See positive reply alerts for cold email.

3. Speed-to-lead SMS

1. Webhook node from the CRM or form.
2. Code node formats the phone number.
3. SMS provider node or HTTP Request sends the first text.
4. CRM update marks the lead as contacted.
5. Wait node, then a check for reply, then a reminder task for a rep if there is none.

Client onboarding workflows

4. New client workspace

1. Webhook node receives the onboarding form.
2. Google Drive node copies a template folder structure.
3. Google Docs node creates the kickoff doc and fills placeholders with client details.
4. Google Sheets node adds the client to the master list.
5. ClickUp node creates the onboarding list from a template.
6. Slack node posts links to the team.

My Make version of this replaced about 40 manual setup steps per new client with one form submission, with the workspace ready in under two minutes. See the client onboarding build.

5. Kickoff not booked reminder

1. Schedule Trigger daily.
2. Google Sheets node reads clients onboarded in the last week.
3. Filter node keeps those with no kickoff date.
4. Gmail node sends a booking reminder.
5. Slack node notifies the account manager.

Reporting workflows

6. Weekly client summary

1. Schedule Trigger weekly.
2. Google Sheets node reads the client list.
3. Loop Over Items node processes clients in batches.
4. HTTP Request nodes pull metrics from your reporting sources.
5. Code node computes changes from last week.
6. Slack node posts each summary to the client's internal channel.

See weekly client report Slack bot for more on this.

7. Search Console drops alert

1. Schedule Trigger daily.
2. HTTP Request node calls the Search Console API for each client property.
3. Code node compares clicks to the previous period.
4. IF node keeps drops above your threshold.
5. Slack node alerts the SEO lead.

See Google Search Console API with n8n and Make.

Operations and monitoring workflows

8. Client health change alert

1. ClickUp Trigger on task updates.
2. IF node checks the health field changed.
3. Google Sheets node looks up account owner and context.
4. Switch node routes by owner.
5. Slack node alerts the right CSM, and a ClickUp node creates a follow-up task.

This mirrors the client health monitor I built in Make.

9. Failed payment alert

1. Webhook node receives a Stripe event, or an email trigger node reads billing emails.
2. Code node extracts invoice, contact and amount.
3. Slack node pings billing.
4. ClickUp node logs a task.

The Make version uses a mailhook and pattern matching, see failed-payment alerts.

10. Website uptime and form check

1. Schedule Trigger every few minutes.
2. HTTP Request node calls each client site or form endpoint.
3. IF node checks for a non-success status.
4. Slack node alerts ops, with a short wait and recheck to avoid false alarms.

AI workflows

11. Internal docs assistant

1. Chat Trigger or Slack trigger receives a question.
2. AI Agent node with a chat model.
3. A vector store tool connected to your SOPs and client docs.
4. Memory so follow-up questions work.
5. Response sent back to Slack.

See my n8n AI agent tutorial for the setup, and n8n AI agent tools for which tools to give it.

12. Client wins formatter

1. Slack trigger listens to a wins channel.
2. Google Docs node pulls client context.
3. AI node rewrites the raw note into a short, formatted win.
4. IF node routes test messages to a test channel.
5. Slack node posts the formatted win.

My production version is the AI Client Wins Slack bot, built in Make with live and test channels and error handling.

n8n workflow ideas: how to pick what to build

If you have a long list of ideas, prioritise by:

1. Frequency. Something that happens daily beats something that happens quarterly.
2. Cost of mistakes. A missed lead or payment hurts more than a late report.
3. Steps replaced. Count manual steps today. Onboarding often has dozens.
4. Simplicity. Start with one trigger and a few actions. Add AI later.

For more, see n8n templates for agencies and the broader list of workflow automation examples for agencies.

How I build this

I build these workflows in n8n or Make, depending on what fits the agency, with error workflows, naming and documentation, and I can set up self-hosted n8n if you need it. See my workflow automation and custom AI agents services, or the fixed-price Agency Reporting and Alerts Pack for the reporting and alert workflows. To find the best first workflow for your agency, request a free 15-minute Loom teardown.

FAQ

What can you automate with n8n?

Almost any process that involves apps with APIs: lead routing, onboarding, reporting, billing alerts, data syncs and AI agents that answer questions or classify messages.

Where can I find n8n workflow templates?

n8n has an official template library on its website and inside the editor. Treat templates as a starting point and adapt the credentials, fields and error handling to your setup.

Is n8n good for beginners?

It is learnable, but it assumes some comfort with data and JSON. Simple webhook-to-Slack workflows are easy, while complex workflows benefit from someone technical.

Can n8n workflows use AI?

Yes. n8n has AI agent and LLM nodes that can call chat models, use tools, keep memory and query vector stores, so you can add AI steps to normal workflows.