How to Connect Typeform to Trello (Zapier, Make or Email)

Trello is often the first place a small team organises its work, and Typeform is often the first form tool it reaches for. Joining them is a natural next step: a new response becomes a card, the card lands in a list, someone picks it up. It is one of the simplest integrations to build. It is also one of the easiest to outgrow without noticing, so this guide covers both the setup and the signs that the board has become the wrong place for the work.

If you are wondering whether Trello should be in your stack at all, our piece on replacing Trello, Asana and ClickUp is the wider argument. The short three-step version of this setup is on the Typeform to Trello integration page.

There are four ways to get Typeform responses onto a Trello board. They trade setup effort against control.

Typeform has also offered a Trello Power-Up in the past. Search the Power-Ups directory on your board to see what is listed for your account now, and read what it actually does before you rely on it. For the common job, every new response becoming a new card with its answers in the right places, the routes in the table are the ones that are documented and supported.

Every Trello board has its own email address, found in the board menu under the email to board setting. Anything sent to that address becomes a card in the list you choose: the subject becomes the card name and the body becomes the description. Typeform, meanwhile, can send a notification email to you each time someone responds. Point that notification at the board address and you have a working integration with no third tool.

It is crude but useful. Customise the notification subject so it includes the respondent's name or company, because that subject becomes the card title. Keep the email body to the answers. Labels may differ slightly in your version, and some Trello setups let you add labels or members with hashtags and mentions in the subject, which is worth testing on yours.

The limits are real. You cannot map answers to custom fields, you cannot route different answers to different lists, and if the email format changes your cards change with it. For a handful of responses a week, it is fine. Beyond that, move to an automation tool.

This is the setup most teams should use. It is the same shape in both tools, and our Make vs Zapier comparison will help if you are choosing between them.

Two small habits save a lot of trouble later. Give each Typeform question a stable reference name before you map it, so rewording a question on the live form does not break the mapping. And connect both apps from a shared team login rather than a personal one, so the integration does not stop the week its builder leaves.

A card that says "New Typeform entry" is a notification, not a piece of work. Design the card so someone scanning the list knows what it is without opening it.

Name: two or three answers joined together, such as company and request type. Description: every question and answer, labelled, plus a link to the response in Typeform. Trello descriptions support basic formatting, so put each question in bold and the answer beneath it. Labels: one label per value of the answer you sort by, such as service line or urgency. Keep the label set small and identical to the form options. Due date: set relative to submission if the request has a response promise. Source: use Typeform hidden fields to capture the campaign or page, and put it in a custom field or the description. It is the only way to answer later where the good requests came from.

Finally, decide what happens to cards when the work is finished. An intake list that only ever grows becomes unreadable within a season. Agree a done list, archive cards from it on a regular rhythm, and if you need a record of every request, keep that record in Typeform's results or a spreadsheet export rather than in an ever-longer board. The board is for work in flight. Treating it as an archive is how teams end up scrolling past finished requests to find the live ones, and how a new request gets missed among them.

You can build branching in the automation tool: a Zapier Path per request type, each writing to a different list. It works. It also hides the logic in a tool most of the team never opens. A cleaner pattern is to keep the Zap to one trigger and one create card step, apply a label from the deciding answer, and let Trello's built-in automation do the rest: when a card with the "billing" label lands in intake, move it to the finance list and add the finance lead.

The rules then live on the board, where anyone can see and change them. When something is routed wrongly, the person who notices can fix it without asking who built the Zap. Automation limits depend on your Trello plan, so check yours before you lean on it.

Typeform plus Trello is a good starting point. A few signals say it has become the wrong shape for the job:

The cards are really leads. If the form is an enquiry and the card is where you track whether you replied, you are running a sales pipeline on a kanban board. It has no contact history, no follow-up schedule and no record of what was sent.

You keep a second copy somewhere. If someone exports cards to a spreadsheet each month to see what came in and what closed, the board is not holding the information you need.

The automations multiply. One Zap becomes four, then a second form, then a step that also adds the person to your email tool. Each one is another subscription allowance to watch and another thing that can stop.

Replies are slow. The card exists, but nobody answers the person who filled in the form until someone notices the card. The integration moved the data. It did not move the work.

If the form is internal requests or project intake, none of this applies and Trello is a perfectly good home. If the form is how customers reach you, the destination should be a CRM record with a reply attached. OpsWyse handles that whole path in one system: the form creates the contact and the task, and Wyse drafts the first reply for someone to approve before it sends. That is more than a small team doing internal intake needs, and for them, Typeform plus Trello is the right size.