![]()
![]()
+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.
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.