# Rundeck integrations: jobs and executions

> Import jobs, create a project and run an adhoc command in Rundeck, and start a workflow when Rundeck sends “Job started”.

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

## Overview

Rundeck is a runbook automation tool from PagerDuty for defining operational jobs and running scripts and commands across servers, on demand or on a schedule. Tray.ai connects to Rundeck through the HTTP Connector, so your workflows can call the Rundeck API alongside the rest of your stack.

## Use cases

### Jobs

Read, create, delete, and manage jobs in Rundeck from any Tray.ai workflow. The Rundeck API covers calls such as list jobs and run a job.

- List jobs
- Run a job
- Retry a job

### Executions

Read, delete, and manage executions in Rundeck from any Tray.ai workflow. The Rundeck API covers calls such as list running executions and get execution info.

- List running executions
- Get execution info
- Get execution output

### Projects

Read, create, and delete projects in Rundeck from any Tray.ai workflow. The Rundeck API covers calls such as list projects and create a project.

- List projects
- Create a project
- Get project info

### Adhoc commands

Create adhoc commands in Rundeck from any Tray.ai workflow. The Rundeck API covers calls such as run an adhoc command and run an adhoc script.

- Run an adhoc command
- Run an adhoc script

### Key storage

Read, create, and delete key storage in Rundeck from any Tray.ai workflow. The Rundeck API covers calls such as upload keys and list keys.

- Upload keys
- List keys
- Delete keys

### Webhooks

Read, create, update, and delete webhooks in Rundeck from any Tray.ai workflow. The Rundeck API covers calls such as list project webhooks and add a webhook.

- List project webhooks
- Add a webhook
- Update a webhook

## Challenges Tray.ai solves

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

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

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

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

### Can I get a dedicated Rundeck connector?

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