Integration
Connect LaunchDarkly to Avoma
When Access Token Event fires in LaunchDarkly, your agent runs Update call in Avoma. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want LaunchDarkly and Avoma to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What LaunchDarkly can start in Avoma
When Access Token Event in LaunchDarkly
then Update call in Avoma
When Code Reference Repository Event in LaunchDarkly
then Upload Audio Call in Avoma
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 Avoma
Triggers and actions 11 triggers · 51 actions
Trigger
Access Token EventTriggers when access token activity happens on your LaunchDarkly account.
Trigger
Code Reference Repository EventTriggers when code reference repository activity happens on your LaunchDarkly account.
Trigger
Flag EventTriggers when flag activity happens on your LaunchDarkly account.
Trigger
Integration EventTriggers when integration activity happens on your LaunchDarkly account.
Trigger
Member EventTriggers when member activity happens on your LaunchDarkly account.
Trigger
Relay Proxy Configuration EventTriggers when relay proxy configuration activity happens on your LaunchDarkly account.
Trigger
Role EventTriggers when role activity happens on your LaunchDarkly account.
Trigger
Segment EventTriggers when segment activity happens on your LaunchDarkly account.
Trigger
Service Token EventTriggers when service token activity happens on your LaunchDarkly account.
Trigger
Team EventTriggers when team activity happens on your LaunchDarkly account.
Trigger
User EventTriggers when user activity happens on your LaunchDarkly account.
Action
Add or Remove User Targets From a Feature FlagAdds 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 flagCreates 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 metricCreates 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 tokenCreates 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 environmentAdds a new environment to a LaunchDarkly project, so flags can be configured separately for it. Returns the environment's SDK keys.
Action
Create a projectCreates a new LaunchDarkly project, optionally with its own environments and flag-naming rules.
Action
Create a segmentCreates a segment in one environment of a LaunchDarkly project, so you can target a named group of people with your flags.
Action
Delete environmentDeletes an environment from a LaunchDarkly project, along with all the flag settings it held.
Action
Delete feature flagPermanently deletes a feature flag from a LaunchDarkly project, in every environment.
Action
Delete metricDeletes a metric from a LaunchDarkly project.
Action
Delete projectDeletes a LaunchDarkly project and everything inside it - all of its environments, flags and segments.
Action
Delete segmentDeletes a segment from one environment of a LaunchDarkly project.
Action
Evaluate a Feature FlagWorks out which variation of each feature flag a particular person (or other context) would be served in one environment, and why.
Action
Get access tokenReturns one LaunchDarkly access token by its id, including its name, role, and when it was last used.
Action
Get custom roleReturns one LaunchDarkly custom role by its key, including its name, description, and policy statements.
Action
Get environmentReturns one environment in a LaunchDarkly project, including its keys, colour, and default flag settings.
Action
Get feature flagReturns one feature flag in a LaunchDarkly project, including its variations, tags, and per-environment settings.
Action
Get metricReturns one metric in a LaunchDarkly project, including how it is measured and which events it counts.
Action
Get projectReturns one LaunchDarkly project by its key, including its name, tags, and default settings.
Action
Get segmentReturns one segment in a LaunchDarkly project environment, including its included and excluded contexts and its rules.
Action
Get teamReturns one LaunchDarkly team by its key, including its name, description, and how many members and roles it has.
Action
List access tokensReturns the access tokens in your LaunchDarkly account.
Action
List custom rolesReturns the custom roles in your LaunchDarkly account.
Action
List environmentsReturns the environments in one LaunchDarkly project.
Action
List feature flagsReturns the feature flags in one LaunchDarkly project.
Action
List metricsReturns the metrics in one LaunchDarkly project.
Action
List projectsReturns the projects in your LaunchDarkly account.
Action
List segmentsReturns the segments in one LaunchDarkly project environment.
Action
List teamsReturns the teams in your LaunchDarkly account.
Action
List usersReturns the end users LaunchDarkly has seen in one project environment. Built on the contexts API, which replaced the retired users API.
Action
Search contextsSearches the contexts LaunchDarkly has seen in one project environment using a filter expression.
Action
Toggle a Feature FlagTurns a LaunchDarkly feature flag on or off in one environment.
Action
Update a Feature Flag With JSONUpdates 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 roleUpdates a LaunchDarkly custom role — its name, description, base permissions, or policy statements. Fields you leave blank are not changed.
Action
Update environmentUpdates an environment in a LaunchDarkly project — its name, colour, cache time, or confirmation settings. Fields you leave blank are not changed.
Action
Update metricUpdates a metric in a LaunchDarkly project — its name, description, tags, or unit. Fields you leave blank are not changed.
Action
Update projectUpdates a LaunchDarkly project — its name, tags, or default flag settings. Fields you leave blank are not changed.
Action
Update segmentUpdates 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 teamUpdates a LaunchDarkly team — its name, description, members, or custom roles. Fields you leave blank are not changed.
Action
Get callReturns a single Avoma call by its external ID, including its CRM links, recording URL, processing state and linked meeting.
Action
Get meetingReturns a single Avoma meeting by its UUID, including its attendees, schedule, state, and recording and transcription details.
Action
Get meeting insightsReturns the AI notes, keyword occurrences, popular keywords and speakers for a completed Avoma meeting.
Action
Get recordingReturns the signed audio and video download links for the recording of an Avoma meeting. If the video is still being processed, returns a message instead of the links.
Action
Get transcriptionReturns the transcript of a meeting's recording, including the speakers, the timed transcript text and a link to the VTT file.
Action
List callsReturns the calls in your Avoma organization that started within a date range, optionally narrowed to inbound or outbound calls.
Action
List meetingsReturns the meetings in your Avoma organization that started within a date range, optionally filtered by attendee, CRM record, recording length or meeting type.
Action
List notesReturns the AI-generated notes for meetings in a date range, optionally narrowed to one meeting or custom category.
Action
List scorecard evaluationsReturns completed scorecard evaluations for meetings, optionally narrowed by date range, scorecard template, meeting or evaluated user.
Action
List usersReturns the users in your Avoma organization, including each user's name, email, role, teams and status.
Action
Update callUpdates an existing call's details in Avoma, such as its subject, participant names, meeting purpose and outcome, or linked CRM records, and returns the updated call.
Action
Upload Audio CallCreates a call in Avoma from a publicly reachable audio recording. Avoma downloads the recording and processes it into a transcript and notes, or uses a transcript you supply.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from LaunchDarkly
LaunchDarkly to OntraportOntraport is an all-in-one CRM, marketing automation, and e-commerce platform.
LaunchDarkly to OpenRouterOpenRouter is a unified interface to AI models.
LaunchDarkly to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
LaunchDarkly to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
LaunchDarkly to MailchimpMailchimp marketing automation and email platform.
LaunchDarkly to StripeStripe is a payment processing platform for online businesses.
More into Avoma
HubSpot to AvomaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to AvomaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to AvomaSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to AvomaGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to AvomaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to AvomaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
LaunchDarkly and Avoma, 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 Avoma when something happens in LaunchDarkly?
Any of Avoma's 12 actions, including Update call, Upload Audio Call, Get call and Get meeting. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Avoma to LaunchDarkly?
Avoma has no triggers in the catalog today, so automations start in LaunchDarkly. If you need the other direction, ask: your agent reads Avoma's API documentation and adds it.
Do I have to build a connector for LaunchDarkly or Avoma?
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 Avoma 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.