# Auto-assign support tickets with Jira and Supabase: n8n workflow

> Started by a clock, and works across Jira and Supabase vectors. It puts OpenAI behind a retrieval step, so answers are drawn from documents you supply...

Source: https://millionrounds.com/workflow/auto-assign-support-tickets-with-jira-and-supabase (Millionrounds; every figure on the page links to its filing or article)

[Automation library](https://millionrounds.com/workflows) · [Customer support](https://millionrounds.com/workflows?category=Customer+support#library)

# Auto-assign support tickets with Jira and Supabase

Started by a clock, and works across Jira and Supabase vectors. It puts OpenAI behind a retrieval step, so answers are drawn from documents you supply rather than from the model alone. 28 steps, 1 branch, 2 loops or waits: large, and worth reading before you trust it with anything live.

Large Calls a model: OpenAI Retrieval

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fauto-assign-support-tickets-with-jira-and-supabase)

**28 steps** Large: read it before trusting it with anything live

**1** Branch: places the flow splits

**2** Loops or waits

**2** Services it connects to

## The flow

Starts it 2 Model 10 Logic 10 Service 6

The steps in the order they run, from what starts it.

- 1 **Schedule Trigger** Schedule trigger *Starts it*
- 2 **Embeddings OpenAI** Embeddings Open Ai *Model*
- 3 **Recursive Character Text Splitter** Text Splitter Recursive Character Text Splitter *Model*
- 4 **Embeddings OpenAI1** Embeddings Open Ai *Model*
- 5 **OpenAI Chat Model** Lm Chat Open Ai *Model*
- 6 **Schedule Trigger1** Schedule trigger *Starts it*
- 7 **OpenAI Chat Model1** Lm Chat Open Ai *Model*
- 8 **Last 50 Resolved** Jira *Service*
- 9 **Issues Similarity Database** Vector Store Supabase *Model*
- 10 **Default Data Loader** Document Default Data Loader *Model*
- 11 **Supabase Vector Store** Vector Store Supabase *Model*
- 12 **Find Similar Issues + Assignees** Agent *Model*
- 13 **Get Unassigned Tickets more than 5 days** Jira *Service*
- 14 **To Structured Output** Information Extractor *Model*
- 15 **Remove Duplicates** Remove Duplicates *Logic*
- 16 **For Each Issue** Split In Batches *Logic*
- 17 **Issues to Items** Split Out *Logic*
- 18 **Collect Fields** Set *Logic*
- 19 **Issue Ref** No Op *Logic*
- 20 **If has Items?** If *Logic*
- 21 **For Each User** Split In Batches *Logic*
- 22 **Skip** No Op *Logic*
- 23 **Count Assigned Open Issues per User** Summarize *Service*
- 24 **Check User Workflow** Jira *Service*
- 25 **Sort By Most Capacity** Sort *Logic*
- 26 **Tally In-Progress Issues per User** Set *Logic*
- 27 **Assign User to Ticket** Jira *Service*
- 28 **Add Comment to Issue** Jira *Service*

## How it's built

- **Starts on:** A clock
- **Steps:** 28, with 1 branch, 2 loops or waits
- **Size:** Large: read it before trusting it with anything live
- **Connects to:** Jira, Supabase vectors
- **Model:** OpenAI
- **Retrieval:** Answers are drawn from documents you supply, not from the model alone

## Questions

What does it need to run?

An n8n account, plus your own Jira and Supabase vectors accounts, and a key for OpenAI. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

Yes. It calls OpenAI. Its answers draw on documents you give it, not on the model alone. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Take your time. At 28 steps it is large: read it before trusting it with anything live.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

**Before you run it**

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 28 steps before you point it at anything that matters.

## Run it in n8n

- **Create your n8n account** Free to start. n8n is where the workflow runs. [Create an n8n account ↗](https://millionrounds.com/n8n)
- **Download the workflow** Free with a Millionrounds account. [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fauto-assign-support-tickets-with-jira-and-supabase)
- **Paste it into n8n** Open a new workflow in n8n and paste. Then connect your own accounts.

Stored with the author's traces removed: canvas notes, instance identifiers, saved credential names and any live document they had left behind.

## Connects to

Each opens the other workflows that use it.

[Jira](https://millionrounds.com/workflows?service=Jira#library)[Supabase vectors](https://millionrounds.com/workflows?service=Supabase+vectors#library)

## Workflows like it

Also customer support, with the same services where possible, closest in size first.

- [**Automate customer support issue resolution with OpenAI** 29 steps · calls a model · Jira, Notion](https://millionrounds.com/workflow/automate-customer-support-issue-resolution-with-openai)
- [**Triage and resolve stale Jira tickets with OpenAI and Notion** 29 steps · calls a model · Jira, Notion](https://millionrounds.com/workflow/triage-and-resolve-stale-jira-tickets-with-openai-and-notion)
- [**Automate B2B SaaS renewal risk management with CRM** 30 steps · Gmail, HubSpot](https://millionrounds.com/workflow/automate-b2b-saas-renewal-risk-management-with-crm)
- [**Create a WhatsApp customer support bot with OpenAI** 23 steps · calls a model · Gmail, Google Calendar](https://millionrounds.com/workflow/create-a-whatsapp-customer-support-bot-with-openai)
- [**Escalate overdue and blocked Jira tickets with Gmail** 33 steps · Gmail, Jira](https://millionrounds.com/workflow/escalate-overdue-and-blocked-jira-tickets-with-gmail)
- [**AI WhatsApp support with Gemini and Twilio** 22 steps · calls a model · Airtable, Google Drive](https://millionrounds.com/workflow/ai-whatsapp-support-with-gemini-and-twilio)