LaunchDarkly and Okta Integration

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

Connect LaunchDarkly and Okta to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.

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

Learn about LaunchDarkly and Okta

Detailed info you need to know about LaunchDarkly and Okta 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]

  • Okta

    • Developer Tools
    • 2 triggers
    • 44 searches
    • 90 actions

    Identity and access management with users, groups, apps, policies, factors and hooks.[6]

How to connect LaunchDarkly to Okta

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

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

WEXTL exposes actions and triggers for LaunchDarkly and Okta 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 triggersOkta 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.

Okta modules

  • Activate a Device Marks a device as active. Use Suspend a Device and Unsuspend a Device to pause and resume a device instead.
  • Activate A Group Rule Starts a group rule in Okta. Deactivate A Group Rule stops it again.
  • Activate a Policy Activates one policy that belongs to the selected Policy Type. Deactivate a Policy reverses the step.
  • Activate A User Activates a user in Okta. Deactivate A User is the opposite step.
  • Activate An Application Switches an application on in Okta. Deactivate An Application reverses it.
  • Activate an Authenticator Enables an authenticator and reports its ID and Status. Reverse it later with Deactivate an Authenticator.
  • Activate an Authorization Server Starts an authorization server in Okta. Deactivate an Authorization Server turns it off again.
  • Activate an Event Hook Turns on an event hook. Output includes its ID and Status, and Verify an Event Hook checks the delivery endpoint.
  • Activate an Identity Provider Turns on an identity provider in Okta. Deactivate an Identity Provider turns it off again.
  • Add A Group Adds a group to Okta, built from a Profile. Replace A Group later changes its profile, and Delete A Group removes it.
  • Assign A Group Owner Makes an Owner responsible for a group. Delete A Group Owner undoes the assignment.
  • Assign A User To A Group Makes a user a member of a group. Unassign A User From A Group does the reverse.
  • Assign An App Sign-In Policy Sets the sign-in policy of an Application in Okta to a Policy of the matching Policy Type.
  • Assign An Application Group Assigns a group to an application with an optional Priority and Profile. Output includes Status and Last Updated, and Unassign An Application Group takes it back.
  • Assign An Application User Assigns an Okta user to an application. Use Profile for app-specific profile fields as JSON, such as a username mapping. Output includes ID and Status Changed.
  • Create A Group Rule Starts a rule definition for groups from a Name. Activate A Group Rule switches it on afterwards.
  • Create a Policy Makes a policy under a Policy Type, with a Name. Use Priority to control the evaluation order relative to other policies, and Conditions and Settings for JSON that depends on the policy type.
  • Create a Policy Rule Attaches a rule under a policy, built from a Rule Type and a Name. Give it a Priority, Conditions or Actions, whose shape varies by rule type.
  • Create a Realm Sets up a realm. Fill the Profile with the name, domains and realmType.
  • Create A User Registers a person in your Okta organization from a Profile. Activate A User is the separate step for activation.
  • Create a User Type Adds a user type under its Name and Display Name, optionally with a Description. The Created time is in the output.
  • Create An Application Builds an application from a Label and a Sign-On Mode. Add Visibility, Settings or Credentials as JSON, noting that the shape of Settings depends on the Sign-On Mode. Output includes ID and Status.
  • Create an Authorization Server Sets up an authorization server from a Name. Use Audiences to list the audiences, separated by spaces, and add a Description, Issuer Mode or Status as well.
  • Create an Identity Provider Registers an identity provider of an Identity Provider Type such as SAML2 or OIDC, with a Name. Use Protocol and Policy to add configuration, and the output holds the new id, type and status.
  • Create an OAuth 2.0 Scope Defines a scope on an authorization server under a Name. Use Display Name for the text in the consent dialog and Default Scope to mark it as a default.
  • Deactivate a Device Sets a device to inactive. Activate a Device sends it back to the active state.
  • Deactivate A Group Rule Stops a group rule from running. Activate A Group Rule starts it again.
  • Deactivate a Policy Deactivates one policy of the matching Policy Type. Activate a Policy puts it back in use.
  • Deactivate A User Deactivates a user in Okta. Reactivate A User is the related step.
  • Deactivate An Application Switches an application off in Okta. Activate An Application brings it back.
  • Deactivate an Authenticator Disables an authenticator and reports its ID and Status. Activate an Authenticator re-enables it.
  • Deactivate an Authorization Server Turns off an authorization server. Activate an Authorization Server reverses the change.
  • Deactivate an Event Hook Turns off an event hook, with its ID and Status in the output. Activate an Event Hook switches it back on.
  • Deactivate an Identity Provider Switches off an identity provider. Activate an Identity Provider turns it on again.
  • Delete a Device Removes a device record from your Okta organization.
  • Delete A Group Removes a group from your Okta tenant.
  • Delete A Group Owner Deletes an owner assignment from a group in Okta.
  • Delete A Group Rule Removes a group rule in your Okta setup.
  • Delete a Policy Deletes a policy of the matching Policy Type from Okta.
  • Delete a Policy Rule Deletes a Rule under a Policy that belongs to the selected Policy Type.
  • Delete a Realm Deletes a realm out of your Okta tenant.
  • Delete A User Deletes a user account from your Okta tenant.
  • Delete a User Type Removes the definition of a user type from Okta. The result is final.
  • Delete An Application Removes an application from your Okta organization.
  • Delete an Authorization Server Removes an authorization server from your Okta tenant.
  • Delete an Identity Provider Deletes an identity provider from the Okta setup.
  • Delete an OAuth 2.0 Scope Removes a Scope from an Authorization Server in Okta.
  • Enroll a Factor Enrolls a factor for a user with a Factor Type such as sms, call or push. Add a Provider, or fill Profile with factor-specific enrollment data. Turn on Activate to activate it at enrollment. Look for the factor ID and Status in the result.
  • Get a Device Looks up a device and returns its Status plus the Created and Last Updated dates.
  • Get a Policy Shows a policy of the chosen Policy Type. Output includes Name, Description, Priority and System.

Explore alternative integrations

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

Automate LaunchDarkly and Okta on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting LaunchDarkly and Okta.

How do I connect LaunchDarkly and Okta?

Connect your LaunchDarkly and Okta 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 Okta?

Example: when the "Watch Audit Log Entries" trigger in LaunchDarkly fires, WEXTL can "Activate a Device" in Okta. LaunchDarkly has 2 triggers (including Watch Audit Log Entries and Watch Events). Okta has 134 actions (including Activate a Device, Activate A Group Rule, and Activate a Policy). Add filters and transforms between steps when you need them.[1]

Can LaunchDarkly trigger actions in Okta, and Okta 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 Okta?

No. LaunchDarkly-to-Okta 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 Okta in real time?

Yes. Trigger-based automations start the moment LaunchDarkly (or Okta) 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 + Okta 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 Okta?

You can build your LaunchDarkly + Okta 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 Okta integration.

  1. LaunchDarkly and Okta integration source code, module specs and credentials implementation.
  2. Our LaunchDarkly and Okta integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for LaunchDarkly and Okta, 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. Okta 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 Okta integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore LaunchDarkly and Okta, or get started