LogoLogo
  • 🖐️Welcome Aboard!
  • 📖Information
    • What is Autom Mate?
    • What is Autom?
    • Features of Autom Mate
    • Architecture of Autom Mate
  • 🤓Learn Autom Basics
  • 📚Libraries
    • Integration
      • Active Directory
      • AFAS
      • Autom Mate
      • Azure Active Directory
      • Azure DevOps
      • BambooHR
      • ChatGPT
      • ConnectWise
      • Database
      • Desktop Actions
      • EasyVista
      • Email
      • Exchange Web Server
      • Exact Online
      • Excel
      • Freshdesk
      • Freshservice
      • Ftp-Sftp
      • GitLab
      • Google Drive
      • Google Workspace
      • HaloITSM
      • Hubspot
      • Intune
      • Ivanti Service Manager
      • Jenkins
      • Jira Confluence
      • Jira Service Management
      • Jira Software
      • Lakeside
      • Lansweeper
      • Matrix42
      • ME ServiceDesk Plus
      • Microsoft Outlook Calendar
      • Microsoft SharePoint
      • Microsoft Teams
      • My ChatGPT
      • OCR
      • PDF
      • PowerShell
      • Python
      • RESTful Web Service
      • Salesforce
      • ServiceDesk Plus Cloud
      • ServiceNow
      • Slack
      • SolarWinds
      • Stripe
      • TOPdesk
      • Twilio
      • Twitch
      • VMware
      • WhatsApp
      • Word
      • X
      • Xurrent
    • Transform
      • Advanced Actions
      • Array
      • Base64
      • Condition
      • Cryptography
      • CSV
      • Data Table
      • Date
      • File
      • Folder
      • Number
      • Object
      • Repeatable
      • SSH
      • String
      • Text
    • Utility
      • Display Message
      • Grouping
      • Mate DB
      • Mate Drive
      • Time Management
    • Agentic AI (Beta Version)
      • Open AI (Beta Version)
  • 🎇Autom Features
    • Variables
    • Triggers
    • Data Manager
    • Debug
    • Stop Action
    • Function
    • Error Handling and Exception Management
    • Development Mode ( Dev Mode )
    • Business Impact Estimator
  • 🛰️Product Features
    • Dashboard
      • Dashboard
      • Monitoring
      • Alerts
    • Store
      • Autom Store
      • Library Store
    • My Environment
      • Mate Agent
      • Automs
      • Libraries
    • Management
      • User Management
        • Users
        • Roles
        • Forgot Password
      • Vault
      • Webhook & API
      • Alert Management
      • Queue
    • Create Autom
    • Settings
      • Personalization
      • Port & SSL
      • Mail Server
      • License
      • Log Retention
    • Time Zone Management in Autom Mate
  • 💾Installation Setup
    • System Requirements and Ports Configuration
    • Autom Center Installation
      • Autom Center Installation
      • Autom Center Update
    • Mate Agent Installation
      • Mate Agent Installation
      • Mate Agent Update
    • App Installations
      • MS Teams ChatBot Installation
    • Full Chain PFX File Creation Guide
  • 📔Release Notes
    • Amsterdam Edition
      • Amsterdam 3.2.9
      • Amsterdam 3.3.0
    • Boston Edition
      • Boston 4.0.0
      • Boston 4.1.0
      • Boston 4.2.0
      • Boston 4.3.0
        • Boston 4.3.1
        • Boston 4.3.2
        • Boston 4.3.3
        • Boston 4.3.4
        • Boston 4.3.5
        • Boston 4.3.6
        • Boston 4.3.7
      • Boston 4.4.0
        • Boston 4.4.1
      • Boston 4.5.0
  • 🎓Academy
    • 🎓Autom Mate Academy: Basics of Autom Mate
    • 🎓Mastering Automation with Autom Mate: From Workflow Creation
    • 🎓The Ultimate Autom Mate: Teams & Smart Integrations
  • 👔Autom Store & Use Cases
    • 🛒Autom Store Use Cases
    • 🖥️Use Cases
      • How to Create Bidirectional Connection Between JIRA and Xurrent to Open Requests or Tickets
      • Employee Onboarding Process Automation Using Autom Mate
  • ❓FAQ
    • ⚙️General Functionality
    • 🧩Integration Capabilities
    • Data Management and Validation
    • ⁉️Error Handling and Workflow Management
    • Automation Use Cases
    • Connectors and Triggers
    • Custom GPT Models
Powered by GitBook
On this page
  • Introduction
  • What is Matrix42?
  • Automate Integration with Matrix42
  • Using the Integration
  • How to Use Actions
  • View a Ticket
  • View All Users
  • View Attachments of a Ticket
  • View Data of a Widget

Was this helpful?

  1. Libraries
  2. Integration

Matrix42

PreviousLansweeperNextME ServiceDesk Plus

Last updated 2 days ago

Was this helpful?

Introduction

This document provides comprehensive and up-to-date instructions for integrating Matrix42 into Autom Mate. The integration allows users to interact with Matrix42's service management platform, enabling operations like viewing tickets, managing users, and retrieving system data directly within Autom Mate workflows.

Through this integration, Autom Mate users can automate processes such as ticket management, user updates, and system health monitoring, all without needing to write additional code.


What is Matrix42?

Matrix42 is a leading IT service management (ITSM) platform, designed to streamline and automate IT operations. It provides tools for managing service requests, incidents, changes, and asset management, as well as enabling IT teams to provide high-quality service delivery.

Matrix42 is used in enterprises to optimize IT processes, improve productivity, and enhance user satisfaction. With this integration, Autom Mate users can easily access and manipulate Matrix42 data within their workflows.


Automate Integration with Matrix42

Under the Integration Library, Autom Mate provides several built-in actions that allow seamless interaction with Matrix42, including View Tickets, View Users, and View Attachments.

🔐 Prerequisite

Before using this integration, ensure you have the appropriate credentials stored securely in Autom Mate:

  1. Navigate to the page in Autom Mate.

  2. Create a new Vault item containing your Matrix42 API Key or connection credentials.

  3. Use this credential in the App Credential field within the action configuration.

This ensures secure communication and credential management across your automation processes.


Using the Integration

To use the Matrix42 integration in Autom Mate:

  1. Select the Matrix42 Action: Choose from pre-built actions like "View a Ticket", "View All Users", or "View Attachments" from the Integration Library.

  2. Fill in Required Fields: Provide necessary inputs like Ticket ID, Widget ID, or Application ID, depending on the action being used.

  3. Assign Variables: For each action, you will be prompted to assign output variables (e.g., ticket data, user details, etc.) to store the results.

  4. Use Variables in Subsequent Actions: After executing the action, you can use the assigned output variables in downstream actions, such as sending notifications, updating records, or making decisions based on ticket or user data.


How to Use Actions

View a Ticket

Description and Purpose

The Matrix42 - View a Ticket action allows Autom Mate users to retrieve details about a specific ticket in the Matrix42 system. This action is essential for automation processes that involve retrieving ticket information based on a unique Ticket Number, such as ticket status, priority, assignee, or other details.

By providing the Ticket Number, users can fetch the full ticket data from Matrix42, which can then be used in further processing or decision-making workflows.


Usage Instructions

1

Select App Credential

App Credential (Required): Select the credential that connects Autom Mate to Matrix42. Example:

Matrix42

This credential ensures secure communication between Autom Mate and Matrix42, allowing you to view tickets.

2

Provide Ticket Number

Ticket Number (Required): Enter the unique identifier of the Matrix42 ticket you want to view. Example:

TICKET-12345

This ticket number will be used to query the Matrix42 system and retrieve the corresponding ticket details.

3

Assign Output Variables

  • Output Body (Required): Select an object-type variable (e.g., ViewaTicket_output_d1469266fbad4b959bdf1154c0955aed) to store the full details of the ticket.

  • Output Header (Required): Select another object-type variable (e.g., ViewaTicket_output_header_d1469266fbad4b959bdf1154c0955aed) to store metadata about the ticket query, such as response status or additional information.

4

Execute and Review

Run the action. After execution, the selected variables will store the ticket details and metadata. You can use these variables to further process the ticket information, such as in conditional logic or for reporting.


Inputs

Field
Description

App Credential

Select the credential for connecting to Matrix42 (e.g., Matrix42).

Ticket Number

Enter the unique ticket number for the Matrix42 ticket (e.g., TICKET-12345).


Outputs

Field
Description

Output Body

Contains the full ticket data from Matrix42, including status, priority, assignee, etc.

Output Header

Contains metadata about the response, such as status code, message, or other relevant details.


Example

  • App Credential:

Matrix42
  • Ticket Number:

TICKET-12345
  • Output Body: The output variable ViewaTicket_output_d1469266fbad4b959bdf1154c0955aed will contain detailed information about the specified ticket, such as ticket status, assigned team, description, and more.

  • Output Header: The output variable ViewaTicket_output_header_d1469266fbad4b959bdf1154c0955aed will contain metadata about the response, such as the API status or error messages.


View All Users

Description and Purpose

The Matrix42 - View All Users action allows Autom Mate users to retrieve a list of all users in the Matrix42 system. This action is helpful for use cases where user information needs to be fetched for reporting, user management, or creating a list of all users within the system. The action does not require any input data, and the output consists of user data retrieved from Matrix42.


Usage Instructions

1

Select App Credential

App Credential (Required): Select the credential that connects Autom Mate to Matrix42. Example:

Matrix42

This credential ensures secure access to the Matrix42 system for retrieving the user data.

2

Assign Output Variables

  • Output Body (Required): Select an object-type variable (e.g., ViewAllUsers_output_c092ffba813347c9809c3aaebb36fadc) to store the full details of all users retrieved from Matrix42. This variable will hold the list of all users.

  • Output Header (Required): Select another object-type variable (e.g., ViewAllUsers_output_header_c092ffba813347c9809c3aaebb36fadc) to store metadata about the response, such as status, message, or additional information.

3

Execute and Review

Run the action. After execution, the output variables will contain the user data and metadata retrieved from Matrix42. These variables can be used for further processing, such as filtering users, performing user-specific actions, or displaying data in a UI.


Inputs

This action does not require any input data. It fetches all user data directly from the Matrix42 system based on the provided credential.


Outputs

Field
Description

Output Body

Contains the full list of all users in the Matrix42 system. This is typically an object or array containing user details such as user ID, name, role, etc.

Output Header

Contains metadata about the response, such as status, message, or other relevant details.


Example

  • App Credential:

Matrix42
  • Output Body: The output variable ViewAllUsers_output_c092ffba813347c9809c3aaebb36fadc will contain detailed information about all users in Matrix42, including usernames, roles, and other associated details.

  • Output Header: The output variable ViewAllUsers_output_header_c092ffba813347c9809c3aaebb36fadc will contain metadata such as the status of the request, the number of users retrieved, or any error messages if applicable.


View Attachments of a Ticket

Description and Purpose

The Matrix42 - View Attachments of a Ticket action allows Autom Mate users to retrieve all attachments associated with a specific ticket in the Matrix42 system. This action is essential for automation scenarios where ticket-related attachments need to be processed, saved, or reviewed.

By specifying the Ticket ID and defining the output type, users can extract the attachment details for further actions, such as saving them to Mate Drive or processing them dynamically within workflows.


Usage Instructions

1

Select App Credential

App Credential (Required): Select the credential that connects Autom Mate to Matrix42. Example:

Matrix42

This credential ensures secure access to the Matrix42 system, allowing for the retrieval of ticket attachments.

2

Provide Ticket ID

Ticket ID (Required): Enter the unique identifier of the Matrix42 ticket whose attachments you wish to view. Example:

TICKET-12345

This ID will be used to query Matrix42 and retrieve the attachments associated with the specified ticket.

3

Choose Output Type

Output Type (Required): Select the desired format for the attachment data:

  • Base64: The attachments will be returned in base64 encoding, which is useful if the files need to be saved or transmitted as binary data.

  • Folder Path: Select this option if you want to specify the destination folder where the attachments should be saved in Mate Drive. You need to provide a folder path.

The Folder Path option requires a valid destination path to save the file in MateDrive. Ensure that the destination folder exists or will be created during the process. You can use Data Store paths like mate:/ or mate:/foldername.

4

Assign Output Variables

  • Output Body (Required): Select an array-type variable (e.g., ViewAttachmentsofaTicket_output_349c66a9359c4487b38ed9e0daacc783) to store the list of attachments retrieved from the ticket.

  • Output Header (Required): Select an object-type variable (e.g.,ViewAttachmentsofaTicket_output_header_349c66a9359c4487b38ed9e0daacc783) to store metadata about the response, such as status, message, or additional information.

5

Execute and Review

Run the action. After execution, the output variables will contain the attachment details for the specified ticket, which can then be used in subsequent actions, such as saving to Mate Drive or logging.


Inputs

Field
Description

App Credential

Select the credential for connecting to Matrix42 (e.g., Matrix42).

Ticket ID

Enter the ticket ID of the Matrix42 ticket to retrieve attachments from (e.g., TICKET-12345).

Output Type

Choose the format for the output. Options include Base64 or Folder Path.

Folder Path

Specify the folder path to save the attachments in Mate Drive (optional).


Outputs

Field
Description

Output Body

An array containing the list of attachments for the specified ticket. This could include file names, types, and other metadata.

Output Header

Contains metadata about the response, such as status, message, or other relevant details.


Example

  • App Credential:

Matrix42
  • Ticket ID:

TICKET-12345
  • Output Type:

Base64
  • Folder Path:

mate:/ticket_attachments
  • Output Body (ViewAttachmentsofaTicket_output_349c66a9359c4487b38ed9e0daacc783): The output will contain an array of attachment details like the file names, sizes, and other relevant data.

  • Output Header (ViewAttachmentsofaTicket_output_header_349c66a9359c4487b38ed9e0daacc783): The output will contain metadata such as the status of the request, the number of attachments retrieved, or any error messages if applicable.


View Data of a Widget

Description and Purpose

The Matrix42 - View Data of a Widget action allows Autom Mate users to retrieve the data associated with a specific widget within the Matrix42 platform. This action is useful for automating the process of fetching widget data based on a given Application ID and Widget ID, allowing users to process or analyze widget-specific information dynamically within their workflows.

By providing the Application ID and Widget ID, users can access detailed data related to the widget, such as configuration settings, performance metrics, or status information, and integrate it into their automation processes.


Usage Instructions

1

Select App Credential

App Credential (Required): Select the credential that connects Autom Mate to Matrix42. Example:

Matrix42

This credential ensures secure communication between Autom Mate and Matrix42, allowing access to the widget data.

2

Provide Application ID

Application ID (Required): Enter the unique identifier for the application whose widget data you wish to view. Example:

APP-56789

This ID will be used to query Matrix42 for the widget data related to the specified application.

3

Provide Widget ID

Widget ID (Required): Enter the unique identifier of the widget within the application for which data is to be retrieved. Example:

WIDGET-12345

This ID will be used to retrieve the data for the specific widget.

4

Assign Output Variables

  • Output Body (Required): Select an array-type variable (e.g., ViewDataofaWidget_output_8bea9a4af0e54544a7b4d694032f9e2e) to store the data retrieved for the widget.

  • Output Header (Required): Select an object-type variable (e.g., ViewDataofaWidget_output_header_8bea9a4af0e54544a7b4d694032f9e2e) to store metadata about the response, such as status, message, or other relevant information.

5

Execute and Review

Run the action. After execution, the output variables will contain the widget data and metadata, which can be used for further processing, reporting, or decision-making within the workflow.


Inputs

Field
Description

App Credential

Select the credential for connecting to Matrix42 (e.g., Matrix42).

Application ID

Enter the unique Application ID to retrieve data for (e.g., APP-56789).

Widget ID

Enter the unique Widget ID to retrieve data for (e.g., WIDGET-12345).

Output Body

Select an array-type variable to store the widget data.

Output Header

Select an object-type variable to store metadata about the response.


Outputs

Field
Description

Output Body

An array containing the data of the specified widget, such as its configuration, metrics, or status.

Output Header

Metadata about the response, including status, message, or other relevant details.


Example

  • App Credential:

Matrix42
  • Application ID:

APP-56789
  • Widget ID:

WIDGET-12345
  • Output Body (ViewDataofaWidget_output_8bea9a4af0e54544a7b4d694032f9e2e): The output variable will contain an array of widget data, such as configuration settings, performance metrics, or widget-specific information.

  • Output Header (ViewDataofaWidget_output_header_8bea9a4af0e54544a7b4d694032f9e2e): The output variable will contain metadata such as the response status, success message, or error details.

📚
Vault