OtherReal-timeUpdated May 2026

Rundeck

Rundeck job automation runbook

Rundeck is the operations job-scheduling and runbook-automation platform — used by ops teams to centralise automation, give controlled access to scripted tasks, and audit runs. Tiny Command exposes one action, no triggers: List Items (recent jobs, runs, or projects depending on parameters). The connection takes the Rundeck instance URL plus an API token. For workflows that need to invoke Rundeck jobs from external triggers (Slack command fires a Rundeck deploy job, monitoring alert triggers a Rundeck remediation runbook), the job-execution endpoint (HTTP action) is the integration. Rundeck's value over plain cron + shell scripts is the access control, audit trail, and UI for non-engineers to safely run pre-defined operations tasks.

Connect Rundeck

0triggers

1action

≈ 2 minto set up

Freetier · no card

Actions

Do anything Rundeck can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
List Rundeck Items	Returns recent jobs, executions, or projects depending on parameters. For "show me last 10 runs" inventory or audit workflows.	0 fields	View →

Recipes

Pre-built Rundeck workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Rundeck → Slack alerts

AI-triage every Rundeck event, ping the right channel only when it matters.

Rundeck → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Rundeck → Notion database

Turn Rundeck into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Rundeck once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Rundeck field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Rundeck integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Rundeck to Tiny Command?

Open the Tiny Command workflow builder, drop in a Rundeck node, and click Connect. Authorize Rundeck once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Rundeck triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Rundeck today. Use Tiny Command's universal Webhook or Schedule trigger to start Rundeck workflows, then run any Rundeck action you need.

What Rundeck actions can I run from a workflow?

1 Rundeck action are available out of the box, covering other operations like "List Rundeck Items". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Rundeck integration real-time?

Rundeck actions execute synchronously inside your workflow. Tiny Command waits for Rundeck's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Rundeck with Tiny Command?

No. Every Rundeck trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Rundeck API endpoint directly.

How much does the Rundeck integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Rundeck integration itself has no per-app surcharge.