What this shows

This example shows how TriageFast turns an auth error reported via a support tool into a prioritized GitHub issue so engineers can respond quickly.

Raw feedback

User message

Hey, I tried to connect my account and keep getting "Invalid API key" — it was working yesterday. Now I get a 401 and can't sync orders, please help!

Triage output

Structured result

{
    "type": "bug",
    "severity": "high",
    "title": "Invalid API key causing 401 on sync",
    "summary": "User receives a 401 \"Invalid API key\" when connecting their account via the support-tool sync.",
    "tags": [
        "auth",
        "api",
        "invalid-api-key",
        "401",
        "support-tool"
    ],
    "sentiment": "frustrated",
    "confidence": 0.95
}

Resulting issue

github

401 Invalid API key during support-tool account sync

Description: User reports failing to connect their account via our support-tool with a 401 "Invalid API key" error. This was previously working for the user and is blocking order syncs. Steps to reproduce: 1. Attempt to connect account via support-tool sync flow. 2. Observe 401 response with message "Invalid API key". Raw user message: "Hey, I tried to connect my account and keep getting \"Invalid API key\" — it was working yesterday. Now I get a 401 and can't sync orders, please help!" Expected: Successful connection and order sync. Actual: 401 Unauthorized, connection fails. Impact: User cannot sync orders; support ticket opened and user is blocked. Suggested next steps: Check recent auth key rotations, verify API key validation logic, and inspect logs for 401 events tied to support-tool connector.

Live example

Use the API directly

Send the same raw message to TriageFast and get the structured result back through the normal ingest endpoint.

curl -X POST https://triagefast.app/api/v1/ingest -H "Authorization: Bearer tf_live_xxxx" -H "Content-Type: application/json" -d '{"source":"support-tool","message":"Hey, I tried to connect my account and keep getting \"Invalid API key\" — it was working yesterday. Now I get a 401 and can't sync orders, please help!"}'

How it works

Step 1

Send the message

Post the raw support-tool message to the ingest endpoint.

Step 2

TriageFast classifies it

AI extracts fields like type, severity, title, summary, tags, sentiment, and confidence.

Step 3

Structured output appears in github

A GitHub issue is created with the structured triage data for engineers to act on.

Related examples

Support-tool auth failure converted into GitHub issue