AI-triage Typeform responses into Trello cards

Every new Typeform submission gets categorized for urgency and request type, turned into a Trello card with the right list and labels, and posted to Slack.

Agentic Task
TypeformTrelloSlackOperationsCustomer SupportFeedback TriageNotifications & Alerts

Build an agent workflow that runs every time a new response is submitted to a configured Typeform. Use a Typeform outgoing webhook on form-submit as the trigger.

When a response comes in, the agent should:

1. Read every field from the Typeform payload (question titles and answers, including hidden fields if present).

2. Use an LLM to: (a) categorize the submission against an operator-configured set of categories — urgency level, request type, and priority — where the operator supplies the allowed values and a short description of each; (b) write a clean 2 to 4 sentence summary of what the requester is asking for; (c) suggest a due date based on the urgency (the operator configures how many days each urgency level maps to).

3. Call Trello's Create a Card operation to add a card to the operator-configured board and list. The card title should be a short tag plus a one-line summary (for example, "[Enterprise lead] Acme exploring SSO rollout"). Set the due date computed in step 2. Apply Trello labels that match the AI's categorization — the operator pre-maps each category value to a Trello label ID. The card description should put the AI summary at the top, then list every original form question and answer as a Q/A block.

4. If the form answers contain obvious to-do items (for example a "what assets do you need delivered?" field), call Trello's Create a Checklist and Create a Checklist Item operations to add a checklist with one item per inferred task. This step is optional and can be skipped if no clear to-dos exist.

5. Call Slack's Send a Message operation to post to the operator-configured channel. The message should include a link to the new Trello card, the AI summary, the assigned labels, and a clear urgency flag (for example, prefix with a siren emoji if urgency is critical). The operator should also be able to configure a minimum urgency for posting — for example, only post to Slack when urgency is high or critical.

Operator-configurable parameters: Typeform form ID; Trello board ID and list ID where new cards land; Trello label ID mappings per category value (urgency, request type, priority); due-date mapping per urgency level in days from submission; Slack channel ID; minimum urgency level required to send a Slack message; an optional list of keywords that, when present in any answer, force urgency to critical.

The same workflow should work for sales lead intake, design brief intake, or support ticket intake just by changing the category values, label mappings, and target board, list, and channel. Do not hardcode any of those values in the workflow logic.

Additional information

What does this prompt do?
  • Picks up every new Typeform submission the moment it lands.
  • Reads the answers and tags each submission for urgency, request type, and priority using AI.
  • Creates a Trello card on your intake board with a clean summary, the right labels, a due date, and all the original answers in the description.
  • Posts a Slack message with a link to the new card and a flag for anything urgent.
What do I need to use this?
  • A Typeform account and the form you want to monitor.
  • A Trello account with an intake board, the list where new requests should land, and the labels you want the AI to apply.
  • A Slack workspace and the channel where your team wants to see new requests.
How can I customize it?
  • Swap the categories the AI assigns. Use it for sales leads, design briefs, or support tickets by changing the urgency levels, request types, and labels.
  • Point it at a different Trello board, list, or set of labels so each team has its own intake queue.
  • Choose which Slack channel gets pinged, and tell it what counts as urgent so quiet requests stay quiet.

Frequently asked questions

Can the same workflow handle sales leads, design briefs, and support tickets?
Yes. The categories, Trello board, labels, and Slack channel are all set when you connect the workflow. Run a separate copy for each intake type, or change the settings to switch what it triages.
How does the AI decide what urgency or request type to assign?
You give it the list of categories you want (for example, low, medium, high, critical) and a short description of each. The AI reads the form answers and picks the best match, then writes a 2 to 4 sentence summary of what the person is asking for.
What does the new Trello card look like?
The title is a short label plus a one-line summary. The description starts with the AI summary, then lists every original form question and answer. The card gets labels that match the AI's tags and a due date based on its urgency.
Does this work on Trello Free?
Yes. Creating cards, adding labels, setting due dates, and adding checklists all work on the free plan.
Can I keep the Slack alert just for urgent requests?
Yes. You can tell the workflow to only post to Slack when urgency is high or critical, so your team channel only pings for things that actually need attention.

Stop hand-routing every form submission.

Connect Typeform, Trello, and Slack once, and Geni triages every new response, files the card, and pings the right channel.