Matrix42 Node for n8n

What it does

The node talks to the Matrix42 ESMP web services API and covers the tasks that come up most often in service desk automation:

• Tickets: create a ticket with a chosen state, close incidents and service requests, transform a ticket into another type, add journal entries with template parameters
• Data fragments: search, create, update and delete fragments of any data definition, with paging for large results
• Data objects: create, read, update and delete objects of a configuration item
• Data queries: read the list items of a data query, with paging and user filters
• Storage: upload a file and attach it to a configuration item
• Imports: run a predefined import definition

Starting workflows from Matrix42

The package also contains a Matrix42 Trigger. It checks Matrix42 at an interval and starts a workflow when something new appears:

• when a ticket is created, optionally only for one ticket type such as incidents
• when an object of any data definition is created
• when an object is created or changed

An ASQL filter narrows down what counts. The trigger starts from the newest existing record, so switching it on never replays old tickets. Every result carries the object ID, ready for the ticket operations of the node.

Setting it up

1. The node is verified by n8n. Open the nodes panel in n8n, search for Matrix42 and install it; this works on n8n Cloud as well. On a self-hosted n8n you can also install n8n-nodes-matrix42 under Settings and then Community Nodes or with npm.
2. Create a credential. The recommended way is a Matrix42 API token: the node exchanges it for a short-lived access token and renews it before it expires. User name and password work as well.
3. If your Matrix42 server uses a self-signed certificate, either add its certificate authority to n8n or switch on "Ignore SSL Issues" for that credential.

Compatibility

• n8n 1.85 or later, last tested with n8n 2.36
• Node.js 22 or later
• Matrix42 ESMP API, last tested with Matrix42 26.1

Good to know

The node uses only the documented public API of Matrix42. It is a community project and not affiliated with or endorsed by Matrix42. Questions and bug reports go to the issues of the repository on GitHub.

What the node can do in a real service desk is described in our post Matrix42 Integration for n8n. If you want AI assistants to work with the same Matrix42 instance, have a look at the Matrix42 MCP Server.