Turn Zapier Form Submissions into Trello Cards Automatically
An n8n workflow that receives form submissions relayed by Zapier and creates a richly formatted Trello card — title, description, due date and label — on the right list, so intake requests, bug reports or orders become actionable tasks the moment someone hits submit.
- 1
Create the n8n webhook
Add a
Webhooknode (POST) and copy its URL. Submit a test entry so you can see the field names Zapier forwards (name, email, request type, details, deadline). - 2
Build the form Zap
In Zapier: trigger on your form's 'New Submission', action
Webhooks by Zapier → POSTto the n8n URL, mapping every field you want on the card. Turn it on and submissions start flowing. - 3
Compose the card content
A
Setnode builds a clear title ([type] name — short summary) and a markdown description with all the details, plus a computed due date if the form didn't provide one. Good formatting here is what makes the card instantly workable. - 4
Route to the right list
A
Switchnode reads the request type and outputs the matching TrellolistId. Skip this if you only use one list — but it's what turns a dumb intake into an organized triage. - 5
Create the Trello card
A
Trellonode (or HTTP Request to the Trello API) creates the card on the chosen list with the title, description, due date and a label. The requester's task is now visible to the team the second they submit.
Frequently asked questions
Which forms work with this?
Any form Zapier can trigger on — Google Forms, Jotform, Typeform, Gravity Forms, Tally, and dozens more. Zapier normalizes the submission and POSTs it to n8n, so the recipe doesn't care which form tool you use. Swap the form without touching the n8n flow.
Can it route different requests to different lists?
Yes. If your form has a 'type' field (bug / feature / order), a `Switch` node in n8n picks the target Trello list ID per type. One workflow then feeds several boards or lists, keeping each team's queue clean instead of one giant pile.
How do due dates get set?
If your form asks for a deadline, map it straight to the card's due date. If not, the workflow can compute one — for example due in 3 business days — using an n8n date expression. Cards then arrive already scheduled, so nothing silently ages out.