STEP 1
Connect Cortex and Rundeck
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Cortex and Rundeck Integration
Keep Cortex and Rundeck in sync by integrating their events and actions. When developer tools events happen in Cortex, update the Rundeck automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Cortex and Rundeck
Detailed info you need to know about Cortex and Rundeck integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Cortex to Rundeck
Set up your Cortex and Rundeck integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Cortex and Rundeck nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Cortex and Rundeck. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Cortex and Rundeck work in WEXTL?
WEXTL exposes actions and triggers for Cortex and Rundeck that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Rundeck triggersCortex actions
Rundeck modules
- Abort ExecutionAborts execution.
- Browse Job GroupsBrowses job groups.
- Bulk Disable ExecutionsPerforms the disable Executions operation.
- Bulk Disable SchedulesPerforms the disable Schedules operation.
- Bulk Enable ExecutionsPerforms the enable Executions operation.
- Bulk Enable SchedulesPerforms the enable Schedules operation.
- Create ProjectCreates a project.
- Create Project ACLCreates a project acl.
- Create System ACLCreates a system acl.
- Create TokenCreates a token.
- Create User TokenCreates an user token.
- Create WebhookCreates a webhook.
- Create/Import JobsCreates a /import jobs.
- Delete All Job ExecutionsDeletes all job executions.
- Delete Config KeyDeletes config key.
- Delete ExecutionDeletes execution.
- Delete Executions BulkDeletes executions bulk.
- Delete JobDeletes job.
- Delete Job Executions HistoryDeletes job executions history.
- Delete Jobs BulkDeletes jobs bulk.
- Delete Jobs FileDeletes jobs file.
- Delete KeyDeletes key.
- Delete MOTDDeletes motd.
- Delete Named Project ACLDeletes named project acl.
- Delete Named System ACLDeletes named system acl.
- Delete ProjectDeletes project.
- Delete Project ACLDeletes project acl.
- Delete ReadmeDeletes readme.
- Delete System ACLDeletes system acl.
- Delete TokenDeletes token.
- Delete WebhookDeletes webhook.
- Disable Job ExecutionDisables job execution.
- Disable Job ScheduleDisables job schedule.
- Disable System ExecutionsDisables system executions.
- Enable Job ExecutionEnables job execution.
- Enable Job ScheduleEnables job schedule.
- Enable System ExecutionsEnables system executions.
- Execute Bulk Execution DeleteExecutes bulk execution delete.
- Execute Bulk Job DeleteExecutes bulk job delete.
- Export JobsRetrieves export jobs.
- Export ProjectExports project.
- Export Project AsyncExports project async.
- Get ExecutionReturns execution.
- Get Execution MetricsReturns execution metrics.
- Get Execution ModeReturns execution mode.
- Get Execution OutputReturns execution output.
- Get Execution Output NodeReturns execution output node.
- Get Execution Output StateReturns execution output state.
- Get Execution Output StepReturns execution output step.
- Get Execution Result DataReturns execution result data.
Cortex modules
- Delete AnalyzerRemoves a custom analyzer registration.
- Delete JobDeletes a job record.
- Get AnalyzerReturns a single analyzer.
- Get JobReturns a single job.
- Get Job ReportReturns the report for a completed job.
- List AnalyzersRetrieves available analyzers.
- List JobsRetrieves analyzer/responder jobs.
- List RespondersRetrieves available responders.
- Make an API CallPerforms an arbitrary authorized API call.
- Run AnalyzerSubmits an observable to an analyzer.
- Run ResponderRuns a responder against a TheHive entity.
- Submit JobSubmits a file-type observable to an analyzer.
- Update Analyzer ConfigurationUpdates org-level analyzer configuration.
Frequently asked questions
Common questions about connecting Cortex and Rundeck.
Connect your Cortex 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. [3]
Example: when Rundeck's "Watch Executions" fires, WEXTL can "Delete Analyzer" in Cortex. Cortex has 13 actions (including Delete Analyzer, Delete Job, and Get Analyzer); Rundeck has 141 actions (including Abort Execution, Browse Job Groups, and Bulk Disable Executions). Add filters and transforms between steps when you need them. [1]
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. [2]
No. Cortex-to-Rundeck automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Cortex (or Rundeck) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Cortex + Rundeck automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Cortex and Rundeck integration.
- Cortex and Rundeck integration source code, module specs and credentials implementation.
- Our Cortex and Rundeck integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Cortex and Rundeck — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Cortex integration information
- Rundeck integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library