AI-triage Typeform responses into Trello cards

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.