# How to Route Client Requests: AI Form, Agent or Rules > Route client requests with AI: collect clean details with a form, route by rules with n8n If and Switch, test, publish, and keep an agent for questions. Source: https://learn.ynteractive.com/content/blog/route-client-requests-with-ai-form-agent-or-rules · Updated 2026-10-11 · Free from Stepthrough (https://learn.ynteractive.com) Quick answer To route client requests with AI, collect the details in a clean form, let simple rules decide where each request goes, test the whole path with real data, and publish only when every route has somewhere to land. Use an agent for the questions that need a little judgment and keep a person on anything that commits the office. Three free lessons cover the pieces: [Jotform AI intake form](https://learn.ynteractive.com/content/jotform-ai-client-intake-form) for collecting, [IF and Switch](https://learn.ynteractive.com/content/n8n-if-and-switch-node-tutorial) for routing, and [Execute Step, Execute Workflow and Publish](https://learn.ynteractive.com/content/n8n-execute-step-execute-workflow-publish) for testing and going live. Last updated October 11, 2026 By [Robert Breen](https://learn.ynteractive.com/content/about) · Published October 11, 2026 · Updated October 11, 2026 · 5 min read Intake · n8n · Jotform · Routing This guide puts the three together in the order you would do them. ## Should a rule, an agent or a person decide? Pick the simplest one that works. [AI Agent vs Chatbot vs Automation](https://learn.ynteractive.com/content/ai-agent-vs-chatbot-vs-automation) draws the line with six unpaid invoices. An [automation](https://learn.ynteractive.com/content/glossary/automation) follows fixed rules every time and never uses judgment. An agent gets a goal, decides the steps and can make small judgment calls. A [chatbot](https://learn.ynteractive.com/content/glossary/chatbot) gives an answer and you finish the job. For routing, a rule is usually enough: a budget over a number, a service that is one of three types. Save the agent for the messy middle and give it limits, such as don't send anything. Keep the decision with a person when the request commits the office to a price, a deadline or advice. ## How do you collect clean details first? Use a form that asks for exactly the fields your rules need. In the Jotform lesson, you describe an [intake form](https://learn.ynteractive.com/content/glossary/intake-form) for a made-up accounting firm in one sentence, and Jotform AI builds it. You then read the fields (name, email, phone, company and service type come back required, and whether they should be is your call), ask **Form Copilot** for a better title and one extra field, and write a rule in plain words so the extra field only shows to advisory clients. Check the rules the AI wrote against what you asked for, and remember the lesson's warning: a new Jotform form is public by default, so anyone with the link can submit it. ## How do you route requests with If and Switch? Start with a test request, then add one decision at a time. In the n8n lesson, a service form already has two actions ready: an email to the owner and a new row in the request log. You send a test request first, with a service and a budget of 2500, so you have real data to route. 1. **Add an If.** Drag **Budget** into value 1, choose **Number**, **is greater than**, and type 1000 in value 2. The request goes to **True Branch**, because 2500 is more than 1000. Each item takes one branch or the other, never both. True goes to the owner's email and false goes to the log. 2. **Put a Switch in front.** When emergencies must reach the owner whatever the budget, add a Switch in **Rules** mode: one rule per output, with the outputs renamed **Repair** and **Emergency**. 3. **Keep a fallback.** By default, items that match no rule are dropped. Under **Options**, add **Fallback Output** and choose **Extra Output**, so anything else lands in a separate output. In the lesson, the Installation request matched neither rule and landed in Fallback. 4. **Wire every road.** Repair goes on to the If, Emergency to the owner's email and Fallback to the log. If a number arrives as text, for example from a webhook, switch on **Convert types where required**. The picture version is [n8n If and Switch Nodes: Route Requests by Rules](https://learn.ynteractive.com/content/visual/n8n-if-and-switch-nodes-route-by-rules). ## How do you test before you publish? Run one node at a time, then everything, and check the real result. In [Execute Step, Execute Workflow and Publish](https://learn.ynteractive.com/content/n8n-execute-step-execute-workflow-publish), **Execute step** runs one node with the data from the node before it. If that node has no input, n8n runs the earlier nodes first, and a Webhook just waits for a form. Pin sample data on the Webhook so test runs use it. Then use **Execute workflow**. Every node shows a green check, but a green check means the node ran, not that the output is right, so open the sheet and read the row. In the lesson that check reveals a blank Service column to fix. ## How do you go live without a surprise? Publish, then use the Production URL. Saving does not turn a workflow on. After **Publish**, open the Webhook, choose **Production URL**, and copy the address with /webhook/ in it, not /webhook-test/. Any change you make afterwards needs another Publish, because the live workflow stays the old version until you do. A form that works while you test and then goes quiet is usually still pointing at the test address. The picture is [n8n Webhook: Test URL vs Production URL, Explained](https://learn.ynteractive.com/content/visual/n8n-test-url-vs-production-url-webhook), and the longer read is [n8n Webhook Test vs Production URL](https://learn.ynteractive.com/content/blog/n8n-webhook-test-vs-production-url). ## Where does an agent fit in? On the questions that come in all day. [Jotform AI Agents](https://learn.ynteractive.com/content/jotform-ai-agent-client-questions) teaches a chat agent one stable answer, such as what to bring to a first consultation and when the office is open, and tests it with the question in different words. The rule from that lesson applies to routing too: teach it only what is true, test it with questions you did not teach it, and let it hand everything else to a person. ## Key takeaways - Pick the simplest decider: a rule for fixed conditions, an agent for judgment calls, a person for commitments. - Collect the fields your rules need, and check any rule the AI wrote against your request. - Use If for a yes or no and Switch for more than two roads, and always set a fallback so nothing is dropped. - Test with real data and check the sheet, since green checks only mean the nodes ran. - Publish, then use the Production URL, and publish again after every change. ## Frequently asked questions **When do I need a Switch instead of an If?** Use an If for one yes or no question. Use a Switch when there are more than two roads, such as repair, emergency and everything else. **What happens to a request that matches no rule?** By default it is dropped. Set Fallback Output to Extra Output so it lands in its own output and you can send it somewhere. **Why did my form stop working after I tested it?** It is probably still pointing at the Test URL, which only listens while you test in the editor. Publish the workflow and use the Production URL. **Where do I start?** Begin with [IF and Switch](https://learn.ynteractive.com/modules/n8n-if-switch), then take [Execute Step, Execute Workflow and Publish](https://learn.ynteractive.com/modules/n8n-execute-publish). ## Build it yourself, free **IF and Switch in n8n: Route Work by Rules**. Send each request where it belongs. Use an If node to split big jobs from small ones, then a Switch with named outputs and a fallback to route by service. You do every step yourself in a practice copy of n8n, it checks your work as you go, and “Do it for me” finishes any step you get stuck on. Free, and nothing touches your real accounts. [Start the free lesson](https://learn.ynteractive.com/modules/n8n-if-switch) [Or read the full step-by-step guide](https://learn.ynteractive.com/content/n8n-if-and-switch-node-tutorial) ## Free lessons in this post - [IF and Switch in n8n: Route Work by Rules](https://learn.ynteractive.com/content/n8n-if-and-switch-node-tutorial): Send each request where it belongs. Use an If node to split big jobs from small ones, then a Switch with named outputs and a fallback to route by service. - [Jotform AI: Build a Client Intake Form from One Prompt](https://learn.ynteractive.com/content/jotform-ai-client-intake-form): Describe a client intake form to Jotform AI, fix it with Form Copilot, add a show/hide rule in plain words, and copy the link to send to new clients. - [n8n: Execute Step, Execute Workflow and Publish](https://learn.ynteractive.com/content/n8n-execute-step-execute-workflow-publish): Learn the buttons in today's n8n editor: run one node with Execute step, pin test data, run everything with Execute workflow, then Publish and copy the Production URL. ## Watch it in a free lesson: Gmail AI Triage: Auto-Label Every Email and Draft Replies ### Gmail AI Triage: Auto-Label Every Email and Draft Replies: video walkthrough Full walkthrough · 2:31 · with captions Build an n8n workflow that reads each new email, sorts it as a lead, a client or an invoice with a Text Classifier, adds the matching Gmail label, and drafts a reply to clients for you to check. The whole lesson narrated step by step, recorded in Stepthrough’s simulated practice environment. [Watch it with chapters and the full transcript](https://learn.ynteractive.com/content/gmail-ai-triage-labels-drafts-n8n#watch) From the free lesson [Gmail AI Triage: Auto-Label Every Email and Draft Replies](https://learn.ynteractive.com/content/gmail-ai-triage-labels-drafts-n8n) ## Related terms Plain-English definitions, each with an example from a free lesson. [Automation](https://learn.ynteractive.com/content/glossary/automation) · [Chatbot](https://learn.ynteractive.com/content/glossary/chatbot) · [Intake form](https://learn.ynteractive.com/content/glossary/intake-form) · [AI form builder](https://learn.ynteractive.com/content/glossary/ai-form-builder) · [Conditional logic](https://learn.ynteractive.com/content/glossary/conditional-logic) · [Execute step](https://learn.ynteractive.com/content/glossary/execute-step) · [Execute workflow](https://learn.ynteractive.com/content/glossary/execute-workflow) · [Execution (n8n)](https://learn.ynteractive.com/content/glossary/n8n-execution) [The full AI glossary](https://learn.ynteractive.com/content/glossary) ## Related prompts - [Form show/hide rule prompt](https://learn.ynteractive.com/content/prompts/form-conditional-rule-prompt): Turn a form rule into one plain sentence an AI form builder can read: which field should appear, for which answer, and hidden… - [Intake form description prompt](https://learn.ynteractive.com/content/prompts/intake-form-description-prompt): Describe a new-client intake form so an AI form builder gets it right first time: who fills it in, what to collect, what is… - [Request routing rules prompt](https://learn.ynteractive.com/content/prompts/routing-rules-plain-words-prompt): Write down who should get which request before you build it in n8n: the condition for each route, the exit names and a fallback… [All free prompt templates](https://learn.ynteractive.com/content/prompts) ## Visual guides The same ideas as quick visual guides: swipe through the slides, or read each one as text. - [Jotform AI Intake Form: 5 Steps to Build and Share One](https://learn.ynteractive.com/content/visual/jotform-ai-client-intake-form-in-5-steps): A visual guide to building a client intake form with Jotform AI: describe it, read the fields, fix it with Form Copilot, add a rule and share the link. - [n8n Execute Step vs Execute Workflow vs Publish](https://learn.ynteractive.com/content/visual/n8n-execute-step-execute-workflow-publish-explained): A visual guide to the three n8n buttons: run one node with Execute step, pin test data, run everything with Execute workflow, then Publish for real. - [n8n If and Switch Nodes: Route Requests by Rules](https://learn.ynteractive.com/content/visual/n8n-if-and-switch-nodes-route-by-rules): A visual guide to n8n If and Switch nodes: split big jobs from small ones with one condition, then route by service with named outputs and a fallback. [All visual guides](https://learn.ynteractive.com/content/visual) ## Keep reading - [How to Pick the Right AI Tool for Office Work](https://learn.ynteractive.com/content/blog/pick-the-right-ai-tool-for-office-work): Pick an AI tool by the job: an assistant for drafts, Jotform for intake, Gamma for decks, Flova or DomoAI for video, n8n for rules. With a lesson for each. - [Sales Follow-Up by Deal Stage: Messages That Fit](https://learn.ynteractive.com/content/blog/sales-follow-up-by-deal-stage): Sales follow up by deal stage: one short message per open deal, matched to where it stands, with one ask. A ChatGPT prompt, then an n8n agent. - [What Can You Automate With n8n? 8 Office Examples](https://learn.ynteractive.com/content/blog/what-can-you-automate-with-n8n): What can you automate with n8n? Eight office examples, from Gmail reply drafts to invoice approvals, each with a free practice lesson. [All blog posts](https://learn.ynteractive.com/content/blog) · [All free tutorials](https://learn.ynteractive.com/content)