Description
n8n-nodes-matrix42
This is an n8n community node that integrates with the Matrix42 ESMP Web Services API: tickets, data fragments and objects, data queries, imports, file storage, and a polling trigger.
n8n is a fair-code licensed workflow automation platform.
| Contents | |
| — | — |
| Installation | Install as an n8n community node |
| Operations | All resources, operations and the trigger node |
| Credentials | Webservice Token and Basic auth setup |
| Compatibility | Supported n8n, Node.js and Matrix42 versions |
| Resources | Documentation links |
| Version History | What changed in each release |
| Project | Contributing, code of conduct, security policy, releases |
| Legal & Disclaimer | Trademark and API-usage notes |
Installation
Follow the installation guide in the n8n community nodes documentation.
Operations
Data Fragment
- Get Many (
getAll): Retrieve data fragments matching a search expression, with Return All / Limit paging. - Create (
create): Create a new data fragment in the specified Data Definition. - Update (
update): Update an existing data fragment. - Delete (
delete): Delete a data fragment by its ID. - Create (
create): Create a new object for a Configuration Item. - Get (
get): Retrieve a single object by its ID. - Update (
update): Update an existing object. - Delete (
delete): Delete an object by its ID. - Get Data (
getData): Read the list items of a data query, with paging and an optional structured User Filters body. - Create (
create): Open a new ticket in the Service Desk, with a selectable initial State. - Close (
close): Close an Incident or Service Request. - Transform (
transform): Transform a ticket into another type. - Add Journal Entry (
addJournalEntry): Add a comment to a ticket, optionally with template parameters (Name/Value/Format rows) and a custom creator. - Upload (
upload): Upload a file and attach it to a Configuration Item. - Execute (
execute): Run a predefined import definition to ingest data. - Ticket Created (default): fires for every new Service Desk ticket, with an optional ticket-type filter (e.g. only Incidents).
- Object Created: same for any data definition, watched through a configurable creation-date attribute.
- Object Created or Updated: fires for new and changed records of any class, via the universal
TimeStampcolumn. - n8n: Node API version 1; built and tested against
n8n-workflow2.x. Requires n8n 1.85 or later. Last tested with n8n 2.36.9. - Node.js: v22 or higher.
- Matrix42 ESMP API: Last tested against Matrix42 26.1.
- n8n community nodes documentation
- CONTRIBUTING.md |
| Code of conduct | SECURITY.md |
| Releases | GitHub releases, published to npm from CI |Legal & Disclaimer
This project is an unofficial, community-maintained integration for the Matrix42 ESMP Public API.
It uses only documented, publicly available endpoints as described in the official
This Week's Favorites in automation
More in automation
Popular Tutorials
From Zero to Your First AI Agent in 25 Minutes (No Coding)
n8n Will Change Your Life as a Developer
I Built a Marketing Team with 1 AI Agent
An AI Agent That Builds Teams of AI Agents
Best n8n Community Nodes for Evolution API (WhatsApp)
How to Install n8n Community Nodes (Self-Hosted, Docker, npm and n8n Cloud)
Verified vs Unverified n8n Community Nodes: What’s the Difference?
n8n Community Edition vs Cloud: Which Community Nodes Can You Use?
How to Build and Publish Your Own n8n Community NodeFrom our network
Free decision maker
Yes or No Button
Stuck on a choice? A free one-tap yes or no button that decides for you in a second.
Try the button
Always-on Steam broadcasts
247 Streamer
How to keep a Steam store page broadcast on air around the clock: what Valve allows, the options and real costs.
Keep your page live
Data Object
Data Query
Ticket
Storage
Import
Matrix42 Trigger
The package also ships a Matrix42 Trigger node – a polling trigger that starts workflows when records appear in Matrix42:
An ASQL filter, extra output columns, a per-poll limit and a Fetch Full Object option are available under Additional Fields. Output rows include the object ID as ObjectID, ready for the ticket operations. On activation the trigger starts from the newest existing record, so historic records never fire; “Fetch Test Event” just returns the newest matching record as a sample.
Credentials
> Prerequisite: You must have access to a running Matrix42 instance with appropriate API permissions.
This node supports two authentication methods. Configure these under Workflow -> Credentials.
Matrix42 Webservice Token Auth
1. Server URL – Your Matrix42 server URL (e.g. https://matrix42.example.com).
2. Webservice Token – Your Matrix42 API Token.
3. Ignore SSL Issues (Insecure) – Enable when the server uses a self-signed certificate.
The node exchanges the API Token for a short-lived access token and refreshes it automatically before it expires, then sends it as the Bearer token on every request.
> Self-signed certificates: enable Ignore SSL Issues (Insecure) on the credential, or add the server’s CA certificate to n8n’s trusted store (see https://docs.n8n.io/hosting/configuration/configuration-examples/custom-certificate-authority/).
Matrix42 Basic Auth
1. Server URL – As above.
2. User and Password – Your Matrix42 user credentials.
3. Ignore SSL Issues (Insecure) – As above.
