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.
New submission on your "Apply now" form
Create a card on the "Applied" list with the candidate's name as the title, and the role, availability and cover letter in the description
One-directional. A submission triggers the action — nothing is written back into your form.
Hiring for two or three roles at once does not need an applicant tracking system, but it does need somewhere everyone can see. This flow drops each application onto the "Applied" list as a card named after the candidate and labelled with the role they went for.
Recruiters and founders use it because the board already matches how they think about hiring: a list per stage, cards dragged from screening to interview to offer. Reading a candidate takes one click, and the whole team can see who is waiting.
Setting it up
- 1
Publish the application form and submit a test application against a real open role, so the sample carries the exact option text from Position Applied For.
- 2
Create one Trello label per open role on the hiring board, named to match those options character for character — Zapier matches on the label that already exists.
- 3
Set the formformform "New Submission" trigger to the application form and pull in that sample submission.
- 4
Add "Create Card" against the hiring board with the list fixed to "Applied", so every candidate enters at the same stage.
- 5
Map Full Name into the card's Name field, and select the label using Position Applied For so the board can be filtered down to one role.
- 6
Build the Description with Email Address and Available Start Date at the top, then Cover Letter and Relevant Skills underneath.
- 7
Leave the Members field empty in the action — assignment is a triage decision, and an auto-assigned card tends to get ignored by everyone else.
- 8
Test the Zap, confirm the label matched rather than being left blank, then turn it on and archive the test card.
What maps where
Using the Job Application 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 "Applied" list |
| Position Applied For | Card label, one per open role |
| Available Start Date | Top of the card description |
| Cover Letter | Card description |
| Relevant Skills | Card description, below the cover letter |
| Email Address | First line of the card description |
Variations worth knowing
Follow the Create Card step with Trello's "Create Checklist" action, using the new card's ID. Every applicant then arrives with the same four checks — CV read, screening call, take-home sent, references — so no candidate quietly skips a stage.
Branch on Employment Type with Paths and send each to its own board. Contract hiring usually moves on a different clock from permanent hiring, and one shared "Applied" list makes both look slower than they are.
If something isn't arriving
The label names on the board no longer match the wording of the Position Applied For options. Renaming a role in the form editor breaks the match silently. Update the label text in Trello to match the option exactly, then retest.
Almost always a genuine second submission — people resubmit when a page reloads or when they want to correct something. Check the submission timestamps in your responses list, keep the later card, and archive the earlier one.
Frequently asked questions
Can applicants see which stage they are at?
No, and the board should stay private. Nothing travels back from Trello to the form, so a candidate only knows what you tell them. Most teams send stage updates from their normal mail tool when a card moves.
Can I only create cards for applicants worth interviewing?
Add a Zapier filter before the Trello step and test a field such as Employment Type or Available Start Date. Every application is still stored in formformform, so filtering the board does not throw anyone away.
Is the application data now living in Trello?
A copy of the fields you mapped is. The full submission stays in formformform, where you can search and export it. That matters when someone asks for their data to be removed and you need to find every place it went.
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.
- 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.
- 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.
- 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