n8n

AI agents and autopilot

Good for: Automations you can host.

Open n8n

Prompts

+3TextsFollow up

Plan an n8n flow that answers new leads

What it does: Writes the n8n workflow step by step: a form comes in, the lead goes into your CRM, you get a ping, and a text draft waits for your OK.

Use it when: New form leads wait hours because nobody sees them.

You get: A node by node plan with each setting, a test list, and what happens when a step fails.

Open in
See the prompt
You are my automation builder, an n8n expert who has built lead flows for small businesses.

Goal: a node by node n8n plan and a test list, so I can build the flow in one sitting.
Context: my business loses leads that wait. They want an answer fast, so the flow must never drop one.

First, check that you can read what I told you about my form, CRM and ping. Tell me which of the 3 you have. If any is missing, use its default, or ask me to paste my form fields instead.

My form tool: [for example: Tally, Typeform, website form. If I don't say, use a Webhook node.]
My CRM: [for example: Close, HubSpot. If I don't say, use a Google Sheets node.]
Where I want the ping: [for example: Slack, email. If I don't say, use email.]

Plan an n8n workflow. For each node give: the node name, what it does, the settings to fill in, and what passes to the next node.
1. Trigger: a new form answer (the form tool's n8n trigger, or a Webhook node).
2. Clean it: trim names, fix the phone format, drop test entries.
3. Look for the same email or phone in the CRM. If found, add a note. If not, create the lead.
4. Ping me with the name, what they asked, and a link to the lead.
5. Draft a text back under 160 characters that thanks them and says when I'll call. Save it as a draft or a task for me. Do not send it.
6. An error path: if any step fails, ping me with the step name and the raw form answer.

Then give me the whole workflow as n8n JSON I can import (in n8n: Workflows, then Import from file), with the same node names and no keys in it.

Then give me a test list: 5 fake form answers to try, and what should happen for each.

Rules:
- Logins go in n8n Credentials only. Never put a key in a node's text field.
- Name every node in plain words.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot, say so, and keep going.

Before you show me, check:
- Check that every node passes something to the next one, and the error path covers every step.
- Make sure no node sends a text: the text back is saved as a draft or a task.
- Make sure the JSON has every node from the plan and no logins.

Last, save these steps as a skill called 'New Lead Flow' so you do it this way each time I plan an automation for new leads.
To run it again, just say: "Run my New Lead Flow skill."

Built on The E-Myth Revisited's systems-dependent business.

You needYour CRMN8nAny AITested on sample data

+3EmailRun the business

Plan an n8n flow that sorts your inbox with AI

What it does: Writes an n8n workflow that reads new emails, has an AI sort them into a few labels, and pings you only for the ones that matter.

Use it when: Your inbox mixes leads, bills and junk, and leads wait.

You get: A node by node plan with settings, the sorting prompt, a test list, and what happens when it's not sure.

Open in
See the prompt
You are my automation builder. I use n8n.

My email: [Gmail or Outlook]
My labels: [for example: LEAD, CUSTOMER, BILL, OTHER]
Where to ping me: [for example: Slack, a text, email]
The AI I'll use in n8n: [for example: OpenAI, Anthropic]

Plan an n8n workflow. For each node: the name, what it does, the settings, and what passes on.
1. Trigger: a new email (the Gmail or Outlook trigger node).
2. Trim it: sender, subject, the first 1,000 characters of the body.
3. Sort: an AI node (Text Classifier or a basic LLM node) with a short prompt that picks one label and says UNSURE when it can't tell. Write that prompt, under 80 words.
4. Label the email in my inbox.
5. If LEAD or UNSURE: ping me with sender, subject and a one line summary (have the sort node write it, or add a small AI node). Pass the trimmed fields along so the ping node has them.
6. Error path: a separate error workflow that starts with the Error Trigger node, set as this workflow's error workflow. It pings me with the node name.

Then 6 test emails to try (label them TEST, made-up senders are fine) and the label each should get.

Rules:
- It never replies, forwards or deletes. Labels and pings only.
- Logins in n8n Credentials only.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Inbox Sorter' so you do it this way each time I plan an inbox automation.

Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 8: Decentralized Command

You needYour emailN8nAny AITested on sample data

Prompts from around the web

1 prompts, each credited to the person who wrote it.

Similar tools

In: AI agents and autopilot

Watch

n8n Explained In 2 Minutes

Video by CodeHead · 2 min

How I'd Learn n8n if I had to Start Over in 2026

Video by Nate Herk · 14 min

Read more: n8n

Don't see your work here?

Tell me what you do every day, and I'll make guides and prompts for it.

Want this built for you? Get it built.