Skip to content
Rundeck logo

Connectors / IT · HTTP Connector

Automate Rundeck with Tray.ai

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

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.

See all connectors

What can you do with Rundeck on Tray.ai?

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.

  • When Rundeck sends “Job failed”, open an incident and page the on-call engineer through your incident tool.
  • Run a job in Rundeck to restart a service when your monitoring tool fires a known alert.
  • When Rundeck sends “Average duration exceeded”, warn the operations team in your team chat before the job holds up others.
  • Get execution output after each run and attach it to the change ticket in your IT service desk.
Connects through
HTTP Connector
Authentication
An API key in a request header or an API key in the query string

Set it up

Connect Rundeck to Tray.ai

Each step uses Rundeck's own API details, from its documentation.

Step 1

Save Rundeck's API key

Save the key as a Tray.ai authentication. The HTTP Client puts it in the request header, read from $.auth. The key stays out of the workflow and out of the logs.

Step 2

Import a request from Rundeck's docs

Add an HTTP Client step and paste a cURL example from Rundeck's API docs. Tray.ai fills in the method, URL, headers, and query.

Step 3

Start with “List jobs”

It's one of 25 documented actions, under Jobs. The response comes back as data the next step can map into your other apps.

Step 4

Start workflows from Rundeck events

Give Rundeck the URL of a Tray.ai webhook trigger. “Job started” can then start a workflow, and so can 4 other events.

What the Rundeck API covers

6 resources and 25 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.

Jobs

  • List jobs
  • Run a job
  • Retry a job
  • Import jobs
  • Export jobs
  • Delete a job

Executions

  • List running executions
  • Get execution info
  • Get execution output
  • Abort an execution
  • Delete an execution

Projects

  • List projects
  • Create a project
  • Get project info
  • Delete a project
  • Export a project archive

Adhoc commands

  • Run an adhoc command
  • Run an adhoc script

Key storage

  • Upload keys
  • List keys
  • Delete keys

Webhooks

  • List project webhooks
  • Add a webhook
  • Update a webhook
  • Delete a webhook

Events Rundeck can send to a Tray.ai webhook trigger

  • Job started
  • Job succeeded
  • Job failed
  • Job failed with retry
  • Average duration exceeded

Checked against Rundeck's own documentation on 2026-10-22

docs.rundeck.com/docs/api

Frequently asked questions

What can a Tray.ai workflow do in Rundeck?

+

The Rundeck API documents 25 actions across 6 resources (Jobs, Executions, Projects, Adhoc commands, Key storage, Webhooks). For example: List jobs; List running executions; List projects. A workflow can make any documented call through the HTTP Connector.

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.

Which Rundeck events can start a Tray.ai workflow?

+

Rundeck sends 5 events to a webhook URL, for example: Job started; Job succeeded; Job failed; Job failed with retry; Average duration exceeded. A Tray.ai webhook trigger receives them and starts a workflow.

See Rundeck working against your stack.

We'll walk through a tailored demo with your systems plugged in.

Great — a couple more details

This helps us connect you with the right person. Optional, and you can skip it.