--- title: "Connect LaunchDarkly to Luma - APIANT.ai" description: "When \"Access Token Event\" fires in LaunchDarkly, your agent runs \"Add ticket type\" in Luma." canonical: "https://apiant.ai/connect/launchdarkly-to-luma" --- # Connect LaunchDarkly to Luma When **Access Token Event** fires in [LaunchDarkly](https://apiant.ai/connections/launchdarkly), your agent runs **Add ticket type** in [Luma](https://apiant.ai/connections/luma). Describe the whole flow and it is built, tested on every scenario and kept running. LaunchDarkly **11** triggers LaunchDarkly **39** actions Luma **17** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want LaunchDarkly and Luma to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What LaunchDarkly can start in Luma - When **Access Token Event** in LaunchDarkly then **Add ticket type** in Luma - When **Code Reference Repository Event** in LaunchDarkly then **Apply contact tag** in Luma Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with LaunchDarkly and Luma ## Triggers and actions 11 triggers · 56 actions - Trigger **Access Token Event** Triggers when access token activity happens on your LaunchDarkly account. - Trigger **Code Reference Repository Event** Triggers when code reference repository activity happens on your LaunchDarkly account. - Trigger **Flag Event** Triggers when flag activity happens on your LaunchDarkly account. - Trigger **Integration Event** Triggers when integration activity happens on your LaunchDarkly account. - Trigger **Member Event** Triggers when member activity happens on your LaunchDarkly account. - Trigger **Relay Proxy Configuration Event** Triggers when relay proxy configuration activity happens on your LaunchDarkly account. - Trigger **Role Event** Triggers when role activity happens on your LaunchDarkly account. - Trigger **Segment Event** Triggers when segment activity happens on your LaunchDarkly account. - Trigger **Service Token Event** Triggers when service token activity happens on your LaunchDarkly account. - Trigger **Team Event** Triggers when team activity happens on your LaunchDarkly account. - Trigger **User Event** Triggers when user activity happens on your LaunchDarkly account. - Action **Add or Remove User Targets From a Feature Flag** Adds people to, or removes them from, the individual targeting list for one variation of a feature flag in a chosen environment. - Action **Create a feature flag** Creates a new feature flag in a LaunchDarkly project, either a plain on/off flag or one with your own list of variations. - Action **Create a metric** Creates a metric in a LaunchDarkly project so you can measure the effect of a flag or experiment - a custom event, a click, a page view, or a trace. - Action **Create an access token** Creates a LaunchDarkly API access token with the access level you choose. The full token value is returned only on this call, so save it right away. - Action **Create an environment** Adds a new environment to a LaunchDarkly project, so flags can be configured separately for it. Returns the environment's SDK keys. - Action **Create a project** Creates a new LaunchDarkly project, optionally with its own environments and flag-naming rules. - Action **Create a segment** Creates a segment in one environment of a LaunchDarkly project, so you can target a named group of people with your flags. - Action **Delete environment** Deletes an environment from a LaunchDarkly project, along with all the flag settings it held. - Action **Delete feature flag** Permanently deletes a feature flag from a LaunchDarkly project, in every environment. - Action **Delete metric** Deletes a metric from a LaunchDarkly project. - Action **Delete project** Deletes a LaunchDarkly project and everything inside it - all of its environments, flags and segments. - Action **Delete segment** Deletes a segment from one environment of a LaunchDarkly project. - Action **Evaluate a Feature Flag** Works out which variation of each feature flag a particular person (or other context) would be served in one environment, and why. - Action **Get access token** Returns one LaunchDarkly access token by its id, including its name, role, and when it was last used. - Action **Get custom role** Returns one LaunchDarkly custom role by its key, including its name, description, and policy statements. - Action **Get environment** Returns one environment in a LaunchDarkly project, including its keys, colour, and default flag settings. - Action **Get feature flag** Returns one feature flag in a LaunchDarkly project, including its variations, tags, and per-environment settings. - Action **Get metric** Returns one metric in a LaunchDarkly project, including how it is measured and which events it counts. - Action **Get project** Returns one LaunchDarkly project by its key, including its name, tags, and default settings. - Action **Get segment** Returns one segment in a LaunchDarkly project environment, including its included and excluded contexts and its rules. - Action **Get team** Returns one LaunchDarkly team by its key, including its name, description, and how many members and roles it has. - Action **List access tokens** Returns the access tokens in your LaunchDarkly account. - Action **List custom roles** Returns the custom roles in your LaunchDarkly account. - Action **List environments** Returns the environments in one LaunchDarkly project. - Action **List feature flags** Returns the feature flags in one LaunchDarkly project. - Action **List metrics** Returns the metrics in one LaunchDarkly project. - Action **List projects** Returns the projects in your LaunchDarkly account. - Action **List segments** Returns the segments in one LaunchDarkly project environment. - Action **List teams** Returns the teams in your LaunchDarkly account. - Action **List users** Returns the end users LaunchDarkly has seen in one project environment. Built on the contexts API, which replaced the retired users API. - Action **Search contexts** Searches the contexts LaunchDarkly has seen in one project environment using a filter expression. - Action **Toggle a Feature Flag** Turns a LaunchDarkly feature flag on or off in one environment. - Action **Update a Feature Flag With JSON** Updates a LaunchDarkly feature flag by sending your own semantic patch instructions as JSON, for changes the ready-made actions do not cover. - Action **Update custom role** Updates a LaunchDarkly custom role — its name, description, base permissions, or policy statements. Fields you leave blank are not changed. - Action **Update environment** Updates an environment in a LaunchDarkly project — its name, colour, cache time, or confirmation settings. Fields you leave blank are not changed. - Action **Update metric** Updates a metric in a LaunchDarkly project — its name, description, tags, or unit. Fields you leave blank are not changed. - Action **Update project** Updates a LaunchDarkly project — its name, tags, or default flag settings. Fields you leave blank are not changed. - Action **Update segment** Updates a segment in a LaunchDarkly project environment — its name, description, tags, or the contexts it includes and excludes. Fields you leave blank are not changed. - Action **Update team** Updates a LaunchDarkly team — its name, description, members, or custom roles. Fields you leave blank are not changed. - Action **Add guests** Adds one or more guests to a Luma event, optionally assigning ticket types, an approval status, and whether Luma emails them. Returns any guests Luma skipped. - Action **Add host** Adds a host to a Luma event, as a manager or as check-in staff, by email address. - Action **Add ticket type** Creates a new ticket type (free or paid) for a Luma event. Paid ticket types require the calendar to have a connected Stripe account. - Action **Apply contact tag** Applies a contact tag to existing contacts on your Luma calendar, identified by user ID or email. Does not create new contacts. - Action **Block contact** Blocks a contact on your Luma calendar so they can't follow it or join its events, and stop receiving your invites and newsletters. - Action **Cancel event** Cancels a Luma event. The event is permanently deleted, all guests are notified, and paid guests can optionally be refunded. - Action **Create Calendar Person** Adds a person to your Luma calendar as a contact by email, optionally with a name and contact tags, so you can invite them to events and send newsletters. - Action **Get calendar** Returns the details of the Luma calendar your connected API key belongs to, including its name, URL, location, social handles and default event settings. - Action **Get event** Returns the details of a Luma event, including its schedule, location, visibility, hosts and, for events you manage, guest counts by status. - Action **Get guest** Returns one guest of a Luma event, looked up by guest ID, ticket key, guest key or email, including their approval status, registration answers and tickets. - Action **Import contacts** Imports contacts into your Luma calendar so you can invite them to events and send them newsletters, optionally tagging them. - Action **List contacts** Returns the contacts (people) on your Luma calendar, optionally filtered by a name/email search, tags or membership status. - Action **List events** Returns the events on your Luma calendar, optionally filtered by date range, submission status, platform and access level. - Action **List guests** Returns the guests who have registered for or been invited to a Luma event, with their approval status, contact details, registration answers and tickets. - Action **List ticket types** Returns every ticket type set up for a Luma event, including its name, price and capacity. - Action **Send invites** Sends people an email invite (and an SMS if their phone is linked to Luma) to a Luma event. Returns any invitees who were skipped because they unsubscribed, were removed, or are blocked. - Action **Update guest status** Changes a guest's registration status for a Luma event — approve (Going), decline, move back to pending approval, or waitlist — optionally refunding a paid guest and adding a personal note to the notification email. ## Each app on its own - [ **LaunchDarkly** LaunchDarkly allows you to innovate faster, deploy fearlessly, and make each release a masterpiece.](https://apiant.ai/connections/launchdarkly) - [ **Luma** Luma is an event management app that gives you the tools to host delightful events.](https://apiant.ai/connections/luma) Reviews ## What our customers say ## More from LaunchDarkly - [ **LaunchDarkly to Ontraport** Ontraport is an all-in-one CRM, marketing automation, and e-commerce platform.](https://apiant.ai/connect/launchdarkly-to-ontraport) - [ **LaunchDarkly to OpenRouter** OpenRouter is a unified interface to AI models.](https://apiant.ai/connect/launchdarkly-to-openrouter) - [ **LaunchDarkly to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/launchdarkly-to-salesforce) - [ **LaunchDarkly to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/launchdarkly-to-slack) - [ **LaunchDarkly to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/launchdarkly-to-mailchimp) - [ **LaunchDarkly to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/launchdarkly-to-stripe) ## More into Luma - [ **HubSpot to Luma** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-luma) - [ **Salesforce to Luma** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-luma) - [ **Slack to Luma** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-luma) - [ **Google Sheets to Luma** Google Sheets](https://apiant.ai/connect/google-sheets-to-luma) - [ **Gmail to Luma** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-luma) - [ **Google Calendar to Luma** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-luma) Questions ## LaunchDarkly and Luma, answered ### ### What can start an automation from LaunchDarkly? Any of LaunchDarkly's 11 triggers in the catalog, including Access Token Event, Code Reference Repository Event, Flag Event and Integration Event. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Luma when something happens in LaunchDarkly? Any of Luma's 17 actions, including Create Calendar Person, Send invites, Update guest status and Add guests. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Luma to LaunchDarkly? Luma has no triggers in the catalog today, so automations start in LaunchDarkly. If you need the other direction, ask: your agent reads Luma's API documentation and adds it. ### ### Do I have to build a connector for LaunchDarkly or Luma? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use LaunchDarkly and Luma without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.