LaunchDarkly and PagerDuty Integration

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

Connect LaunchDarkly and PagerDuty 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 PagerDuty

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

  • PagerDuty

    • Developer Tools
    • 2 triggers
    • 69 searches
    • 79 actions

    Incident management and on-call with services, schedules, escalation policies and incidents with webhook subscriptions.[6]

How to connect LaunchDarkly to PagerDuty

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

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

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

PagerDuty modules

  • Add a User to a Team Puts a user on a team, optionally with a given Role.
  • Add an Escalation Policy to a Team Attaches an existing escalation policy to a team and links the two.
  • Add Notification Subscribers Signs up people or teams as Subscribers for the status updates on one incident. The response includes the Result for each subscriber.
  • Assign Tags Adds and removes tags on an escalation policy, incident, service, team or user in one call. Use Add Tags for new or existing tags and Remove Tags to detach tags the entity already has.
  • Cancel Responder Requests for an Incident Cancels responder requests on an incident for the chosen Responder Request Targets, made by the Requester.
  • Change the Impact of an Incident on a Business Service Sets whether an incident impacts a business service, through Relation (Impacted or Not Impacted). The output returns the Relation.
  • Convert the Event Rules of a Service into Event Orchestration Rules Converts event rules from a service into event orchestration rules. The output reports a Convert Status and where they were Converted To.
  • Create a Change Event Records a change in PagerDuty from a Summary and a Source. Use Timestamp to set when the change occurred (it defaults to now) and Custom Details to attach more information.
  • Create a Maintenance Window Stops the listed Services from creating incidents from a Start Time until an End Time, when they start creating incidents again.
  • Create a New Integration Creates an integration on a service from a Type or a Vendor. For email integrations, add Email Filters and choose Email Incident Creation to control how messages open incidents.
  • Create a Note on an Incident Posts a note on an incident. Output includes the Channel and Created At of the note.
  • Create a Responder Request for an Incident Asks users or escalation policies to respond to an incident, sending a Message from the Requester.
  • Create a Schedule Builds an on-call rotation in a Time Zone from one or more Schedule Layers. Give it a Name and Description, and allow Overflow to let shifts run past the end of the range.
  • Create a Service Adds a service that incidents attach to, tied to an Escalation Policy. Add Auto Resolve Timeout, Acknowledgement Timeout, Alert Grouping or Support Hours to shape how incidents behave.
  • Create a Status Update on an Incident Posts a Message as a status update on an incident. Fill Subject and HTML Message to send a custom HTML email update.
  • Create a Tag Makes a tag from a Label. Attach it to entities with Assign Tags.
  • Create a Team Makes a team in PagerDuty from a Name. Use Description to describe the team and set Default Role to Manager or None.
  • Create a User Adds a user from a Name and Email, with an optional Role, License ID, Job Title, Color and Time Zone for the profile.
  • Create a User Contact Method Gives a user a new way to be reached, such as an email address or phone number. Fill Type, Label and Address, then Country Code if it is a phone.
  • Create a User Handoff Notification Rule Warns a user before an on-call shift changes hands, through a chosen Contact Method Type. Add a Notify Advance in Minutes delay before the rule fires.
  • Create a User Notification Rule Adds a step to how a user is alerted for incidents of a given Urgency. Wait before it fires with Start Delay in Minutes and choose the channel with Contact Method Type.
  • Create a User Status Update Notification Rule Defines how a user receives incident status updates, through a Contact Method Type.
  • Create an Escalation Policy Creates an escalation policy from a Name and ordered Escalation Rules. Use Number of Loops to repeat the policy after the last rule.
  • Create an Event Rule on a Service Creates an event rule on a service that matches incoming events by Conditions and then runs its Actions. Use Position to set its index, Time Frame to restrict when it applies and Disabled to create it switched off.
  • Create an Incident Raises an incident on a Service, under a Title. Rank it with Urgency and Priority, route it by Escalation Policy, and add an Incident Key to avoid duplicates.
  • Create Notification Subscriptions Signs one user up for the Subscribables listed, with a Result returned per entry.
  • Create One or More Overrides Replaces who is on call during specific time ranges on a schedule. Each entry of Overrides names a user and its own start and end. Output lists the Status and Errors of every override.
  • Create Team Notification Subscriptions Subscribes a team to the Subscribables listed. The output gives a Result per subscription.
  • Delete a Note on an Incident Removes a single note attached to an incident in PagerDuty.
  • Delete a Schedule Removes an on-call schedule from PagerDuty, given its Schedule ID.
  • Delete a Service Deletes the whole service with this Service ID from your PagerDuty account.
  • Delete a Tag Deletes the tag label with this ID from the tag list of your PagerDuty account.
  • Delete a Team Removes a team. Use Reassignment Team to move its unresolved incidents to another team.
  • Delete a User Removes a person from PagerDuty by User ID.
  • Delete a User Contact Method Deletes one contact method of a user in PagerDuty, found with User ID and Contact Method ID.
  • Delete a User Handoff Notification Rule Removes a rule that warned a user ahead of on-call shift changes.
  • Delete a User Notification Rule Removes one alert step from the incident notifications of a user.
  • Delete a User Session Ends one login session of a user, found by its Type.
  • Delete a User Status Update Notification Rule Deletes the rule that sent a user incident status updates through one contact method.
  • Delete All User Sessions Signs a user out by ending every session they have, browser and API alike.
  • Delete an Escalation Policy Deletes an escalation policy from your PagerDuty account, using the policy ID.
  • Delete an Event Rule from a Service Deletes one event rule of a service in PagerDuty, picked by the service and rule IDs.
  • Delete an Override Deletes one override from an on-call schedule, found by Schedule ID.
  • Delete or End a Maintenance Window Ends a maintenance window that is running, or deletes a scheduled one that has not started yet.
  • Enable a Webhook Subscription Enables a webhook subscription. The output shows whether it is Active along with its Delivery Method and Events.
  • Get a Change Event Reads one change event with its Summary, Timestamp, Services and Integration.
  • Get a Log Entry Reads a single entry from the PagerDuty log. Use Time Zone to show its times in a chosen zone.
  • Get a Maintenance Window Loads a maintenance window and reports its Sequence Number, Start Time and End Time. Use Include to add more models.
  • Get a Schedule Retrieves a schedule with its Schedule Layers, restricted to the Since to Until range. Add Include Next Oncall For User to see the next shift of one person.
  • Get a Service Pulls up a service with its Name, Description, Auto Resolve Timeout and Acknowledgement Timeout.

Explore alternative integrations

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

Automate LaunchDarkly and PagerDuty on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting LaunchDarkly and PagerDuty.

How do I connect LaunchDarkly and PagerDuty?

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

Example: when the "Watch Audit Log Entries" trigger in LaunchDarkly fires, WEXTL can "Add a User to a Team" in PagerDuty. LaunchDarkly has 2 triggers (including Watch Audit Log Entries and Watch Events). PagerDuty has 148 actions (including Add a User to a Team, Add an Escalation Policy to a Team, and Add Notification Subscribers). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore LaunchDarkly and PagerDuty, or get started