Integration
Connect LaunchDarkly and wethod
When Access Token Event fires in LaunchDarkly, your agent runs Create a contact in wethod, or New Client in wethod to Create a project in LaunchDarkly. 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 wethod 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 and wethod can do together
From LaunchDarkly to wethod
When Access Token Event in LaunchDarkly
then Create a contact in wethod
When Code Reference Repository Event in LaunchDarkly
then Create an invoice in wethod
From wethod to LaunchDarkly
When New Client in wethod
then Create a project in LaunchDarkly
When New Contact in wethod
then Create a feature flag in LaunchDarkly
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 wethod
Triggers and actions 18 triggers · 89 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.
Trigger
New ClientRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Trigger
New ContactRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Trigger
New InvoiceRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.
Trigger
New PersonHere the dedicated support page.
Trigger
New ProjectThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Trigger
Sent InvoiceTriggers when an invoice is in sent status.
Trigger
Updated ProjectTriggers when a project is created or updated.
Action
Archive a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.
Action
Create a clientRequired permissions: - **crm.edit**: allows to create resources. Here the dedicated support page.
Action
Create a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Create an invoiceRequired permissions: - **invoices.create**: required to create invoices for projects where the user is PM or Account. - **invoices.create_other**: required to create invoices for projects where the user is not PM or Account.
Action
Create a personCreates a new person as a **placeholder**: a member of the team who can be planned and allocated on projects, but cannot sign in until invited. Required permissions: - **team.edit_user** or **team.edit_placeholder**: allows creation of placeholder persons. [Here the dedicated support page](https:/
Action
Create a person allocationRequired permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He
Action
Create a projectRequired permissions: - **pipeline.create**: to create a project the user is PM or Account - **pipeline.create_other**: to create a project where the user is not PM nor Account Here the dedicated support page. ### Project met
Action
Create a project statusRequired permissions: - **project_status.create**: allows to create resources of projects where the user is the PM or the Account. - **project_status.create_other**: allows to create resources of projects where the user is not the PM nor the Account.
Action
Create a timesheetRequired permissions: - **timetracking.view**: allows to create resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.
Action
Delete a clientRequired permissions: - **crm.edit**: allows to delete resources. Here the dedicated support page.
Action
Delete a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Delete an invoiceRequired permissions: - **invoices.delete**: required to delete invoices for projects where the user is PM or Account. - **invoices.delete_other**: required to delete invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to delete sent/paid invoices.
Action
Delete a person allocationRequired permissions: - **planning.modify**: to delete allocation for a project where the user is PM or Account - **planning.modify_other**: to delete allocation for a project where the user is not PM nor Account - **planning.modify_past**: to delete allocation on today or in a date in the past [He
Action
Delete a projectRequired permissions: - **pipeline.delete**: to delete project where the user is PM or Account - **pipeline.delete_other**: to delete project where the user is not PM nor Account Here the dedicated support page.
Action
Delete a timesheetRequired permissions: - **timetracking.view**: allows to delete resources. Here the dedicated support page.
Action
Find ClientFinds the first client whose name matches the search text.
Action
Find PersonFinds the first person whose name or email matches the search text.
Action
Get a budgetRequired permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.
Action
Get a clientRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Action
Get a contactRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Action
Get an expenseRequired permissions: - **expenses.view**: allows view the expense if the user is the owner. - **expenses.view_other**: allows view the expense if the user is not the owner. Here the dedicated support page.
Action
Get an invoiceRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of any invoice. Here the dedicated support page.
Action
Get a personHere the dedicated support page.
Action
Get a projectThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Action
Get a stream:::warning Requires **Streams** to be enabled in company settings. :::
Action
Get the authenticated personReturns the person data associated with the currently authenticated user. No specific permissions are required beyond authentication.
Action
List budgetsRequired permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.
Action
List business unitsRequired permissions: - **settings.company**: allows view of company business units.
Action
List clientsRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Action
List contactsRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Action
List expensesRequired permissions: - **expenses.view**: allows view expenses where the user is the owner. - **expenses.view_other**: allows view expenses where the user is not the owner. Here the dedicated support page.
Action
List invoicesRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.
Action
List job titlesRequired permissions: - **settings.company**: allows view of job titles. Here the dedicated support page.
Action
List people allocationsRequired permissions: - **planning.view**: allows view of resources owned by the user. - **planning.view_other**: allows of view resources not owned by the user. Here the dedicated support page.
Action
List personsHere the dedicated support page.
Action
List projectsThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Action
List project statusesRequired permissions: - **project_status.view**: allows view resources of projects where the user is the PM or the Account. - **project_status.view_other**: allows view resources of projects where the user is not the PM nor the Account.
Action
List project typesList project types
Action
List streams:::warning Requires **Streams** to be enabled in company settings. :::
Action
List timesheetsRequired permissions: - **timetracking.view** Here the dedicated support page.
Action
Set an invoice as paidRequired permissions: - **invoices.edit_sent**: allows setting invoices as paid.
Action
Set an invoice as unpaidRequired permissions: - **invoices.edit_sent**: allows setting invoices as unpaid.
Action
Unarchive a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.
Action
Update a clientRequired permissions: - **crm.edit**: allows to update resources. Here the dedicated support page.
Action
Update a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Update an invoiceRequired permissions: - **invoices.edit**: required to update invoices for projects where the user is PM or Account. - **invoices.edit_other**: required to update invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to update sent/paid invoices.
Action
Update a personRequired permissions: - **team.edit_user** or **team.edit_placeholder**: allows update of placeholder persons. - **team.edit_user**: allows update of invited and active persons. Here the dedicated support page.
Action
Update a person allocationRequired permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He
Action
Update a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account - **pipeline.job_order**: to update a project job order [Here the dedicated support page].
Action
Update a timesheetRequired permissions: - **timetracking.view**: allows to update resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.
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 wethod
HubSpot to wethodHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to wethodSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to wethodSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to wethodGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to wethodGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to wethodGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
LaunchDarkly and wethod, 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 wethod when something happens in LaunchDarkly?
Any of wethod's 50 actions, including Create a client, Create a contact, Create an invoice and Create a person. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from wethod to LaunchDarkly?
Yes. When something happens in wethod, your agent can act in LaunchDarkly too. This page covers both directions: wethod's triggers and LaunchDarkly's actions are listed here as well.
Do I have to build a connector for LaunchDarkly or wethod?
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 wethod 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.