CHATBOTS

Capture Discord Feature Requests as Trello Cards

When a member asks about a feature that isn't on the roadmap, the bot confirms it's not tracked, creates a new Trello card in the Backlog, and links the member to follow it.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew feature question in DiscordDiscordDiscord
  • ActionSearch Trello for matching cardTrelloTrello
  • LogicBranch when no card exists
  • ActionNormalize request into card title with OpenAIOpenAI
  • ActionCreate or upvote Backlog card in TrelloTrelloTrello
  • OutputConfirm and share card link in DiscordDiscordDiscord

What it does

Turns unanswered 'is X shipped yet?' questions into roadmap input. If the bot can't find a matching Trello card, it treats the question as a signal: it creates (or upvotes) a Backlog card capturing the request and tells the member it's now tracked, so demand is recorded instead of lost in chat.

When to use it

Use it when community questions reveal features you aren't tracking yet and you want that demand to flow straight into Trello. Pairs well with the status-answerer bot for the cases where no card exists.

How it works

  1. 1A new feature question in Discord triggers the flow.
  2. 2The bot searches the Trello board for a matching card.
  3. 3A branch fires only when no card is found.
  4. 4OpenAI normalizes the request into a clean card title and summary.
  5. 5The bot checks the Backlog for a near-duplicate; if found it adds a vote comment, otherwise it creates a new Backlog card.
  6. 6The bot replies in Discord confirming the request is tracked and shares the card link.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DiscordCommunity channels + voice + bots.
  2. 2
    Connect TrelloKanban boards for everything.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.