# xMatters integrations: incidents and people

> Create an incident, create a person and create a device in xMatters. Connect xMatters to the rest of your IT stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/xmatters-integrations/
**Categories:** IT
**Connects through:** HTTP Connector

## Overview

xMatters is an incident management and on-call alerting service that notifies the right responders, runs incident workflows and tracks on-call schedules for IT and DevOps teams. Tray.ai connects to xMatters through the HTTP Connector, so your workflows can call the xMatters API alongside the rest of your stack.

## Use cases

### Events

Read, create, and update events in xMatters from any Tray.ai workflow. The xMatters API covers calls such as get events and trigger an event.

- Get events
- Trigger an event
- Add a comment to an event

### Incidents

Read and create incidents in xMatters from any Tray.ai workflow. The xMatters API covers calls such as get incidents and create an incident.

- Get incidents
- Create an incident
- Modify an incident

### People

Read and create people in xMatters from any Tray.ai workflow. The xMatters API covers calls such as get people and create a person.

- Get people
- Create a person
- Modify a person

### Groups

Read, create, and delete groups in xMatters from any Tray.ai workflow. The xMatters API covers calls such as get groups and create a group.

- Get groups
- Create a group
- Modify a group

### On-call

Read on-call in xMatters from any Tray.ai workflow. The xMatters API covers calls such as get who is on call and get on-call summary.

- Get who is on call
- Get on-call summary

### Devices

Read, create, and delete devices in xMatters from any Tray.ai workflow. The xMatters API covers calls such as get devices and create a device.

- Get devices
- Create a device
- Modify a device

## Challenges Tray.ai solves

### Keeping xMatters credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store xMatters credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the xMatters API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the xMatters API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to xMatters?

Yes. Tray.ai connects to xMatters through the HTTP Connector, which calls the xMatters API directly. Any call the xMatters API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with xMatters?

The xMatters API uses basic authentication and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated xMatters connector?

xMatters runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated xMatters connector from the xMatters API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/