Skip to content

Automation · Operations and reporting

Turn off on WhatsApp the feature flag that breaks the checkout in LaunchDarkly

If a change breaks payment, ask on WhatsApp to turn off the flag: an AI agent finds it in LaunchDarkly, turns it off or requests approval.

How do I quickly turn off a feature flag that broke the checkout without opening LaunchDarkly?

You write to your Met "turn off the new checkout flag in production". The Met finds the project, searches the flag and opens its production configuration to confirm it is on. If the admin turned on in Connections the action that turns flags on or off, which starts turned off, the Met turns it off and tells you the previous and new state. If production requires approval, LaunchDarkly does not apply the change: the Met creates the request with the reviewer you name. Finally it checks the change history to tell you who had touched the flag.

What starts it

When someone asks for it

It starts when someone on the team asks the Met on WhatsApp to turn off a flag. The Met does not watch flags on its own or turn them off without being asked.

A manual task: someone on the team runs it with a button, or asks the Met for it in chat.

Who runs it

Internal Met that handles your LaunchDarkly feature flags

This is not a named, seeded Met. It is an internal Met with LaunchDarkly connected, for the owner or the agency that maintains the app: its work ends when the flag is off or the approval request is created.

Run by the data analyst Met

Channels: WhatsApp

What you need connected

5 steps · 7 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

  1. 1

    Find the project

    The Met lists the account's projects, with search by name, and takes your app's project for the next queries.

  2. 2

    Find the flag and its state

    The Met searches the flag in the production environment and opens its full configuration to confirm it is on and which variation it serves.

  3. 3

    Turn off the flag

    If the admin turned on the action that turns flags on or off, which starts turned off, the Met turns it off in production and tells you the previous and new state. If it is still off, it tells you it cannot.

  4. 4

    Request approval if production requires it

    If LaunchDarkly replies that the environment requires approval, the Met looks up the reviewer you name and creates the request with the instructions LaunchDarkly returned.

  5. 5

    Tell you who had changed it

    The Met queries the change history and replies with who last touched the flag and when, so your team can review that change.

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

FAQ

Questions about this automation

LaunchDarkly serves them the flag's off variation. Check in LaunchDarkly which variation that is before using this procedure.

Yes, with the same action, if it is still on in Connections. You ask for it in another instruction once your team confirms the fix shipped.

No. LaunchDarkly's hosted MCP server is not available on the European Union instance or in federal environments.

Keep going

Other automations built on the same tools

Want this automation running on your own data?

We will show it to you with your accounts connected, not with a canned demo.