Turn Scattered User Feedback into a Prioritized Feature Board
An n8n workflow that collects feedback from a form, support inbox or Slack, has Claude categorize and de-duplicate each item into feature themes, and adds or upvotes cards on a Trello board — so product decisions rest on aggregated signal instead of the loudest recent complaint.
- 1
Collect the feedback
A
Webhooknode receives feedback items as{ text, source }from any channel you wire up. - 2
Categorize with Claude
An
HTTP Requestto Claude returns strict JSON: a canonicalfeaturename, atheme, and a one-linesummary. This turns free-form text into a consistent label. - 3
Find or create the card
A
Trellosearch checks for an existing card named after the feature. AnIFbranches: found → increment its vote count; not found → create a new card with the summary. - 4
Keep the board ranked
Store the vote count in the card and sort the list by it, so the most-requested features rise to the top automatically — a living, evidence-based roadmap input.
Frequently asked questions
How does it avoid duplicate cards?
Claude maps each new feedback item to an existing theme when one fits, returning a canonical feature name. The workflow searches the board for that name and, if found, increments a vote count on the existing card instead of creating a new one — so demand aggregates.
What sources can feed it?
Anything that can POST to a webhook: a feedback form, forwarded support emails, a Slack shortcut, or intercom/helpdesk exports. Normalize each into { text, source } and the rest of the pipeline is identical regardless of origin.