Gmail Support Email to Linear Triage Workflow (n8n, OpenRouter, Sentry)

Automatically triage Gmail support emails and file them into Linear with Jev Decisions + OpenRouter

This n8n workflow pulls new support messages from Gmail every hour, uses OpenRouter to call the Jev Decisions API for labeling, severity, and ownership, optionally enriches with Sentry, Stripe, and an identity admin HTTP API, then creates a routed Linear issue—with human escalation when confidence or sensitivity requires it.

What this workflow does

• Runs hourly to fetch the latest emails sent to your support inbox (default filter: to:support@example.com).
• Skips already-processed messages from prior runs and converts each email body from HTML to Markdown.
• Classifies & prioritizes by sending the email content to the Jev Decisions API (via OpenRouter) to determine:
  • labels, severity, and ownership team
  • tags
  • whether investigative tools should be queried
• If Jev indicates tools should be used, the workflow queries Sentry, Stripe, and/or an identity admin HTTP API, then normalizes and aggregates the evidence.
• Second-pass confirmation: sends aggregated tool findings back to Jev for a revised severity, team, and recommended next action.
• Files in Linear by building a clear issue title/description from the original email plus Jev decisions and tool evidence.
• Determines escalation (filed vs escalated) based on confidence and sensitivity/credentials signals and the filing outcome.

Use cases

• SaaS support teams routing incidents and feature requests into Linear automatically.
• Faster triage for bug reports by pairing Jev classification with Sentry evidence.
• Credential- or account-related investigations enriched via an identity admin API, with escalation when needed.
• Billing-related context added through Stripe queries during support triage.

Technical details

• n8n nodes/integrations: Gmail, Jev Decisions via OpenRouter, Linear, and tool lookups including Sentry and Stripe (plus an identity admin HTTP API).
• Core workflow logic: if, set, code, and conditional execution to run tools only when Jev flags them.
• Setup: provide Gmail OAuth credentials, update the Gmail recipient filter/search query, and add an OpenRouter API credential for the Jev Decisions endpoint.