# Automated GLPI ticket deadline alerts with Microsoft Teams: n8n workflow

> Started by a clock. It calls services over plain HTTP rather than through connectors. 14 steps, 2 branches, 1 loop or waits: a working afternoon to...

Source: https://millionrounds.com/workflow/automated-glpi-ticket-deadline-alerts-with-microsoft-teams (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)

# Automated GLPI ticket deadline alerts with Microsoft Teams

Started by a clock. It calls services over plain HTTP rather than through connectors. 14 steps, 2 branches, 1 loop or waits: a working afternoon to understand properly.

Medium

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fautomated-glpi-ticket-deadline-alerts-with-microsoft-teams)

**14 steps** Medium: a working afternoon

**2** Branches: places the flow splits

**1** Loop or waits

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

## The flow

Starts it 1 Logic 8 Service 5

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

- 1 **Schedule Trigger** Schedule trigger *Starts it*
- 2 **Configuration Variables** Set *Logic*
- 3 **Get session token** Http Request *Service*
- 4 **Tickets about to expire** Http Request *Service*
- 5 **Split Out** Split Out *Logic*
- 6 **Loop Over Items** Split In Batches *Logic*
- 7 **Aggregate** Aggregate *Logic*
- 8 **Support Technician 1?** If *Logic*
- 9 **End session1** Http Request *Service*
- 10 **Send a message to Support Technician 1** Microsoft Teams *Service*
- 11 **Support Technician 2?** If *Logic*
- 12 **No Operation, do nothing2** No Op *Logic*
- 13 **Send a message to Support Technician 2** Microsoft Teams *Service*
- 14 **No Operation, do nothing3** No Op *Logic*

## How it's built

- **Starts on:** A clock
- **Steps:** 14, with 2 branches, 1 loop or waits
- **Size:** Medium: a working afternoon
- **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 a clock.

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?

Plan an afternoon. 14 steps is enough that you should read each one before running it.

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 14 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%2Fautomated-glpi-ticket-deadline-alerts-with-microsoft-teams)
- **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.

- [**Bidirectional ticket sync between Freshdesk and Linear** 14 steps](https://millionrounds.com/workflow/bidirectional-ticket-sync-between-freshdesk-and-linear)
- [**Multi-channel customer support automation suite with Slack** 14 steps · Email, Slack](https://millionrounds.com/workflow/multi-channel-customer-support-automation-suite-with-slack)
- [**Triage and escalate HubSpot tickets to Jira with Slack SLA** 14 steps · HubSpot, Jira](https://millionrounds.com/workflow/triage-and-escalate-hubspot-tickets-to-jira-with-slack-sla)
- [**Triage and route support emails with Gemini and Gmail** 14 steps · Gmail, Google Sheets](https://millionrounds.com/workflow/triage-and-route-support-emails-with-gemini-and-gmail)
- [**AI customer support agent - never sleep, never miss a customer** 14 steps · calls a model · Email, Notion](https://millionrounds.com/workflow/ai-customer-support-agent-never-sleep-never-miss-a-customer)
- [**Airbnb Telegram agent - AI-powered accommodation search** 14 steps · calls a model · Telegram](https://millionrounds.com/workflow/airbnb-telegram-agent-ai-powered-accommodation-search)