Route Typeform feedback into the right Discord channel

When someone submits our Typeform feedback form, I want an agent to triage the response and route it into the right Discord channel with a discussion thread underneath so the team can talk it through.

Trigger: a Typeform webhook. Typeform natively sends outgoing webhooks the moment a response is submitted, so subscribe to the form's response-submitted webhook and parse the payload for the form title, the answers, and any respondent identifiers.

Read the answers and classify the response as exactly one of: bug, feature request, praise, question, or other. Then write a one-paragraph summary (three to five sentences) that quotes the single most useful verbatim line from the response inside quotation marks, so a reader gets the substance without opening Typeform.

Pick the target Discord channel from a user-configured classification-to-channel map. Typical defaults look like: bug goes to #bugs, feature request goes to #ideas, praise goes to #wins, question goes to #support, and other goes to a fallback channel. The map should be an input on the workflow, not hardcoded, so the user can add categories or rewire routing without editing code.

Use Discord's Send a Message operation to post a formatted embed card into the chosen channel. The card should include: title set to the category label plus a short summary (for example, "Bug: dashboard crashes on Safari"); description set to the one-paragraph summary with the verbatim quote inline; footer set to the respondent's name and email ONLY if the form explicitly captured them AND the response contains an opt-in signal (a consent checkbox answer). When in doubt, omit PII entirely. Pick a category-appropriate embed color, for example green for praise, red for bug, blurple for feature request, yellow for question, grey for other.

After the message posts, use Discord's Create Thread from Message operation on that same message to open a triage thread. Name the thread as the category label plus the first 40 characters of the summary, trimmed cleanly at a word boundary (for example, "Bug: dashboard crashes on Safari when uploa"). This keeps the channel readable while giving the team a dedicated place to discuss each response.

Fallback: if the Typeform webhook payload is missing any field the agent needs (Typeform sometimes trims very long responses or file uploads in the webhook body), call Typeform's Retrieve Responses using the response ID from the webhook to fetch the full response before classifying.

Nuance to keep in mind. PII handling is gentle: only include name or email in the footer if the form explicitly opted in, and never in the title or description. The classification-to-channel map is a workflow input, not hardcoded, so the user can rewire routing at any time. The thread name is always category plus the first 40 characters of the summary, trimmed at a word boundary. Do not create the thread if the initial Send a Message call fails.