# User-friendly technical support portal for GLPI ticket management: n8n workflow

> Started by someone submitting a form. It calls services over plain HTTP rather than through connectors.

Source: https://millionrounds.com/workflow/user-friendly-technical-support-portal-for-glpi-ticket-manag (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)

# User-friendly technical support portal for GLPI ticket management

Started by someone submitting a form. It calls services over plain HTTP rather than through connectors. 23 steps, 5 branches: large, and worth reading before you trust it with anything live.

Large

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fuser-friendly-technical-support-portal-for-glpi-ticket-manag)

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

**5** Branches: places the flow splits

**0** Loops or waits

**0** Services by connector: it calls them over plain HTTP

## The flow

Starts it 1 Logic 9 Service 13

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

- 1 **Technical Support Portal** Form trigger *Starts it*
- 2 **Configuration Variables** Set *Logic*
- 3 **Contact information** Form *Service*
- 4 **Get session token** Http Request *Service*
- 5 **1. Request or incident** Switch *Logic*
- 6 **Request Form** Form *Service*
- 7 **Incident Form** Form *Service*
- 8 **1. Check if File Exists** If *Logic*
- 9 **2. Check if File Exists** If *Logic*
- 10 **1. Upload File** Http Request *Service*
- 11 **Request Category ID** Code *Logic*
- 12 **2. Upload File** Http Request *Service*
- 13 **Incident Category ID** Code *Logic*
- 14 **Create Request** Http Request *Service*
- 15 **Create Incident** Http Request *Service*
- 16 **If1** If *Logic*
- 17 **If** If *Logic*
- 18 **1. Link File to Ticket** Http Request *Service*
- 19 **Finish Request** Form *Service*
- 20 **2. Link File to Ticket** Http Request *Service*
- 21 **Finish Incident** Form *Service*
- 22 **Sign Out GLPI** Http Request *Service*
- 23 **No Operation, do nothing** No Op *Logic*

## How it's built

- **Starts on:** Someone submitting a form
- **Steps:** 23, with 5 branches
- **Size:** Large: read it before trusting it with anything live
- **Connects to:** Nothing by connector; it calls services over plain HTTP
- **Model:** None. This is plumbing, not judgement

## Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on someone submitting a form.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Take your time. At 23 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 23 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%2Fuser-friendly-technical-support-portal-for-glpi-ticket-manag)
- **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.

## Workflows like it

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

- [**Process Stripe test refunds with Allowly** 23 steps](https://millionrounds.com/workflow/process-stripe-test-refunds-with-allowly)
- [**AI email support system: Gmail, Gemini, GPT-4, Slack & Google** 23 steps · calls a model · Gmail, Google Drive](https://millionrounds.com/workflow/ai-email-support-system-gmail-gemini-gpt-4-slack-and-google)
- [**Build RAG-powered support agent for Jira issues with Pinecone** 23 steps · calls a model · Pinecone](https://millionrounds.com/workflow/build-rag-powered-support-agent-for-jira-issues-with-pinecon)
- [**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)
- [**Customer Support with Gemini** 23 steps · calls a model](https://millionrounds.com/workflow/customer-support-with-gemini)
- [**Draft grounded Gmail support replies from a Notion KB** 23 steps · calls a model · Gmail, Notion](https://millionrounds.com/workflow/draft-grounded-gmail-support-replies-from-a-notion-kb)