# Action1 integrations: endpoints

> Create an endpoint group and create an automation schedule in Action1. Connect Action1 to the rest of your IT stack with Tray.ai.

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

## Overview

Action1 is a cloud platform for patching and managing Windows, macOS and Linux endpoints, with vulnerability remediation, software deployment, remote access and asset inventory. Tray.ai connects to Action1 through the HTTP Connector, so your workflows can call the Action1 API alongside the rest of your stack.

## Use cases

### Endpoints

Read, update, and delete endpoints in Action1 from any Tray.ai workflow. The Action1 API covers calls such as list endpoints and get an endpoint.

- List endpoints
- Get an endpoint
- Rename an endpoint

### Endpoint groups

Read, create, update, and delete endpoint groups in Action1 from any Tray.ai workflow. The Action1 API covers calls such as list endpoint groups and create an endpoint group.

- List endpoint groups
- Create an endpoint group
- Update an endpoint group

### Updates

Read and manage updates in Action1 from any Tray.ai workflow. The Action1 API covers calls such as list missing updates and deploy updates.

- List missing updates
- Deploy updates
- List endpoints missing an update

### Vulnerabilities

Read vulnerabilities in Action1 from any Tray.ai workflow. The Action1 API covers calls such as list vulnerable software and list affected endpoints.

- List vulnerable software
- List affected endpoints
- List remediation actions

### Automations

Read, create, update, and delete automations in Action1 from any Tray.ai workflow. The Action1 API covers calls such as list automation schedules and create an automation schedule.

- List automation schedules
- Create an automation schedule
- Delete an automation schedule

### Users

Read, create, and delete users in Action1 from any Tray.ai workflow. The Action1 API covers calls such as list users and create a user.

- List users
- Create a user
- Get a user

## Challenges Tray.ai solves

### Keeping Action1 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 Action1 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 Action1 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 Action1 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 Action1?

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

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

The Action1 API uses 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 Action1 connector?

Action1 runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Action1 connector from the Action1 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/