Skip to main content

Automated GLPI ticket deadline alerts via Microsoft Teams

Workflow preview

Workflow preview
100%
Automated GLPI ticket deadline alerts via Microsoft Teams preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

This n8n workflow provides an automated notification system that monitors tickets in GLPI (Gestionnaire Libre de Parc Informatique) and sends proactive alerts through Microsoft Teams when tickets a...

Best for

  • Ticket Management automation workflows
  • Multimodal AI automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.noop, n8n-nodes-base.httprequest, n8n-nodes-base.set, n8n-nodes-base.microsoftteams, n8n-nodes-base.aggregate, n8n-nodes-base.if, n8n-nodes-base.scheduletrigger, n8n-nodes-base.splitinbatches

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Luis Hernandez.

Original n8n.io source

1.1 Workflow description

Title
Automated GLPI ticket deadline alerts via Microsoft Teams
Workflow name
Automated GLPI ticket deadline alerts via Microsoft Teams

Overview

This n8n workflow provides an automated notification system that monitors tickets in GLPI (Gestionnaire Libre de Parc Informatique) and sends proactive alerts through Microsoft Teams when tickets are approaching their expiration dates.

Key Features

🕘 Automated Scheduling

  • Daily execution scheduled at 9:00 AM
  • Continuous monitoring without manual intervention
  • Customizable scheduling configuration

🎯 Intelligent Deadline Detection

  • Automatic identification of tickets expiring within the next 2 days
  • Configurable date-based filtering criteria
  • Efficient processing of multiple simultaneous tickets

👥 Targeted Notifications

  • Personalized alerts sent to specific technicians via Microsoft Teams
  • Automatic assignment based on ticket assignee
  • Structured messages with key ticket information

🔧 Complete GLPI Integration

  • Secure connection through GLPI REST API
  • Authentication with application tokens
  • Automatic session management (initiation and closure)

Technical Functionalities

Data Processing

  • Extraction: Automatic queries to GLPI database
  • Filtering: Ticket separation by assigned technician
  • Transformation: Data formatting for readable notifications

Conditional Flow

  • Automatic evaluation of responsible technician
  • Intelligent notification routing
  • Handling of cases without specific assignment

Session Management

  • Automatic session initiation with GLPI
  • Secure session token maintenance
  • Controlled session closure upon completion

Ticket Information Included Each alert contains:

Ticket Title: Clear problem description Ticket ID: Unique identifier for tracking Time Remaining: Days/hours until expiration

System Requirements

Infrastructure

  • GLPI server with REST API enabled
  • Running n8n instance
  • Microsoft Teams account with API permissions

Required Credentials

  • GLPI user with application administrator privileges
  • Valid GLPI application token
  • OAuth2 credentials for Microsoft Teams

GLPI User ID Identification

For complete workflow configuration, it's necessary to identify the correct IDs of technical users for proper notification assignment.

User IDs can be obtained by accessing user management in GLPI and observing the ID directly in the browser URL when selecting a specific user.

Path: Administration > Users > [Select User] When clicking on the desired user, you can see the user ID directly in the browser URL (e.g., id=7 for Support Technician 1, id=8 for Support Technician 2).

Configuration

}

Available Customization

  • Alert Period: Modifiable from 2 days to any desired range
  • Execution Schedule: Configurable according to operational needs
  • Recipients: Adaptable to specific team structure

Operational Benefits

For Support Teams

  • Reduction of expired tickets
  • Improved response times
  • Proactive workload management

For Organizations

  • Higher SLA compliance
  • Increased customer satisfaction
  • Optimized technical support resources

Ideal Use Cases

  • IT Service Centers: Incident and request management
  • Technical Support Teams: Critical case tracking
  • Organizations with Strict SLAs: Service agreement compliance
  • IT Departments: Internal ticket monitoring

Scalability

This workflow is designed to:

  • Handle high ticket volumes
  • Adapt to teams of different sizes
  • Integrate with multiple communication channels
  • Expand with additional functionalities

Installation and Deployment

  • Import the JSON workflow into n8n
  • Configure GLPI and Microsoft Teams credentials
  • Update configuration variables
  • Activate the scheduled trigger
  • Perform functionality tests

This workflow represents a robust and scalable solution for proactive ticket management in enterprise environments, significantly improving operational efficiency and service commitment compliance.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - No Operation, do nothing3

Type / Role
n8n-nodes-base.noOp - noOp
Config choices
Version 1

Block 2 - End session1

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 3 - No Operation, do nothing2

Type / Role
n8n-nodes-base.noOp - noOp
Config choices
Version 1

Block 4 - Configuration Variables

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.2

Block 5 - Send a message to Support Technician 1

Type / Role
n8n-nodes-base.microsoftTeams - microsoftTeams
Config choices
Version 2

Block 6 - Send a message to Support Technician 2

Type / Role
n8n-nodes-base.microsoftTeams - microsoftTeams
Config choices
Version 2

Block 7 - Aggregate

Type / Role
n8n-nodes-base.aggregate - aggregate
Config choices
Version 1

Block 8 - Tickets about to expire

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 9 - Get session token

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 10 - Support Technician 1?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 11 - Support Technician 2?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 12 - Schedule Trigger

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 13 - Loop Over Items

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

Block 14 - Split Out

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 15 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

3. Summary Table

Workflow Automated GLPI ticket deadline alerts via Microsoft Teams
Complexity advanced
Nodes 16
Categories Ticket Management, Multimodal AI
Author Luis Hernandez
Published 15 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/7436/7436.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Automated GLPI ticket deadline alerts via Microsoft Teams do?

This n8n workflow provides an automated notification system that monitors tickets in GLPI (Gestionnaire Libre de Parc Informatique) and sends proactive alerts through Microsoft Teams when tickets a...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Ticket Management, Multimodal AI use case.