How to use the RunMyJobs plugin

Submit and monitor RunMyJobs process definitions from Kestra flows.

Authentication

All tasks require baseUrl (the RunMyJobs tenant URL including environment, e.g. https://dublin.runmyjobs.cloud/<customer>/<env>, required). Authenticate with username + password (HTTP Basic, for the built-in RunMyJobs REST interface), token (Bearer token, for the Inbound REST Extension), or apiKey (sent as X-API-KEY, for the Inbound REST Extension). Optionally set headers for custom headers and options for HTTP client configuration (proxy, timeouts, SSL). Store secrets in secrets and apply connection properties globally with plugin defaults.

Tasks

process.Submit submits a RunMyJobs Process Definition — set baseUrl, partition, and definitionName (all required). Optionally set parameters (map of parameters passed under the params field) or body (raw submission body sent verbatim — when set, parameters is ignored; use this to set fields like queue, runtimeLimit, or businessKey).

Set wait (default false) to poll for completion. When wait is true, optionally set pollFrequency (default PT10S) and maxDuration (default PT1H). Set failOnNonCompleted (default true) to fail the task if the process ends in a non-successful terminal state (error, killed, cancelled, aborted, completedAbnormally).

Outputs processId, businessKey, status, and — when wait is true — started and ended timestamps.