# Puppet integrations: orchestrator commands

> Run Puppet on nodes, create a node group and generate an authentication token in Puppet. Connect Puppet to the rest of your IT stack with Tray.ai.

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

## Overview

Puppet is infrastructure automation software from Perforce that keeps servers in a defined configuration and runs on-demand tasks, plans, and patching across nodes. Tray.ai connects to Puppet through the HTTP Connector, so your workflows can call the Puppet API alongside the rest of your stack.

## Use cases

### Orchestrator commands

Create and update orchestrator commands in Puppet from any Tray.ai workflow. The Puppet API covers calls such as run Puppet on nodes and run a task.

- Run Puppet on nodes
- Run a task
- Run a plan

### Jobs

Read jobs in Puppet from any Tray.ai workflow. The Puppet API covers calls such as list jobs and get a job.

- List jobs
- Get a job
- List job nodes

### Node groups

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

- Create a node group
- Get a node group
- Update a node group

### RBAC users and tokens

Read, create, and update rbac users and tokens in Puppet from any Tray.ai workflow. The Puppet API covers calls such as generate an authentication token and revoke an authentication token.

- Generate an authentication token
- Revoke an authentication token
- List users

## Challenges Tray.ai solves

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

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

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

The Puppet API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Puppet connector?

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