--- title: "Feature requests to a Trello backlog" description: "Every feature request submission becomes a Trello card on your \"Ideas\" list, titled with the request and labelled by how much the person asking needs it." url: "https://www.formformform.com/automations/trello-feature-requests-into-backlog" type: static generatedAt: "2026-08-23T18:56:58.727Z" --- ![Trello logo](/logos/integrations/trello.svg) # Send feature requests to your product backlog Feature requests become cards on your "Ideas" list, labelled by how badly the person asking needs them. When this happens New submission on your feature request survey Do this Create a card on the "Ideas" list with the suggestion as the title, the full comment in the description, and a label for how important the request is One-directional. A submission triggers the action — nothing is written back into your form. Feature requests get lost between an inbox, a support tool and somebody's notes app. This flow gives them one destination: a card on the "Ideas" list of your product board, titled with the requester's own headline and labelled by how strongly they need it. Product teams pull that list open during planning, group the cards that describe the same problem, and drag the survivors into the backlog. The value is that the request arrives in the requester's words, along with the workaround they are using today. ## Setting it up 1. 1 Publish the request form somewhere people already are — in-app, in the help centre footer — and submit one request so Zapier has a full sample. 2. 2 Create a label on the product board for each option in the importance question, before you build the Trello step. 3. 3 Set the formformform "New Submission" trigger to the request form and pull in that sample. 4. 4 Add "Create Card" against the product board with the list set to "Ideas", so nothing lands in the committed part of the backlog by accident. 5. 5 Map Feature Title into the card Name on its own — it is already a short headline, which is what makes this list skimmable during planning. 6. 6 Build the Description from What problem does this solve? and What would you like to see?, in that order, so the problem is read before the proposed fix. 7. 7 Add How are you working around it today? and Who else would benefit? at the foot of the description; both are what decide priority in the planning session. 8. 8 Select the label from How important is this to you?, test the Zap, then turn it on and set a recurring calendar slot to actually work the list. ## What maps where Using the [Feature Request Form](https://www.formformform.com/templates/feature-request-form) as the starting point. These are its real fields — swap in your own and the mapping works the same way. Form field Trello Feature Title Card name on the "Ideas" list How important is this to you? Card label What problem does this solve? Card description What would you like to see? Card description, under the problem How are you working around it today? Foot of the card description Who else would benefit? Foot of the card description ## Variations worth knowing Label by area of the product instead Add a question asking which part of the product the request touches — billing, reporting, mobile — and map that to the label rather than importance. Grouping by area suits teams who plan a quarter around one surface at a time. Keep requests from paying customers visible Add a Zapier filter on the email domain, or a plain question asking whether the person is a customer, and give those cards their own list. Requests that come with revenue behind them tend to need a different conversation from general suggestions. ## If something isn't arriving Every card comes through with the same label The label was hard-coded in the Trello step instead of being mapped. Open the Create Card action, clear the fixed selection, and insert the value from How important is this to you? so Trello matches on the answer that was given. Card titles are full paragraphs and the list is unreadable A long-answer question was mapped into the Name field. Use Feature Title there, which is a single line by design, and move the longer text into the description where Trello will render it properly. ## Frequently asked questions How do I stop the "Ideas" list growing until nobody reads it? Work it on a schedule rather than continuously. Once a fortnight, merge the cards describing the same problem, archive what you will not build, and move two or three into the backlog. A list nobody prunes stops being consulted within a month. Can people vote on the requests that are already there? Not through the form — each submission creates its own card, and nothing reads the board back. If you want a ranking, run a separate poll form listing the shortlist, and count the responses in formformform. Does the person who asked hear anything when we ship it? Only if you tell them. Nothing is sent back from Trello. Collect Email Address on the form and keep it in the card description, so whoever closes the card has the address to write to when the feature goes out. ## Related automations - [Add every RSVP to your confirmed guest list](https://www.formformform.com/automations/trello-rsvps-to-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](https://www.formformform.com/automations/trello-bug-reports-to-triage) 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](https://www.formformform.com/automations/trello-applicants-into-hiring-pipeline) Every application becomes a card on the "Applied" list, labelled with the role and carrying the cover letter in its description. - [Turn custom orders into dated fulfilment cards](https://www.formformform.com/automations/trello-orders-to-fulfilment-list) 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](https://www.formformform.com/automations/trello-leads-to-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](https://www.formformform.com/automations/monday-sales-enquiries-to-pipeline) Each sales enquiry lands in the New leads group of your CRM board, tagged "New lead" and ready to work. - [All Trello integration details →](https://www.formformform.com/integrations/trello) - [Start from the Feature Request Form →](https://www.formformform.com/templates/feature-request-form) - [Browse every automation →](https://www.formformform.com/automations) ## 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](https://app.formformform.com/register?utm_source=landing&utm_medium=bottom&utm_campaign=automations&utm_content=trello-feature-requests-into-backlog)