Turn website enquiries into cards on your sales board
Each contact form submission opens a labelled card on your 'New leads' list, ready for a rep to pick up.
New submission on your "Contact us" form
Create a card on the "New leads" list with the prospect's name as the card title, their message in the description, and a green "Inbound" label
One-directional. A submission triggers the action — nothing is written back into your form.
A sales board only works if the leads actually reach it. This flow takes every submission on your contact form and opens a card on the "New leads" list, titled with the person's name, so a rep can scan the column and pick up the next one without opening a shared inbox.
Small teams reach for this when a full CRM is heavier than the pipeline needs. Cards get dragged from "New leads" to "Contacted" and "Won", and the enquiry that started it sits in the card description where anyone on the board can read it.
Setting it up
- 1
Publish your contact form and send one genuine enquiry through it, so Zapier has a sample with the Subject and Message fields filled in.
- 2
In Zapier, point the formformform "New Submission" trigger at that published contact form — not a draft copy of it.
- 3
Add Trello's "Create Card" action, choose your pipeline board, then set the list to "New leads" rather than leaving the board's first list selected.
- 4
Map Full Name into the card's Name field, and append Subject after it so two enquiries from the same person stay distinguishable.
- 5
Build the Description from Message, with Email Address and Phone Number on the lines above it so a rep can reply straight from the card.
- 6
Create a green label called "Inbound" on the board before you finish the Zap — Zapier only offers labels that already exist on that board.
- 7
Set the card position to "top" so the newest enquiry sits at the head of the list instead of below yesterday's.
- 8
Run the test, read the card in Trello, then switch the Zap on. Dragging that card to "Contacted" changes nothing back in the form — the flow runs one way only.
What maps where
Using the Contact Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Trello |
|---|---|
| Full Name | Card name on the "New leads" list |
| Subject | Appended to the card name to keep similar enquiries apart |
| Message | Card description |
| Email Address | First line of the card description, above the message |
| Phone Number | Card description, next to the email address |
Variations worth knowing
Add Zapier Paths after the trigger and branch on Subject. Sales questions land on "New leads", support questions on a different board entirely. Each path gets its own Create Card step, so the list and the label are chosen per branch rather than sorted by hand afterwards.
Insert a Formatter step that adds two working days to the submission date, then map the result into the card's Due Date. Trello turns the date amber as it approaches, which gives the board an obvious pile of leads nobody has replied to yet.
If something isn't arriving
Labels have to exist on the destination board before Zapier can select them, and they are per-board, not global. Create the green "Inbound" label on the pipeline board, then reopen the action step and pick it again from the refreshed list.
The mapped question was renamed or removed in the form editor after the Zap was built. Open the Create Card step, remap Full Name from a fresh sample submission, and retest before turning the Zap back on.
Frequently asked questions
Can I send enquiries to different boards depending on who they are for?
Yes. Zapier Paths let one form feed several boards — branch on the Subject field and give each path its own Create Card step. The form stays single, which matters because a split form usually means split reporting later on.
If a rep moves the card to "Won", does the submission update?
No. The connection is one-directional: a submission creates a card, and nothing is written back. Card moves, comments and archiving stay inside Trello. The original submission stays exactly as it was sent, in your formformform responses.
What happens to a lead if Trello is unreachable?
The submission is stored in formformform either way, so nothing is lost. Zapier marks the task as errored and retries it; if it stays failed you can replay it from the Zap history, or export the response and add the card by hand.
Related automations
- Add every RSVP to your confirmed guest list
Each RSVP creates a card on the "Confirmed guests" list with the ticket type as a label and dietary notes in the description.
- Create a triage card for every bug report
Reported bugs land as cards on your "Inbox" list, with reproduction steps in the description and a red label on severe ones.
- Drop each job application onto your hiring board
Every application becomes a card on the "Applied" list, labelled with the role and carrying the cover letter in its description.
- Send feature requests to your product backlog
Feature requests become cards on your "Ideas" list, labelled by how badly the person asking needs them.
- Turn custom orders into dated fulfilment cards
Custom orders arrive as cards on your "To fulfil" list, titled with the item and carrying the customer's date as the due date.
- Add new sales leads to your pipeline board
Each sales enquiry lands in the New leads group of your CRM board, tagged "New lead" and ready to work.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free