LaunchDarkly and Rundeck Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Keep LaunchDarkly and Rundeck matched by integrating their events and actions. When developer tools events happen in LaunchDarkly, update the Rundeck automatically - without any line of code in visual workflow builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about LaunchDarkly and Rundeck

Detailed info you need to know about LaunchDarkly and Rundeck integrations in WEXTL. Explore which modules apps support and how you connect them.

  • LaunchDarkly

    • Developer Tools
    • 2 triggers
    • 66 searches
    • 76 actions

    Feature flag and release management.[5]

  • Rundeck

    • Developer Tools
    • 2 triggers
    • 65 searches
    • 76 actions

    Run jobs, track executions, and manage projects in Rundeck.[6]

How to connect LaunchDarkly to Rundeck

Set up your LaunchDarkly and Rundeck integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between LaunchDarkly and Rundeck work in WEXTL?

WEXTL exposes actions and triggers for LaunchDarkly and Rundeck that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

LaunchDarkly triggersRundeck actions

LaunchDarkly modules

  • Add a Flag Follower Subscribes a member to a feature flag in one environment of a LaunchDarkly project. Output includes the Flag Key and Member ID.
  • Add a Flag Prerequisite Sets up a dependency between flags using Prerequisite Flag and Prerequisite Variation. Add a Comment for the history of the change.
  • Add a Member to Teams Puts an account member into one or more teams at once. Output includes the Role, Email and Teams of the member.
  • Add Flag Targets Serves one Variation of a feature flag to chosen Context Keys. Set Context Kind for a kind other than user, and add a Comment for the change history.
  • Add Members by Email Sends invitations to a list of Emails, giving every invitee the same base Role. Add Custom Roles or Teams to give invitees extra roles and team places. Blank rows are skipped.
  • Add Segment Excluded Targets Excludes Context Keys of one Context Kind from a segment. A key cannot be both included and excluded, and up to 1,500 keys go in per call.
  • Add Segment Included Targets Includes Context Keys of a given Context Kind in a segment. Each call takes up to 1,500 keys, and you can add a Comment to explain the change.
  • Apply an Approval Request Applies an approval request so its changes take effect. Add a Comment to describe the change.
  • Archive a Feature Flag Archives a feature flag in a project. Use Comment to record the reason in the history.
  • Copy Feature Flag Settings Copies flag targeting from the From Environment over to the To Environment, overwriting what is there. Use Only Copy to move only some parts, or leave it empty to copy everything.
  • Create a Big Segment Export Starts exporting a big segment of one environment. Output includes the Export ID.
  • Create a Code Reference Repository Registers a repository for code references under a Name. Use Type for where it is hosted, Source Link for its address, and Default Branch for the main branch.
  • Create a Custom Role Defines a role with a Name, a Key that cannot be changed later, and a Policy of statements. Each statement lists Actions and Resources to allow or deny.
  • Create a Feature Flag Makes a feature flag from a Name and Key. Set Flag Type to boolean for automatic true and false variations, or to string or number and list your own Variations. Turn on Temporary for a flag you will remove later.
  • Create a Flag Approval Request Opens an approval request for a flag Change. Use Description to tell reviewers what changes and why, Notify Members and Notify Teams to ask people to review, and Run At to apply it once approved.
  • Create a Flag Link Links a flag to an outside address, a feature LaunchDarkly marks as beta. Give the link a Title and a Deep Link, and add a Description, Integration Key or Key if needed.
  • Create a Flag Trigger Creates a trigger URL for a flag in one environment. Use Integration to say who calls it and Action to turn the flag on or off when it is called. The result includes the Trigger URL.
  • Create a Metric Defines a metric for experiments. Give it a Name, Key and Kind, and use Success Criteria to say whether a higher or lower value counts as a win.
  • Create a Project Starts a new project with its environments, under a Name plus a Key that cannot be changed later. Add Tags, and enable Include Flags in Client-side Snippets to make new flags available to client-side snippets by default.
  • Create a Segment Sets up a segment for one environment under a Name and Key. Turn on Big Segment for a very large list of context keys, which needs a Big Segment Context Kind.
  • Create a Team Forms a new team. Give it a Name and a Key that cannot be changed later. Use Members to add people and Custom Roles for the roles the team grants to its members.
  • Create a Webhook Registers a webhook that posts LaunchDarkly changes to a URL. Use Resource Kind to say which changes are sent and turn on Sign Requests to sign each delivery. The result also shows the Secret.
  • Create an Access Token Issues an access token that has a Name and Role. The token value is shown once. Turn on Service Token to tie it to the account instead of a member, and use Expires At to end it on a date.
  • Create an Environment Sets up an environment inside a project. Give it a Name, Key and Color, and use Copy Settings From to start from an existing environment. Use Default TTL to set how many minutes clients cache flag values.
  • Delete a Code Reference Repository Deletes a repository that was registered to report code references.
  • Delete a Custom Role Removes a custom role defined from policy statements.
  • Delete a Data Export Destination Removes a data export destination from one environment of a project.
  • Delete a Feature Flag Removes a feature flag from its project. No undo exists.
  • Delete a Flag Link Removes a link attached to a flag, a feature LaunchDarkly marks as beta.
  • Delete a Flag Trigger Deletes a trigger URL attached to a flag in one environment.
  • Delete a Flag Workflow Removes a release workflow belonging to a flag, in one of its environments.
  • Delete a Member Deletes a person from your LaunchDarkly account.
  • Delete a Metric Removes a metric used by experiments in a project.
  • Delete a Project Removes a project, the container of environments and flags, from LaunchDarkly.
  • Delete a Relay Proxy Config Removes a Relay Proxy configuration from your account.
  • Delete a Scheduled Flag Change Removes a change scheduled for a flag in an environment.
  • Delete a Segment Deletes a segment belonging to an environment.
  • Delete a Team Deletes a team, the group that holds members and roles.
  • Delete a Webhook Removes a webhook that delivers LaunchDarkly changes to a URL.
  • Delete an Access Token Deletes an access token from LaunchDarkly, whether it is a member token or a service token.
  • Delete an Application Deletes an application, a feature LaunchDarkly marks as beta.
  • Delete an Approval Request Deletes an approval request that is waiting for a decision or is approved but not yet applied.
  • Delete an Environment Deletes one of the environments listed under a project.
  • Evaluate Flags for Context Evaluates all flags of an environment for one context, built from Context Kind and Context Key. Add Attributes for extra attributes that targeting rules read. Each value comes with its Reason.
  • Get a Big Segment Export Looks up the status of a big segment export started earlier, with its Size Bytes and Creation Time.
  • Get a Big Segment Membership for Context Checks whether a context belongs to a big segment, using Context Key. Output says whether it is Included or Excluded.
  • Get a Code Reference Repository Pulls the Source Link, Type and Default Branch of a code reference repository.
  • Get a Custom Role Reads a custom role, covering its Policy, Base Permissions and Assigned To.
  • Get a Data Export Destination Reads a data export destination of an environment, with its Kind, Config and whether it is On.
  • Get a Feature Flag Returns a feature flag with its targeting. Use Environment to limit the settings to that environment alone.

Rundeck modules

  • Abort an Execution Stops an execution that is still running in Rundeck.
  • Browse Job Groups Lists the job groups inside a project through the browse view. Set Limit to bound how many results a run reads.
  • Create a Project Creates a Rundeck project from a Project name, with an optional Description.
  • Create a Project ACL Saves a new ACL policy file inside a project. Use Policy Contents to supply the YAML text, such as the body of an .aclpolicy file.
  • Create a System ACL Saves a new ACL policy file at the system level. Use Policy Contents to supply the YAML text that defines the policy.
  • Create a Token Generates an API token for one Rundeck user.
  • Create a User Token Generates an API token for a Rundeck user, optionally with Roles.
  • Create a Webhook Creates a webhook under a Name inside a project. Use Config JSON for the settings of the webhook.
  • Create Jobs by Import Adds jobs to a project by uploading a Job definition file. Use Format to say whether the file is YAML or XML.
  • Delete a Config Key Removes one configuration key from a project.
  • Delete a Job Removes a job that was defined in a Rundeck project.
  • Delete a Jobs File Deletes a jobs file from the Rundeck server.
  • Delete a Key Removes a key from Rundeck key storage.
  • Delete a MOTD Removes the MOTD file stored with a project.
  • Delete a Named Project ACL Removes a named ACL policy kept in a project.
  • Delete a Named System ACL Deletes a named ACL policy from the system level.
  • Delete a Project Deletes a project from your Rundeck server.
  • Delete a Project ACL Removes an ACL policy file from the access rules of a project.
  • Delete a Readme Removes the readme file that a project carries in Rundeck.
  • Delete a System ACL Deletes an ACL policy file from the system access rules.
  • Delete a Token Deletes an API token from Rundeck.
  • Delete a Webhook Deletes a webhook that was set up in a project.
  • Delete All Job Executions Removes all executions that a job has in a Rundeck project.
  • Delete an Execution Removes an execution record from your Rundeck server.
  • Delete Executions in Bulk Deletes a group of executions in one request.
  • Delete Job Executions History Clears the executions history kept for one job in Rundeck.
  • Delete Jobs in Bulk Deletes a set of jobs through one call.
  • Disable a Job Execution Switches off execution for one single job in a project.
  • Disable a Job Schedule Pauses the recurring schedule of one job in a Rundeck project.
  • Disable Executions in Bulk Turns off execution for every job on a comma-separated list of Job IDs, in a single request.
  • Disable Schedules in Bulk Suspends the schedules of every job on a comma-separated list of Job IDs, using one request.
  • Disable System Executions Blocks all executions across the whole Rundeck system.
  • Enable a Job Execution Lets one job run again after execution was switched off.
  • Enable a Job Schedule Resumes the recurring schedule of one job in a Rundeck project.
  • Enable Executions in Bulk Turns execution back on for each job on the comma-separated Job IDs list, all in one request.
  • Enable Schedules in Bulk Switches schedules back on for all jobs on the comma-separated Job IDs list with one request.
  • Enable System Executions Allows executions to run again across the whole Rundeck system.
  • Execute Bulk Execution Delete Starts a bulk delete of executions in Rundeck, sent as one request.
  • Execute Bulk Job Delete Sends one bulk request to Rundeck that deletes several jobs.
  • Export a Project Exports a Rundeck project into one archive file, using the project export API.
  • Export a Project Asynchronously Starts a project export in Rundeck and returns before the archive is done. Use Get a Project Export Status to follow it.
  • Export Jobs Writes out the jobs that one Rundeck project holds. Set Limit for a smaller number of results in each run.
  • Generate a Token for a User Generates an API token for a specific Rundeck user account.
  • Get a Feature Retrieves a single feature of the Rundeck server.
  • Get a Job Pulls one job together with the Rundeck project that owns it.
  • Get a Job Forecast Reads the schedule forecast that Rundeck keeps for a job within its project.
  • Get a Job Workflow Returns the workflow saved with a job in its Rundeck project.
  • Get a MOTD Pulls the MOTD file kept with a project in Rundeck.
  • Get a Plugin Detail Reads what Rundeck reports about one plugin on the server.
  • Get a Project Returns one Rundeck project with the details Rundeck has on it.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with LaunchDarkly and Rundeck integrations. Pick any from the list below if the current combination isn't the one you need.

Automate LaunchDarkly and Rundeck on WEXTL®

Claim your 3-day trial to build LaunchDarkly with Rundeck integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting LaunchDarkly and Rundeck.

How do I connect LaunchDarkly and Rundeck?

Connect your LaunchDarkly 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]

What can I automate between LaunchDarkly and Rundeck?

Example: when the "Watch Audit Log Entries" trigger in LaunchDarkly fires, WEXTL can "Abort an Execution" in Rundeck. LaunchDarkly has 2 triggers (including Watch Audit Log Entries and Watch Events). Rundeck has 141 actions (including Abort an Execution, Browse Job Groups, and Create a Project). Add filters and transforms between steps when you need them.[1]

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

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

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

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

Does LaunchDarkly integrate with Rundeck in real time?

Yes. Trigger-based automations start the moment LaunchDarkly (or Rundeck) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a LaunchDarkly + Rundeck integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect LaunchDarkly with Rundeck?

You can build your LaunchDarkly + Rundeck automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the LaunchDarkly and Rundeck integration.

  1. LaunchDarkly and Rundeck integration source code, module specs and credentials implementation.
  2. Our LaunchDarkly and Rundeck integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for LaunchDarkly and Rundeck, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. LaunchDarkly integration information
  6. Rundeck integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted LaunchDarkly and Rundeck integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore LaunchDarkly and Rundeck, or get started