Turn Crisp support chats into Linear bug tickets

This workflow runs whenever a visitor sends a new message in one of my Crisp live chat conversations. Trigger it with a webhook from Crisp on the visitor-message event so the agent runs in real time as new customer messages arrive.

When it fires, use Crisp's Get Messages In Conversation to pull the full conversation for that session, so you are working from the whole thread and not just the latest line. Then, as the first and most important step, decide whether the customer is reporting a genuine bug or technical problem. Ignore general questions, how-to requests, account or billing questions, and sales chatter. Gate hard here: only continue when you are confident this is a real bug report. If it is not, stop without creating a ticket or replying.

When it is a genuine bug, draft a clear, reproducible engineering ticket and create it in Linear using Create Issue on my product team. Write a concise, specific title and a well-structured description. Choose an appropriate priority based on severity: urgent for a total outage or data loss, high for a broken core feature, normal for a smaller defect, and low for cosmetic issues.

The Linear issue description must include the steps the customer reported (what they did and what happened), any browser, device, operating system, or app version details they mentioned, and a link back to the original Crisp conversation so engineers can open the full context. If some of these details were not provided, say so rather than inventing them.

After the ticket is created, reply in the same Crisp conversation using Send Message In Conversation to let the customer know their issue has been logged and will be looked at. Keep this reply short, friendly, and customer-facing; do not paste the internal ticket details or the Linear link into the chat. When sending, the message must come from an operator and include the from and origin values that Crisp requires on an outgoing message.