Loading…
Loading…
Jotform to Trello, wired so submissions become cards in the right list with the details your team needs on the front.
If your team runs on Trello, the Jotform integration turns each submission into a card. A request, a lead, a bug report, or an order shows up as a card in the list you choose, with the form details in the description, ready to drag through your workflow. For Trello-centric teams, it removes the step of manually creating a card from an email.
It's one of the more straightforward integrations: cards land reliably once it's pointed at the right board and list. The things worth setting up are which list new cards enter, what goes in the card name versus the description, and how attachments come across. There's no deep field-typing to wrestle with, the way Airtable or monday have, which makes this mostly a 'configure it once' job. This page covers how cards get created, the handful of gotchas, and when a webhook gives you more control.
I spent five years on Jotform's product team. Trello was a low-friction integration: people connected it and it worked. The occasional question was about card naming and which list cards landed in. Here's how to set it up so cards arrive useful.
In Jotform's Integrations tab you authorize Trello and choose the target board, then the list where new cards should land (usually an intake or 'To Do' list). Every submission creates a card in that list.
You map a form field to the card name (the submitter's name or a request title) and choose which fields fill the card description. Put the details the team needs to triage on the front: name, what they want, contact info.
On submit, Jotform creates a card in the chosen list with the mapped name and description. The team then works it like any other card: assign members, add labels, move it across lists.
Uploaded files attach to the card, typically as links back to Jotform-hosted files. The card carries the submission's content so the team has what they need without opening Jotform.
An internal request or support form creates a card in an intake list, and the team drags it through 'In Progress' and 'Done.' Trello's simplicity is the appeal: no field types to manage, just cards moving across lists.
A contact form drops leads as cards in a 'New Leads' list, where a salesperson labels and assigns them. Lightweight CRM-by-Trello for small teams that don't want a real CRM yet.
Contributors submit ideas or content through a form into a backlog list, and editors prioritize by moving cards. Each submission is a card the team can comment on and schedule.
A bug-report form creates cards in a triage list with the report details in the description and any screenshots attached. The team triages from the board instead of an inbox.
Every submission goes to the single list you configured. There's no conditional routing to different lists or boards based on a field. If different request types should go to different lists, set up separate integrations per form or branch the logic in a webhook.
If the card name maps to a generic field, the board fills with cards that look alike. Map a meaningful field (name plus request type) to the card name so the team can scan the list without opening each card.
The integration creates the card but doesn't apply labels, due dates, or assign members based on form answers. Those stay manual unless you drive them with a Trello automation (Butler) reacting to the new card, or a webhook.
Uploaded files usually attach as links to Jotform-hosted copies rather than as files stored in Trello. If the submission is later deleted or its privacy changes, those links can break. For critical files, also save them to a storage integration like Drive or Dropbox.
I ran into them for five years on the Jotform product team. Book a free call and I'll tell you exactly how to handle your Trello setup, or send me the details first.
Skip the native integration if you need conditional routing (different submissions creating cards on different boards or lists) or automatic labels, due dates, and assignments based on form answers: a webhook, Zapier, or Trello's Butler automation gives you that. For structured, filterable data with typed fields, Airtable or monday fit better than Trello's free-form cards. For simple card creation into one list, though, the native integration is all you need.

The onboarding flow every agency wishes they had before their first client was late with assets

Lead capture with scoring, dedup, CRM sync, and Slack alerts on the ones worth interrupting for.

NPS that actually does something: detractors escalate, promoters refer, and leadership gets the monthly read
In Jotform's Integrations tab, authorize Trello, choose the board and list, then map a form field to the card name and select which fields fill the description. Each submission creates a card in that list. Uploaded files attach to the card, usually as links to Jotform-hosted copies.
Not with the native integration, which creates cards in a single chosen list. For conditional routing, where different request types go to different lists or boards, set up separate integrations per form or use a webhook or Zapier to branch the logic.
No. The integration creates the card but doesn't apply labels, due dates, or members based on form answers. To automate those, use Trello's Butler automation reacting to the new card, or drive the card creation through a webhook or Zapier.
Use Trello when you want a simple card-on-a-board workflow with no field types to manage and you're moving items through stages. Use Airtable (or monday) when you need structured, filterable data with typed fields and linked records. Trello is lighter; Airtable is more of a database.
Free 20-minute call. I'll tell you which workflow fits your Trello setup and what it would take to build, or you can send me the details first.