Can Cockpit trigger actions in Rundeck, and Rundeck in Cockpit?

Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it.

Do I need to write code to integrate Cockpit and Rundeck?

No. Cockpit-to-Rundeck automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.

Cockpit + Rundeck Integration

Keep Cockpit and Rundeck aligned: when developer tools events happen in one, update the other automatically.

Example: when Rundeck's "Watch Executions" fires, WEXTL can "Create Collection" in Cockpit. Cockpit has 11 actions (including Create Collection, Create Entry, and Delete Entry); Rundeck has 141 actions (including Abort Execution, Browse Job Groups, and Bulk Disable Executions).

Explore Documentation

GDPR
Data Encryption
2FA
Local Data Region

Rundeck triggersCockpit actions

Rundeck workflow triggers

Cockpit workflow actions

Frequently asked questions

Common questions about connecting Cockpit and Rundeck.

Connect your Cockpit and Rundeck accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.

CockpitBrowse all Cockpit triggers, actions, and integrations.

RundeckBrowse all Rundeck triggers, actions, and integrations.

Cockpit + Rundeck Integration

Frequently asked questions

How do I connect Cockpit and Rundeck?

What can I automate between Cockpit and Rundeck?

Can Cockpit trigger actions in Rundeck, and Rundeck in Cockpit?

Do I need to write code to integrate Cockpit and Rundeck?

Explore Cockpit and Rundeck, or get started

Cockpit + Rundeck Integration

Frequently asked questions

How do I connect Cockpit and Rundeck?

What can I automate between Cockpit and Rundeck?

Can Cockpit trigger actions in Rundeck, and Rundeck in Cockpit?

Do I need to write code to integrate Cockpit and Rundeck?

Explore Cockpit and Rundeck, or get started