Support tickets to Jira with Gemini
Gemini returns a triage decision; Jira, Slack and Gmail get the ticket. This n8n template receives support requests through a POST webhook and puts the request body into a standard structure. The subject and message go to Google Gemini through an AI Agent node, which returns a JSON triage decision that is parsed into fields. A Switch node routes the request. The workflow then creates a Jira issue with the customer details, the AI summary and the triage data, and sends the matching Slack alert and Gmail notification. It is for support teams whose requests can be sent to a webhook.
Steps
- Trigger: POST webhook receives a support request
- Validates the required fields
At least customer email and message. - Google Gemini returns a triage decisionGoogle Gemini
Category, priority, sentiment, SLA, suggested team. - Maps priority to P1–P4, builds the title
- Creates a Jira issueJira Software
- Routes to billing, technical or general
- Output: Slack channel alertSlack
- Output: Gmail notificationGmail
Limits
- Needs four separate credentials.
- Requests must be sent to the webhook by another tool.
What it does well
- The Jira issue carries the AI summary and the triage data.
- The AI decision is parsed into structured fields before routing.
Before you import
Create and add Google Gemini (PaLM/Google AI), Jira, Slack and Gmail credentials in n8n after the import.
Similar templates
Label Gmail emails with Google Gemini
Also for customer support, 5 steps.
Support tickets: AI reply or escalate
Also for customer support, 9 steps.
Gmail triage and drafts with Claude
Also for customer support, 8 steps.
Gmail and Slack: 18 templates compared
Same two apps, different steps.
Gmail and Google Gemini: 11 templates compared
Same two apps, different steps.
Google Gemini and Slack: 6 templates compared
Same two apps, different steps.
Sort incoming requests
Other templates that do this task.