Overview
A good form asks fewer questions and routes faster. With Taskade Genesis you describe the form in plain English, the AI builds it with the right field types, branching rules show the next question based on the last answer, and a Forms-trigger automation routes every submission to the right place.
TL;DR: Prompt Taskade Genesis for the form you want. Taskade Genesis ships the UI with conditional branches that hide and show questions based on prior answers. Attach a Forms-trigger automation to classify, branch, and save each submission as a row in a Project. Works on every plan, Free included.
Why conditional logic matters
A flat form asks every question to every respondent. A branched form asks only the questions that follow from the last answer. Same data quality, fewer drop-offs. Taskade Genesis makes the branching part visual, and the routing part automated.
The whole thing fits together as one loop: the form collects, the automation classifies, the Project stores, and an agent can read the Project to act on what landed.
Prompt Taskade Genesis for the form
Open Taskade Genesis and describe the form. Be specific about the questions, the branches, and what should happen on submit.
A useful prompt looks like: "Build an onboarding form for a B2B SaaS. Ask company size first. If 1 to 10 people, ask about pricing concerns. If 11 to 200, ask about team setup. If 200+, route to sales. Always collect name, email, and company." Taskade Genesis renders the form with the size question first and the follow-ups gated behind it.
Refine fields and branches
After the first render, click any question to tune it. Change field types, reorder, or rewrite the labels. The Logic panel on the right shows which questions appear under which conditions. Each rule reads if answer X equals Y, show question Z.
- Short Text for names and short answers.
- Long Text for open-ended replies.
- Option Dropdown or Single-Select when branching depends on the choice.
- Number for sizes and quantities used in numeric branches.
- Email with built-in validation for the contact step.
- File when the form collects screenshots or documents.
Keep the branching rules wide at the top, tight at the bottom. Start with one or two segment-defining questions, then narrow into specifics.
Attach the routing automation
Every Taskade Genesis form is also an automation trigger. Open the Automations tab and find the matching flow, or create a new one and pick Form as the trigger.
- Click Add Trigger and choose Form. Pick the form you just built.
- Click +, add an Ask AI step with a prompt like Classify this submission as SMB, Mid-market, or Enterprise and return the label as JSON.
- Add a Branch step that reads the AI label.
- Under each branch, add a Create Task or Add Row to Project action so the submission lands in the right place.
- Optional: add a Slack Send Message or Gmail Send Email action so the right teammate hears about it instantly.
Save and toggle the automation On. Submissions now flow through classification and routing without anyone watching.
Use case: support intake that ends at the right queue
A support team wants a single intake form that splits into three queues. Build a Taskade Genesis form with a first question: "Is this a billing, bug, or feature request?" Each answer reveals a different follow-up, like account email for billing, repro steps for bugs, use case for features.
Wire the Forms-trigger automation to branch on the answer. Billing rows land in a Billing Queue Project, bugs in Engineering Triage, features in Roadmap Inbox. Each branch can also message the right Slack channel so the on-call teammate sees the ticket within seconds.
Save records to a Project
The Project is where every submission becomes a row you can sort, filter, and act on. Pick a Project per branch, or one Project with a Segment column the automation writes to.
| Project pattern | When to use it | What the automation writes |
|---|---|---|
| One Project per branch | Different owners per segment | Full submission as one row in the matching Project |
| One Project, Segment column | Same team owns all queues | Submission plus the AI-assigned segment label |
| Project plus child task | Long-form processing needed | Parent row per lead, child tasks per follow-up step |
| Project plus agent memory | Agent will reply later | Submission appended to agent knowledge via Add Knowledge |
Publish, embed, and iterate
Click Publish on the form. Pick a sharing mode that matches the audience.
- Public link for open intake.
- Password-protected for partner or client forms.
- Embed in any website with the provided snippet.
- Custom domain when the form lives on your own URL.
Open the History tab on the automation to see every submission and its routing decision. Failed runs are flagged with a badge, so a misrouted submission shows up before the requester complains.
After a week of submissions, scan the Project. If one branch is collecting noise, tighten the question above it. If the AI step misclassifies, rewrite its prompt or switch to a custom AI agent for richer judgment. The form, the automation, and the storage live in one place, so every change ships in seconds.
Related guides
- AI Forms. Full field catalog and trigger settings.
- Taskade Genesis Overview. Mental model for prompt-to-app building.
- Automations: The Execution Pillar. Trigger, action, and control-flow primer.
- Branch Action. Route on any variable in the flow.
- Categorize with AI. Preset-based classification for routing.
- Build an AI Dashboard with Taskade Genesis. Companion build for analytics surfaces.