RUNDECK n8n INTEGRATION: AUTOMATE RUNDECK WITH N8N
Looking to automate Rundeck with n8n? You're in the right place. The native Rundeck n8n integration allows you to connect your runbook automation platform directly to your n8n workflows, enabling seamless job execution and metadata retrieval without manual intervention.
With this integration, you get access to 2 powerful actions that let you trigger Rundeck jobs programmatically and fetch job metadata on demand. Whether you're managing infrastructure deployments, running scheduled maintenance tasks, or orchestrating complex operational workflows, connecting Rundeck to n8n opens up endless automation possibilities.
In this guide, you'll discover exactly how to set up the connection, explore each available action in detail, and learn practical use cases to fully leverage the Rundeck n8n integration in your automation stack.
Need help automating Rundeck with n8n?
Our team will get back to you in minutes.
Why automate Rundeck with n8n?
The Rundeck n8n integration gives you access to 2 actions that transform how you manage operational workflows. Specifically, you can execute Rundeck jobs directly from n8n workflows and retrieve detailed job metadata—all without touching the Rundeck interface manually.
Significant time savings stand out as the primary benefit. Instead of logging into Rundeck every time you need to trigger a deployment or maintenance job, you can chain job executions with other tools in your stack. Imagine a scenario where a monitoring alert in Datadog automatically triggers a remediation job in Rundeck, then posts the result to Slack—all hands-free. Improved responsiveness becomes reality when your infrastructure can self-heal or scale based on real-time events captured by n8n.
Zero oversight is another game-changer. By connecting Rundeck to n8n, you eliminate the risk of forgetting to run critical jobs. Every scheduled task, every conditional execution, every post-incident procedure can be automated and logged. Seamless integration with n8n's 400+ app connectors means Rundeck becomes part of a larger ecosystem: trigger jobs from GitHub webhooks, sync job results to Airtable, notify teams via Microsoft Teams, or update tickets in Jira automatically.
Concrete use cases include: automated server provisioning after a new project is created in your PM tool, instant rollback execution when error thresholds are exceeded, scheduled compliance checks that feed results into reporting dashboards, and CI/CD pipeline orchestration where Rundeck handles the deployment phase.
How to connect Rundeck to n8n?
! 1 stepHow to connect Rundeck to n8n?
- 01
Add the node
The Rundeck n8n integration uses API Token authentication to establish a secure connection between your Rundeck instance and n8n workflows.Basic configuration:Generate your Rundeck API Token: Log into your Rundeck instance, navigate to your user profile settings, and create a new API token with appropriate permissions for the jobs you want to automate.Access n8n credentials: In your n8n editor, go to Credentials > Add Credential and search for "Rundeck".Configure the Rundeck account: Enter your Rundeck server URL (e.g., https://rundeck.yourcompany.com) and paste your API token in the designated field.Test the connection: Click the test button to verify n8n can successfully communicate with your Rundeck instance before saving.Save and use: Once validated, your Rundeck credential is ready to be selected in any Rundeck node within your workflows.
TIP💡 TIP: Create a dedicated service account in Rundeck specifically for n8n integrations rather than using personal credentials. This way, you maintain audit trails, can revoke access independently, and avoid disruptions if a team member leaves. Also, scope the API token permissions to only the projects and jobs that n8n needs to access—principle of least privilege keeps your infrastructure secure. For more advanced troubleshooting, check our n8n troubleshooting guide.- 01
Need help automating Rundeck with n8n?
Our team will get back to you in minutes.
Rundeck actions available in n8n
01 Action 01Get Metadata
The Get Metadata action allows you to retrieve detailed information about a specific Rundeck job directly within your n8n workflow. This is incredibly useful when you need to validate job configurations, check job status before execution, or dynamically build workflows based on job properties.
Key parameters:
- Credential to connect with: A required dropdown where you select your configured Rundeck account. This establishes the authenticated connection to your Rundeck instance.
- Resource: A required dropdown set to "Job", indicating this action operates on Rundeck job entities.
- Operation: A required dropdown set to "Get Metadata", specifying that you want to fetch job details rather than execute.
- Job ID: A required text field where you enter the unique identifier of the Rundeck job whose metadata you want to retrieve. You can find this ID in the Rundeck job URL or job definition.
Use cases:
- Fetch job configuration before triggering execution to validate parameters dynamically
- Build dashboards that display real-time job descriptions and schedules pulled from Rundeck
- Create conditional workflows that check job metadata (like last run status) before deciding next steps
- Audit automation by logging job definitions alongside execution results
This action is perfect when you need visibility into your Rundeck jobs without leaving your n8n workflow context.
02 Action 02Execute Job
The Execute Job action is the powerhouse of the Rundeck n8n integration—it lets you trigger any Rundeck job programmatically from your automation workflows. This transforms Rundeck from a standalone tool into a fully integrated component of your event-driven infrastructure.
Key parameters:
- Credential to connect with: A required dropdown to select your Rundeck account credential, authenticating the API call.
- Resource: A required dropdown set to "Job", confirming you're working with job-type operations.
- Operation: A required dropdown set to "Execute", meaning this action will actually run the specified job.
- Job ID: A required text field for the unique identifier of the Rundeck job you want to execute. This is the core parameter—get this from your Rundeck job URL.
- Arguments: An optional section where you can add key-value pairs to pass dynamic parameters to the job at runtime. Click "Add Argument" to include variables like environment names, target servers, or version numbers.
- Filter: An optional text field that lets you apply node filters, restricting which nodes the job runs on based on attributes like hostname, tags, or custom properties.
Use cases:
- Trigger deployment jobs automatically when a pull request is merged in GitHub
- Execute remediation runbooks when monitoring tools like Grafana detect anomalies
- Run scheduled maintenance scripts orchestrated alongside notifications and logging in n8n
- Chain multiple Rundeck jobs together with conditional logic based on previous job outputs
This action shines in scenarios where you need Rundeck's operational power triggered by external events or as part of larger multi-step automation workflows.
Build your first workflow with our team
Drop your email and we'll send you the catalog of automations you can ship today.
- Free n8n & Make scenarios to import
- Step-by-step setup docs
- Live cohort + community support
Frequently asked questions
Is the Rundeck n8n integration free to use?
Yes, the Rundeck integration is included natively in n8n at no additional cost—whether you're using the self-hosted open-source version or n8n Cloud. You simply need an active Rundeck instance (Community or Enterprise) with API access enabled. There are no per-action fees or usage limits imposed by the n8n connector itself. Your only considerations are the licensing model of your Rundeck installation and your n8n hosting plan's execution limits if using the cloud version.Can I pass dynamic arguments to Rundeck jobs from n8n?
Absolutely. The Execute Job action includes an "Arguments" parameter where you can add key-value pairs dynamically. This means you can pull values from previous nodes in your workflow—like form inputs, webhook payloads, or database queries—and pass them directly to your Rundeck job. For example, you could capture a server hostname from a Discord command or Slack and use it as an argument in a targeted deployment job. This makes your automation highly flexible and context-aware.How long does it take to set up the Rundeck n8n integration?
Most users complete the setup in under 5 minutes. The process involves generating an API token in Rundeck (about 1 minute), adding the credential in n8n (1-2 minutes), and testing the connection. If you already have your Rundeck Job IDs handy, you can have a working automation workflow executing jobs within 10-15 minutes total. The interface is straightforward with dropdown selections and clear parameter labels—no complex configuration files or code required. For more advanced automation scenarios, explore our downloadable automation catalog and official n8n Rundeck documentation.
