> ## Documentation Index
> Fetch the complete documentation index at: https://composio-preview.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> Latest updates and announcements for Composio

**Nov 3, 2026**

Create private custom MCP toolkits, configure trigger polling, and upgrade to Composio client 2.0.1.

## SDK releases: custom toolkits in Python 0.31.0 and TypeScript 0.28.0

You can now create custom MCP toolkits for a single user or share them across your project. Both SDKs use Composio client `2.0.1`.

### Release versions

| SDK | Version |
| - | - |
| Python `composio` | `0.31.0` |
| TypeScript `@composio/core` | `0.28.0` |
| TypeScript `@composio/slim` | `0.28.0` |
| TypeScript `@composio/anthropic` | `0.11.7` |

All 13 Python provider packages are released at `0.31.0`.

### What's new

* **Custom MCP toolkits.** Use `composio.experimental.custom_toolkits.create()` in Python or `composio.experimental.customToolkits.create()` in TypeScript. Set `user_id` or `userId` to a user ID for a private toolkit, or to `'all'` to share it across the project. Creation returns a generated slug and, when available, a connect link for a private toolkit. Store the slug and pass it to `update()` to change the name, logo, or API key input copy. TypeScript also accepts `additionalFields.genericId` for headers that use `{{generic_id}}`.
* **Trigger delivery and polling.** Pass `type` to choose webhook or polling delivery for a trigger that supports both. Set `polling_interval` in Python or `pollingInterval` in TypeScript to choose the minutes between polls. Created and listed instances include their delivery type, polling interval, and fallback reason. Trigger type metadata reports supported delivery types and whether webhook endpoint setup is required.
* **Session policies.** TypeScript `sessionConfigs.get()` preserves `require_approval` lists and accepts policy entries that contain only approval requirements. Toolkit metadata also exposes `meta.appUrl` when the API returns it.
* **Anthropic compatibility.** The TypeScript Anthropic provider accepts `@anthropic-ai/sdk` `^0.135.0`.

### Migration notes

> [!WARNING]
>
> Composio client `2.0.1` changes direct API client access and automatic retries for writes. Review the steps below if you call the underlying client or relied on retries for POST and PATCH requests.

1. **Custom toolkit registration.** `upsert()` still works, but warns once per process that it is deprecated. Before: register a toolkit with a caller-chosen slug through `upsert()`. After: call `create()`, store its returned slug, and use `update(slug, ...)` for later metadata changes. The server URL, auth schemes, and owning user cannot change after creation; delete and create the toolkit again to change them.
2. **Write retries.** POST and PATCH requests are sent once by default. A write may complete on the server even when its response is lost, so retry only when you can prevent duplicate side effects. Reads keep their retry behavior. On the TypeScript client returned by `getClient()`, opt a write into retries with that call's `maxRetries` option.
3. **Direct TypeScript client calls.** Replace `client.request(...)` with `client.get(path, options)` for GET requests, retaining the relevant query and request options. For other HTTP methods, use `post`, `patch`, `put`, or `delete`. Resource classes, `Composio.Tools`-style statics, namespace-member types, `Composio.Composio`, and `Composio.DEFAULT_TIMEOUT` are removed. Import types from `@composio/client/resources/*` without `.js` or `.mjs` suffixes, and use indexed access for nested types.
4. **Session config search.** TypeScript `sessionConfigs.list()` ignores the deprecated `search` option and warns when you set it. Filter the returned `items` by name instead.

### Bug fixes

* **Local upload MIME types.** Files uploaded from local paths use the MIME type of their extension instead of always using `application/octet-stream`. Python and TypeScript use the same extension table. Files supplied as `File` objects or URLs keep the MIME type they carry.
* **Python downloaded filenames.** Files downloaded from extensionless URLs use the extension corresponding to a known response MIME type, including formats such as CSV and PowerPoint. Unknown MIME types leave the generated filename extensionless.
* **Python schema defaults.** Default coercion handles schemas whose `type` is a list, including nullable types.
* **Python Gemini execution.** Manual function-call handling uses the user or session you supply, and rejects ambiguous ownership instead of choosing the last user to fetch tools. See the [Gemini provider fix](https://composio-preview.mintlify.site/docs/changelog/2026/10/27).
* **TypeScript session authorization.** Sessions returned by `create()` and `use()` accept the already-supported `experimental` authorization options in their public types.

**Oct 27, 2026**

The Python Gemini provider no longer executes a manually handled function call as whichever user fetched the tools last

## Gemini Manual Function Calling Runs as the Right User

With Automatic Function Calling turned off, `GeminiProvider.handle_response(response)` in `composio-gemini` executed each function call with the executor stored by the latest `tools.get()` or `session.tools()` for that tool. When one `Composio` instance served several users, a call from Alice's conversation could run with Bob's `user_id` and connected account, and Bob's result went back into Alice's chat. The callables used by Automatic Function Calling were not affected.

### Bug Fixes

* **Gemini** (`composio-gemini`): `handle_response` accepts `user_id=` or `session=`, with the same names as `GoogleProvider.handle_response` in `composio-google`. Each call runs exactly as the tool fetched for that user or Tool Router session would: validated against the schema from that fetch (including its schema modifiers), with the modifiers given to `tools.get()`, and through the session's routing, so local custom tools in a `COMPOSIO_MULTI_EXECUTE_TOOL` batch run in process.
* Without a user or session, `handle_response` keeps working for a process that has fetched tools for a single user or session. Once the provider has wrapped tools for more than one, it raises a `ValueError` instead of picking one, and executes nothing.

**Before:**

```python theme={null}
alice_tools = composio.tools.get(user_id="alice", tools=["GMAIL_FETCH_EMAILS"])
bob_tools = composio.tools.get(user_id="bob", tools=["GMAIL_FETCH_EMAILS"])

# response comes from Alice's conversation
composio.provider.handle_response(response)
# The tool executed as bob
```

**After:**

```python theme={null}
composio.provider.handle_response(response, user_id="alice")
# The tool executes as alice

composio.provider.handle_response(response)
# ValueError: tools were wrapped for more than one user or session
```

**Oct 22, 2026**

Require a CA bundle without the compromised eMudhra root, and cap third-party dependency ranges. Get toolkit sunset warnings, preserve tool arguments across Python providers, and migrate direct HTTP clients. Block tool calls or results with session hooks, inspect hook outcomes, and handle blocked proxy requests. Get toolkit sunset warnings, preserve tool schemas across TypeScript providers, and migrate direct API client access.

## Python SDK 0.29.1: certificate and dependency hardening

This patch release hardens how the Python SDK and its providers resolve dependencies. It has no API changes.

### Release versions

| SDK | Version |
| - | - |
| Python `composio` | `0.29.1` |

All 13 Python provider packages are released at `0.29.1`.

### What's changed

* **`certifi>=2026.10.19` is now required.** That bundle removes the emSign ECC Root CA - G3 root after eight eMudhra intermediate keys were compromised. Older bundles still trust certificates issued under it.
* **Third-party dependencies have upper bounds.** Each range stops before the first major version that wasn't released yet when the cap was set, or before `1.0` for packages still on `0.x`. A future major line can't install until the SDK raises the cap. Ranges can still span majors that already exist: `openai>=2.48.0,<4` allows 2.x and 3.x, and `anthropic>=0.120.0,<3` allows 0.x through 2.x. `certifi` stays uncapped so CA bundle updates always install.
* **`pysher` is pinned to `1.0.8`.** The trigger client depends on it, and it has had no release since 2022. Its transport is capped at `websocket-client<2`.
* **Releases come from a locked build.** Packages are built only from locked dependencies and published with PyPI trusted publishing, so each file on PyPI carries an attestation linking it to the GitHub workflow that built it.

Every cap sits above the newest release available today, so existing installs resolve the same versions as before.

## Python SDK 0.29.0: toolkit warnings and provider argument fixes

The Python SDK now warns when the API reports that a toolkit version you use is deprecated. This release also fixes tool argument serialization and preserves more of your schemas across providers.

### Release versions

| SDK | Version |
| - | - |
| Python `composio` | `0.29.0` |

All 13 Python provider packages are released at `0.29.0`.

### What's new

* **Toolkit deprecation warnings.** The SDK warns once per process for each deprecated toolkit version reported through the `Composio-Deprecated-Toolkits` response header. The warning names the version, its sunset date, and how to pin a newer version. See [toolkit versioning](https://composio-preview.mintlify.site/docs/tools-direct/toolkit-versioning.md#deprecation-and-sunset).

### Migration notes

> [!WARNING]
>
> Direct construction of `composio.client.HttpClient` now takes `auth` and `scope` instead of credential keywords and scope headers. It no longer accepts `default_query`. The main `Composio(api_key=...)` constructor keeps its credential options, and Python still reads `COMPOSIO_CUSTOM_HEADERS`.

If you construct `HttpClient` directly, replace the credential keywords with an `auth` value:

Before: `HttpClient(provider="openai", api_key=key)`.

After: `HttpClient(provider="openai", auth=ProjectAuth(key))`, importing `ProjectAuth` from `composio_client`.

For organization and project routing, replace scope headers with `scope=Scope(organization_id=org_id, project_id=project_id)`, importing `Scope` from `composio_client`. Remove `default_query` from direct client construction.

### Bug fixes

* **Pydantic aliases.** Tool execution serializes Pydantic arguments with their declared aliases, including nested models and explicit serialization aliases.
* **Provider arguments.** AutoGen and Google ADK preserve and validate free-form arguments instead of dropping them. OpenAI Agents preserves the source schema's `additionalProperties`. See the [provider behavior changes and limitations](https://composio-preview.mintlify.site/docs/changelog/2026/10/20).
* **Google ADK nested arrays.** The provider preserves nested array item schemas instead of replacing them with a flat string schema.

## SDK releases: session hooks in Python 0.30.0 and TypeScript 0.27.0

You can now attach hooks to a session to block a tool call before it runs or block its result before your agent sees it.

### Release versions

| SDK | Version |
| - | - |
| Python `composio` | `0.30.0` |
| TypeScript `@composio/core` | `0.27.0` |
| TypeScript `@composio/slim` | `0.27.0` |
| TypeScript `@composio/anthropic` | `0.11.6` |

All 13 Python provider packages are released at `0.30.0`.

### What's new

* **Session hooks.** Pass `hooks` when you create or update a session. Hooks can run before execution or after execution, and can apply to selected toolkits. Updating `hooks` replaces the whole list; `None` in Python or `null` in TypeScript removes every hook. You cannot combine `hooks` with `experimental.session_config_id` in Python or `experimental.sessionConfigId` in TypeScript in the same call.
* **Hook outcomes.** Session execution returns `result_type="blocked"` in Python or `resultType: 'blocked'` in TypeScript when a hook blocks a call or result. The response contains empty `data`, the hook's message in `error`, and `block_reason` or `blockReason`. When hooks apply, inspect `hook_results` or `hookResults` for their outcomes. Provider integrations return blocked execution as a failed tool call with the hook's message.

### Migration notes

> [!WARNING]
>
> Session proxy execution now distinguishes completed requests from blocked requests. A blocked request has no HTTP response. Check the result type before reading HTTP response fields.

In Python, replace direct access to a proxy response's `status` with a result-type check:

Before: `print(response.status)`.

After: `print(response["status"] if response["result_type"] == "completed" else response["message"])`.

In TypeScript, make the equivalent check:

Before: `console.log(response.status)`.

After: `console.log(response.resultType === 'completed' ? response.status : response.message)`.

This applies to `session.proxy_execute()` and `ctx.proxy_execute()` in Python, and `session.proxyExecute()` and `ctx.proxyExecute()` in TypeScript.

### Bug fixes

* **Python custom-tool annotations.** `@composio.experimental.tool` reports unresolved input annotations when you register the tool, with the affected parameter and the original resolution error.
* **Anthropic provider dependencies.** The TypeScript Anthropic provider removes its unused `@mastra/mcp` peer dependency, avoiding unrelated packages during installation.

## TypeScript SDK 0.26.0: toolkit warnings and provider schema fixes

The TypeScript SDK now warns when the API reports that a toolkit version you use is deprecated. This release also preserves more of your tool schemas and arguments across providers.

### Release versions

| SDK | Version |
| - | - |
| TypeScript `@composio/core` | `0.26.0` |
| TypeScript `@composio/slim` | `0.26.0` |
| TypeScript `@composio/json-schema-to-zod` | `0.4.0` |
| TypeScript `@composio/claude-agent-sdk` | `0.13.0` |
| TypeScript `@composio/vercel` | `0.13.0` |
| TypeScript `@composio/llamaindex` | `0.11.2` |

### What's new

* **Toolkit deprecation warnings.** The SDK warns once per process for each deprecated toolkit version reported through the `Composio-Deprecated-Toolkits` response header. The warning names the version, its sunset date, and how to pin a newer version. See [toolkit versioning](https://composio-preview.mintlify.site/docs/tools-direct/toolkit-versioning.md#deprecation-and-sunset).
* **Zod v4 schema builder.** Import `jsonSchemaToZod` or `jsonSchemaToZodShape` from `@composio/json-schema-to-zod/v4` to build classic Zod v4 schemas. The root entry continues to build Zod v3 schemas. The v4 builder requires Zod `4.1.13` or newer and preserves schema annotations in metadata for `z.toJSONSchema()`.
* **Provider schema preservation.** The TypeScript Vercel and LlamaIndex providers now give the model the tool's JSON Schema directly, preserving keywords such as `format`, `contentEncoding`, and `contentMediaType`. Claude Agent SDK uses the new Zod v4 builder to preserve those annotations. Existing tool argument validation stays in place.

### Migration notes

> [!WARNING]
>
> This release changes direct API client access, TypeScript Vercel tool schemas, and the Claude Agent SDK provider's minimum Zod version. Apply the relevant steps below before upgrading.

1. **TypeScript client access.** Read credentials from `composio.getConfig()` instead of `composio.getClient().apiKey`, `.userApiKey`, or `.orgApiKey`. The client also removes `.logger`. Its `baseURL`, `maxRetries`, `timeout`, and `logLevel` are read-only; derive a client with `withOptions()` to change them. For example, replace `composio.getClient().maxRetries = 0` with `const client = composio.getClient().withOptions({ maxRetries: 0 })` and use the derived client for those calls.
2. **TypeScript custom headers.** Replace `COMPOSIO_CUSTOM_HEADERS` with the SDK's `defaultHeaders` option. Credential and scope headers in `defaultHeaders` or `createSession({ headers })` are folded into SDK configuration and no longer appear under `getConfig().defaultHeaders`. Supply at most one of `x-api-key`, `x-user-api-key`, or `x-org-api-key`; multiple credential headers now throw. Per-call client headers cannot override credentials or scope. With `apiKey: null` and only an organization API key, API calls, trigger authorization, and `session.mcp.headers` now consistently carry `x-org-api-key`.
3. **Vercel tool schemas.** `tool.inputSchema` is now an AI SDK `Schema`. Replace direct `tool.inputSchema.safeParse(value)` calls with `asSchema(tool.inputSchema).validate(value)`, importing `asSchema` from `ai`.
4. **Claude Agent SDK and Zod v4.** Upgrade Zod to `4.1.13` or newer before upgrading `@composio/claude-agent-sdk`. Older Zod v4 versions do not provide the shared metadata registry the builder needs.
5. **Deprecated TypeScript connection data.** For `customConnectionData` with `S2S_OAUTH2`, supply `val.access_token`, which the API requires.

### Bug fixes

* **Strict TypeScript tool schemas.** OpenAPI `nullable` is converted into a nullable type or a null branch. Unsupported string formats, including `uri`, custom formats, and `path`, are removed before strict requests reach the model provider. This prevents a single tool schema from causing the whole request to fail.
* **String argument validation.** TypeScript checks a string as base64 only when its `contentEncoding` is `base64`. Fields with `format: "binary"` or another encoding, such as `base16`, accept plain strings instead of being rejected as invalid base64.
* **Zod v3 validation paths.** Errors inside nested object properties report each property name once, including errors from `patternProperties`, `additionalProperties`, and `oneOf`.

**Oct 21, 2026**

Failed tool executions and invalid input now exit 1, the CLI calls the backend you logged in to, and `composio execute` goes through the Composio Dashboard.

## CLI 0.5.0 exits 1 on failed executions and runs `composio execute` through the Composio Dashboard

CLI 0.5.0 is a minor release because of one breaking change: commands that failed but exited 0 now exit 1. It also fixes staging and custom-backend logins, and sends `composio execute` through the Composio Dashboard. You don't need to log in again or change any configuration.

### Release versions

| SDK | Version |
| - | - |
| CLI `composio` | `0.5.0` |

### Breaking changes

* **Failed executions exit 1.** `composio execute` now exits 1 when a tool execution fails: the tool reported a failure, the Dashboard or backend couldn't run it, or, with `--parallel`, any one of the calls failed. Meta tools behave the same. It used to exit 0. The `{"successful": false, ...}` JSON on stdout and the messages on stderr are unchanged. In `composio run`, `execute()` still rejects with the tool's error message and the failed result.
* **Invalid input exits 1.** These commands now exit 1 instead of 0 when their input is missing or invalid. They print the same message on stderr, nothing on stdout, and send no request:
  * `composio dev auth-configs info` without an `<id>`
  * `composio dev auth-configs create` with `--custom-credentials` that isn't a JSON object
  * `composio tools info` without a `<slug>`
  * `composio dev triggers create` without a `<trigger-name>`, or with `--trigger-config` that isn't a JSON object
  * `composio dev triggers enable` without an `<id>`
* **`composio orgs switch` without a usable key exits 1.** When the stored API key is empty, `composio orgs switch` now exits 1 and asks you to run `composio login`, instead of warning and exiting 0. It changes nothing either way.

If a script or agent checks the exit code, it now sees these failures. If it relied on exit 0 after a failed execution, handle exit 1 instead.

### Improvements

* **The CLI calls the backend you logged in to.** `composio login` records the backend that issued your key, but commands used to call production unless `COMPOSIO_BASE_URL` or `COMPOSIO_ENVIRONMENT` was set, so a staging login failed with `Invalid or revoked user API key`. Those variables still win when set, and the CLI warns on stderr when one sends your stored key to a different backend. `composio execute` uses the Dashboard recorded with the same login. A rejected key now prints the command to log in again.
* **Unmatched `--account` is a usage error.** When `--account` matches no connected account, `composio execute` and `composio proxy` print one line on stderr and exit 1, instead of a crash report.
* **`composio execute` goes through the Dashboard.** Single executions, `--parallel` executions, and meta tools all use the Dashboard at `https://dashboard.composio.dev`. Output, error details, connection tips, and `--json` shapes stay the same. If the backend is unavailable, the CLI shows the Dashboard's error message. If your network restricts outbound hosts, allow `dashboard.composio.dev` as well as `backend.composio.dev`. Every other command, including `composio dev playground-execute`, still calls the backend API.
* **Executions are sent once.** The CLI sends each execution request once, without retrying or following redirects. After 15 minutes it stops waiting and reports that the tool may still have run.
* **Custom deployments.** If you set `COMPOSIO_BASE_URL` without `COMPOSIO_WEB_URL`, `composio execute` keeps calling that backend. To use a deployment's Dashboard, set both. `COMPOSIO_WEB_URL` must be an `https://` URL without credentials, a query string, or a fragment (`http://` is accepted only for `localhost`). Otherwise `composio execute` fails before sending anything.
* **Telemetry install ID.** When telemetry is enabled, `composio execute` sends the CLI's anonymous install ID, the random UUID stored in `~/.composio/analytics.json`, to the Dashboard in an `x-cli-install-id` header. The header is never sent to the backend API. It isn't sent when you set `COMPOSIO_CLI_TELEMETRY_DISABLED`, `TELEMETRY_DISABLED`, `COMPOSIO_DISABLE_TELEMETRY`, or `CI`.
* **Clearer `composio link` messages.** `composio link` and `composio dev connected-accounts link` reword their usage errors and their waiting and timeout lines on stderr. Exit codes and the JSON on stdout are unchanged.
* **API client.** The CLI uses `@composio/client` `2.0.0-rc.19`. Commands are unchanged.

**Oct 20, 2026**

The Python AutoGen and Google ADK providers no longer drop free-form tool arguments, and OpenAI Agents stops telling the model that open arguments are closed

## Free-Form Arguments Reach Execution in AutoGen, Google ADK, and OpenAI Agents

A tool argument that accepts arbitrary keys, such as an object with no `properties`, `additionalProperties: true`, or `patternProperties`, could reach your tool as `{}` in the Python AutoGen and Google ADK providers. No input error was raised, so the tool ran with different arguments from the ones the model sent.

LangChain, LangGraph, and CrewAI were fixed in Python `0.19.0` (see [Free-Form Object Arguments Are Preserved Across SDKs](https://composio-preview.mintlify.site/docs/changelog/2026/08/06)). This release covers the remaining agentic providers.

### Bug Fixes

* **AutoGen** (`composio-autogen`): both runtime paths, `autogen_core` tools and AG2's `register_tools`, now pass every key the tool schema allows to execution and validate it with the same rules as LangChain and CrewAI. The advertised tool schema now marks the top-level object as open when the source schema does.
* **Google ADK** (`composio-google-adk`): top-level keys the tool schema allows are no longer filtered down to named parameters, and arguments are validated before execution.
* **OpenAI Agents** (`composio-openai-agents`): the advertised top-level schema keeps the source's `additionalProperties` instead of always setting it to `false`. A schema that declares no properties is advertised as open, matching the TypeScript provider.

**Before:**

```python theme={null}
# tool comes from Composio(provider=AutogenProvider()).tools.get(...)
# its input schema is {"type": "object", "properties": {}}
await tool.run_json({"filters": {"status": "open"}}, CancellationToken())
# The tool executed with {}
```

**After:**

```python theme={null}
await tool.run_json({"filters": {"status": "open"}}, CancellationToken())
# The tool executes with {"filters": {"status": "open"}}
```

### Behavior Change for AutoGen and Google ADK

> [!WARNING]
>
> AutoGen and Google ADK now validate tool arguments against the tool's JSON schema, as LangChain, LangGraph, and CrewAI already do. Calls that used to succeed after the provider silently dropped or converted a value now return an error result to the agent: `{"successful": false, "error": "...", "data": null}`.

* An unknown top-level key on a schema that declares properties and omits `additionalProperties` is rejected instead of dropped.
* A value of the wrong type, such as `"5"` for an integer, is rejected instead of converted.
* An optional argument the model leaves out is no longer sent as `""`, `0`, or `{}`. The schema's declared default applies instead.
* An invalid `patternProperties` or schema-valued `additionalProperties` raises when the tool is wrapped.

### Known Limitation

On Google ADK and on AutoGen's AG2 `register_tools` path, the tool declaration is still built from named parameters. A tool whose whole argument object is free-form is therefore not advertised to the model as open, so the model may not send those keys. Free-form objects nested under a declared argument work on every provider.

**Oct 16, 2026**

Require approval before session tools run, answer input requests in both SDKs, and avoid retrying CLI mutations.

## Session tool approvals, Python 3.15 support, and CLI request fixes

You can now require approval before selected session tools run and send the answers back through either SDK.

### Release versions

| SDK | Version |
| - | - |
| Python `composio` | `0.28.0` |
| TypeScript `@composio/core` | `0.25.0` |
| TypeScript `@composio/slim` | `0.25.0` |
| CLI `composio` | `0.4.5` |

All 13 Python provider packages are released at `0.28.0`.

### What's new

* **Session tool approvals.** Set `requireApproval` (`require_approval` in Python) on session toolkit, tool, or tag filters. When a call needs input, catch `ComposioToolInputRequiredError` (`ToolInputRequiredError` in Python), display its `inputRequests` (`input_requests`), and wait for the person's answers. Repeat the call with `inputResponses` and `requestState` (`input_responses` and `request_state`). Forward decline and cancel answers unchanged. Both tool execution and meta-tool execution support this flow.
* **MCP approval fallback.** Set `experimental.noElicitationSupportFallback` (`experimental.no_elicitation_support_fallback` in Python) to `deny` or `allow` to choose what happens when the MCP client cannot ask for approval.
* **Python versions.** The Python SDK supports Python 3.11 through 3.15.

### Migration notes

> [!WARNING]
>
> TypeScript `session.executeMeta()` now takes input-response options as its third argument. Move request options to the fourth argument.

Before: `session.executeMeta(slug, args, requestOptions)`.

After: `session.executeMeta(slug, args, undefined, requestOptions)`.

Both SDKs now pass product and runtime identity through the API client's `identity` option. Remove identity headers such as `x-source`, `x-framework`, `x-sdk-version`, and `x-client-*` from custom default or request headers: the client now rejects attempts to override its identity headers instead of silently replacing them. In TypeScript, Cloudflare Workers and Vercel Edge with Node.js compatibility enabled report their actual runtime, and custom provider names that cannot be sent as header values are reported as `unknown`.

### Bug fixes

* **TypeScript trigger subscriptions.** `triggers.unsubscribe()` closes the realtime connection, cancels an in-progress subscription, and does not create a connection when called before subscribing. Concurrent subscriptions share a connection. Rejected asynchronous trigger handlers are logged without becoming unhandled rejections.
* **CLI request handling.** Only API reads that are safe to repeat are retried. Mutating calls are sent once, preventing a timeout from repeating a side effect. Commands validate the response fields they use while tolerating unrelated API changes.
* **CLI command errors.** Commands that require login report a consistent usage error. Project-resolution failures retain their specific error type. The `dev` group's `--user-id` and `--project-name` flags work before or after the subcommand, and unsupported flags fail with a usage error.

**Oct 15, 2026**

Add a locale parameter to the Connect Link URL to show the hosted connection page in your user's language.

## Show the Connect Link in Spanish or Simplified Chinese

The Connect Link can now show its text in Spanish or Simplified Chinese. Add `?locale=es` or `?locale=zh-CN` to the `redirect_url` before you send it to the user, and the whole flow, including the success and failure screens, uses that language.

For now, only `en`, `es`, and `zh-CN` are supported. Links without `locale`, or with any other value, show English. See [White-labeling authentication → Language](https://composio-preview.mintlify.site/docs/authentication/white-labeling-authentication.md#language) for examples.

**Oct 14, 2026**

Execute Composio meta tools from a Session, configure proxy execution, and inspect Instant tool prices in search results.

## Python SDK 0.27.0 and TypeScript SDK 0.24.0 add Session meta-tool execution and Instant search prices

You can now execute Composio meta tools directly from a Session in both SDKs, enable proxy execution when creating or updating a Session, and request Instant tool prices in search results.

### Release versions

| SDK | Version |
| - | - |
| Python `composio` | `0.27.0` |
| TypeScript `@composio/core` | `0.24.0` |
| TypeScript `@composio/slim` | `0.24.0` |

All 13 Python provider packages are released at `0.27.0`. This release also publishes `@composio/experimental` `0.2.8`, `@composio/anthropic` `0.11.5`, `@composio/claude-agent-sdk` `0.12.2`, `@composio/langchain` `0.11.2`, `@composio/mastra` `0.10.6`, and `@composio/openai-agents` `0.11.2`.

### What's new

* **Execute meta tools.** Use `session.executeMeta()` in TypeScript or `session.execute_meta()` in Python to run a `COMPOSIO_*` meta tool with a slug and optional arguments. The response includes `resultType` (`result_type` in Python), and input requests raise `ComposioToolInputRequiredError` (`ToolInputRequiredError` in Python). Calls are sent once without retries. The exported `ToolRouterSessionMetaToolSlug` type lists the accepted slugs.
* **Configure Session proxy execution.** Pass `proxyExecute: true` when creating a TypeScript Session, or `proxy_execute=True` in Python, to expose `COMPOSIO_PROXY_EXECUTE`. The option also accepts an object with `enable`, and you can change it through `session.update()`. Set it to `false` (`False` in Python) to disable the sandbox's `proxy_execute()` helper too. Set it to `null` (`None` in Python) when updating to remove the stored setting. The API rejects a disabled proxy setting combined with an enabled sandbox proxy setting at creation.
* **Inspect Instant prices in search.** The experimental `instant.returnPricesInSearch` Session option (`instant.return_prices_in_search` in Python) returns each Instant tool's price under `toolkitConnectionStatuses[].instantAccount.prices` (`toolkit_connection_statuses[].instant_account.prices` in Python). You can set it when creating or updating a Session.
* **Filter by hint tags.** Session tag filters accept `createHint` and `updateHint`.

### Bug fixes

* **Python trigger listeners.** `wait_forever()` keeps waiting through recoverable network drops while Pysher reconnects, and returns when the connection worker stops. `restart()` requests a reconnect on the running worker.

### Improvements

* **API client types.** The updated API clients accept a `null` `id_token` in OAuth connection data types. TypeScript's SDK connection-state validation is unchanged.
* **Provider compatibility.** TypeScript provider peer ranges accept Anthropic SDK `0.132` and OpenAI Agents `0.20`. The experimental provider also accepts Pi coding-agent `1.x`.

### Deprecations

`composio.mcp.generate()` now warns once that its URLs depend on the deprecated `include_composio_helper_actions` query parameter. Use a Session's MCP endpoint instead.

**Oct 12, 2026**

Session tools that need user input raise a typed error, Session executions are sent once, and schema patterns run on a linear-time regex engine.

## Python SDK 0.26.0 and TypeScript SDK 0.23.0 report input requests and stop retrying Session executions

Both SDKs move to the `2.0.0-rc.11` API client. A Session tool that needs user input now raises a typed error instead of returning an empty result, Session executions are no longer retried, and tool schema patterns run on a linear-time regex engine.

### Release versions

| SDK | Version |
| - | - |
| Python `composio` | `0.26.0` |
| TypeScript `@composio/core` | `0.23.0` |
| TypeScript `@composio/slim` | `0.23.0` |

This release also publishes `@composio/anthropic` `0.11.4`, `@composio/json-schema-to-zod` `0.3.4`, and `@composio/experimental` `0.2.7`. The Python provider packages are released at `0.26.0`.

### Breaking changes

> [!WARNING]
>
> **Breaking Change**
>
> Session config and execution types now come from the API client, and Python's Instant values are models instead of dictionaries.

**TypeScript**

* `ToolRouterSessionConfig` (`session.config`, the result of `session.update()`) and `ToolRouterSessionConfigHistoryConfig` (`session.listConfigHistory()`) are the client's own types. `instant` is always present, as `false` or the policy object.
* In those types, `toolkits` and each `tools` entry can be a `{ require_approval }`-only object, so a check for `enabled` or `disabled` no longer covers every case. `tags` can carry `require_approval`, and the config can carry `proxy_execute`.
* The Session config is returned as the API sent it. The SDK no longer validates `instant` at runtime or removes a `premium_usage` key.
* `ToolRouterSessionExecuteResponse` requires `resultType`. A custom `ToolCallSession` passed to a provider must return it from `execute()`, because `successful` is no longer derived from `error`.
* `ToolRouterInstantResponseSchema` and `ToolRouterInstantResponse` are no longer exported. Use `ToolRouterSessionConfig['instant']`.

**Python**

* `session.execute().instant_charge` and `session.config.instant` are models, not dictionaries.
* `ToolRouterSessionExecuteResponse` and `ToolRouterSessionSearchResponse` alias the client's classes. `ToolRouterInstantResponse`, `ToolRouterInstantResponseEnable`, `ToolRouterInstantResponseDisable`, and `ToolRouterInstantAccount` are gone from `composio.core.models.tool_router_session`. The input types `ToolRouterInstantConfig`, `ToolRouterInstantEnable`, and `ToolRouterInstantDisable` are unchanged.
* `ToolExecuteParams` no longer has `allow_tracing` and `entity_id`, which were never sent to the API.

**Before:**

```python theme={null}
result = session.execute("EXA_SEARCH", arguments={"query": "composio"})
amount = result.instant_charge["amount"]
```

**After:**

```python theme={null}
result = session.execute("EXA_SEARCH", arguments={"query": "composio"})
amount = result.instant_charge.amount
```

To migrate:

1. In Python, replace dictionary access on Instant charges and the Session `instant` policy with attribute access.
2. In TypeScript, return `resultType` (`'completed'` or `'failed'`) from any custom `ToolCallSession.execute()`.
3. Where you inspect a Session config, handle `toolkits` and `tools` entries that only carry `require_approval`.

### What's new

* **Input requests.** A Session tool can ask for user input, such as an approval, instead of running. `session.execute()`, `session.proxyExecute()` (`session.proxy_execute()` in Python), provider-wrapped Session tools, and the helpers passed to custom tools raise `ComposioToolInputRequiredError` in TypeScript and `ToolInputRequiredError` in Python. The error carries the questions on `inputRequests` (`input_requests`) and the opaque continuation state on `requestState` (`request_state`), which is kept out of logs and serialized output. Nothing was executed and the call is not retried. The SDKs do not submit answers yet.
* **Execution result type.** Session executions report `resultType` in TypeScript and `result_type` in Python as `completed` or `failed`. Read it rather than `error` to tell a failure from a success: a failed execution can carry an empty `error`, and it is no longer reported as successful.
* **`user_id` on direct proxy calls.** `composio.tools.proxyExecute()` accepts `userId` and Python's `composio.tools.proxy()` accepts `user_id`. Projects with 2FA enabled check it against the connected account and may require it.
* **Python Anthropic tool caching.** `AnthropicProvider(cache_tools=True)` attaches Anthropic's ephemeral `cache_control` to the last tool definition, which caches the whole tool list.
* **Python OpenAI Agents strict mode.** `OpenAIAgentsProvider(strict=True)` registers tools with schemas normalized for structured outputs. A schema strict mode cannot express falls back to the non-strict path.

### Bug fixes

* **Session executions are sent once.** `session.execute()`, `session.proxyExecute()`, provider-wrapped Session tools, and the custom tool helpers no longer retry after a timeout, a connection error, or a `408`, `409`, `429`, or `5xx` response, so a retry cannot repeat a side effect such as sending the same email twice. This matches `tools.execute()` and `tools.proxyExecute()`. The experimental workbench helper `run_composio_tool` follows the same rule and reports failed and input-required answers as errors.
* **Linear-time schema patterns.** Tool schema `pattern` and `patternProperties` regexes run on a linear-time engine in both SDKs, so a pattern such as `^(a+)+$` can no longer hang argument validation. A `patternProperties` key that needs lookaround or a backreference fails conversion.
* **Strict mode with optional enums.** Optional `enum` and `const` parameters, `type` beside `anyOf`, and `$ref` with sibling keywords are wrapped whole in `anyOf` with a `null` branch, so the model can omit them under strict mode.
* **Portable file names.** Server-provided file names with characters Windows reserves, such as `report_2026-09-29T10:30:00.csv`, are saved with those characters replaced instead of being rejected. Default saves never overwrite an existing file. Python automatic downloads follow validated redirects again.
* **Object-rooted tool schemas in TypeScript.** Parameters that use `anyOf`, `oneOf`, `allOf`, or `$ref` convert to a `ZodObject` again, so the LangChain, Vercel, LlamaIndex, and Claude Agent SDK providers send a top-level `type: "object"`.
* **Anthropic cache breakpoints in TypeScript.** `cacheTools: true` places a single breakpoint on the last tool and no longer marks `tool_result` blocks, staying within Anthropic's limit of 4 breakpoints per request.
* **Gemini automatic function calling in Python.** Tools with optional or constrained arguments run through automatic function calling again.

### Improvements

* Both SDKs send product identity, product version, language, and runtime version with API requests. `@composio/core` and `@composio/slim` are identified separately.

**Sep 29, 2026**

Use Instant account selection and charge details in both SDKs, with Session-aware provider helpers and connection fixes. The project setting that stopped payload storage is now Zero Data Retention, an organization add-on in Billing. Every project kept its setting.

## Python SDK 0.25.0 and TypeScript SDK 0.22.0 align Instant Sessions

Both SDKs now use the Instant Session and account contracts. Tool execution and usage responses expose exact Instant charges, and provider helpers can execute tools through a supplied Tool Router Session.

### Release versions

| SDK | Version |
| - | - |
| Python `composio` | `0.25.0` |
| TypeScript `@composio/core` | `0.22.0` |
| TypeScript `@composio/slim` | `0.22.0` |

### Instant Sessions and charges

* Configure Instant access with `instant` and request execution charge details with `instant.returnInstantCharge` in TypeScript or `instant.return_instant_charge` in Python. The former `premium_usage` and `return_premium_charge` names are replaced by the Instant contract.
* Read `instantCharge` in TypeScript or `instant_charge` in Python from Session execution results. Project usage summaries expose the exact USD amount as a string; charged tool logs include `metadata.instant_charge`.
* Select an Instant account with `instant_account` in the Session API contract. Session search results describe available Instant tools through `instantAccount` in TypeScript or `instant_account` in Python.

### Provider helpers and fixes

* Google, Cloudflare, and OpenAI Responses helpers in TypeScript, and the Google Gemini helper in Python, accept a Tool Router Session for execution. Existing user ID calls continue to use direct execution.
* TypeScript `ConnectionRequest.status` now follows the result of `waitForConnection()`, and telemetry records calls to `waitForConnection()`.
* The OpenAI provider no longer includes Assistants API helpers. Move Assistants integrations to the Responses API and `OpenAIResponsesProvider` from `@composio/openai`.

## Don't store data is now Zero Data Retention

The **Don't store data** option under **Log storage** is now **Zero Data Retention** (ZDR). You manage it as an organization add-on in **Organization Settings > Billing > Add-ons**. Every project kept its setting, so projects that had **Don't store data** on now show ZDR on.

### What's new

* An organization admin can turn on ZDR for all projects at once. Admins can also turn it on or off for one project in **Project Settings > General**.
* ZDR is available on paid plans for a usage-based price and included on Enterprise, where new projects start with ZDR on. Hobby plan projects that already had **Don't store data** keep ZDR on until an admin turns it off.
* The [Zero Data Retention](https://composio-preview.mintlify.site/docs/security/zero-data-retention.md) page lists what ZDR covers, what it does not cover, and what Composio still stores.

**Sep 24, 2026**

Control premium usage in both SDKs, use saved Session configs in TypeScript, and get fixes for Session updates and file downloads.

## Python SDK 0.24.0 and TypeScript SDK 0.21.0 add Session policies and fixes

Both SDKs add experimental premium usage policies and fix default Session updates. TypeScript also adds saved Session configs and hosted-account details in search results.

### Release versions

| SDK | Version |
| - | - |
| Python `composio` | `0.24.0` |
| TypeScript `@composio/core` | `0.21.0` |
| TypeScript `@composio/slim` | `0.21.0` |

### Premium usage policies

Set `premiumUsage` in TypeScript or `premium_usage` in Python when creating or updating a Session to control billed tool execution. Pass `false` (`False` in Python) to disable it, or a policy object to restrict eligible toolkits and tools. Your project must allow premium usage. Passing a policy object re-enables premium usage on a Session where it was disabled.

In Python, set `premium_usage.return_premium_charge` to receive charge details when available. `session.execute()` exposes them through the typed `premium_charge` field on `ToolRouterSessionExecuteResponse`. Provider integrations and mixed local/remote multi-tool execution preserve these details. The exported `PremiumCharge` type includes `amount`, `currency`, and `charged_by`.

### Saved Session configs in TypeScript

* Read saved configs with `composio.sessionConfigs.list()` and `composio.sessionConfigs.get()`.
* Apply a saved config through `experimental.sessionConfigId` when creating or updating a Session. Read its source metadata through `session.experimental.sourceSessionConfig`.
* Config IDs cannot be combined with inline access fields: `toolkits`, `tools`, or `tags`, plus `experimental.customTools` and `experimental.customToolkits` on create. Invalid combinations fail before a request is sent.
* Search results expose `hostedAccount.allowedToolSlugs` on toolkit connection statuses for Composio hosted accounts.

### Fixes

* **Session updates in both SDKs:** `session.update()` no longer sends `expected_config_version` by default, fixing the API's rejection of ordinary updates. Updates use last writer wins. To request a conditional update where the API supports it, pass `expectedConfigVersion` in TypeScript or `expected_config_version` in Python explicitly.
* **File saves in both SDKs:** unsafe server-supplied mount paths now raise validation errors before creating directories or writing files. This includes paths that resolve to a directory or its parent and filenames with trailing dots exposed by stripping Unicode whitespace.
* **TypeScript downloads:** `RemoteFile.save()` validates its default destination before downloading content, so an invalid mount path fails without a network request.
* **Python auth configs:** update, delete, enable, and disable methods now declare the client's concrete response types, including their `success` and `message` fields.

**Sep 22, 2026**

Both SDKs now use a faster handrolled client, expose more v3.1 APIs, and tighten authentication and session updates.

## Python SDK 0.23.0 and TypeScript SDK 0.20.0 add a faster API client

Python SDK `0.23.0` and TypeScript SDK `0.20.0` replace the old autogenerated client with a new handrolled one. Its lightweight HTTP transport is substantially faster while preserving the SDK APIs you already use. The client also covers more of Composio's v3.1 API.

### Release versions

| SDK | Version |
| - | - |
| Python `composio` | `0.23.0` |
| TypeScript `@composio/core` | `0.20.0` |
| TypeScript `@composio/slim` | `0.20.0` |

### Faster API requests

The new client reduces request overhead without changing existing imports, types, retries, timeouts, error classes, raw responses, streaming responses, or `AbortSignal` support. TypeScript users also get configurable SDK logging through `logger` and `logLevel`; Python routes client deprecations through `ComposioDeprecationWarning`.

### More of the Composio API

* Project webhooks (`webhooks.subscriptions` and `webhooks.endpoints`), tool execution logs, customer-managed keyring transfer keys, experimental usage metering, and experimental project-owned custom toolkits.
* Connected account revocation and deferred OAuth completion.
* Toolkit bulk retrieval, changelogs, OAuth scope recommendations, and grant contexts. Toolkit auth details now include each field's end-user visibility and the scopes an auth method always requests.
* Tool Router session configuration history through `session.listConfigHistory()` in TypeScript and `session.list_config_history()` in Python.
* `userApiKey` and `orgApiKey` in TypeScript, and `user_api_key` and `org_api_key` in Python, for user- and organization-scoped operations.

### Safer authentication and session updates

You can now authenticate without a project key by setting `apiKey: null` in TypeScript or `disable_api_key=True` in Python, then supplying a user or organization API key. Consumer requests can be scoped with `orgId` and `projectId` in TypeScript or `org_id` and `project_id` in Python.

Session MCP configuration exports only the credential and project scope used for the session request, and only when the MCP URL has the same origin as the configured Composio API. `session.update()` now uses the session's last observed config version by default. Concurrent writes raise a typed conflict instead of silently overwriting a newer configuration, and nullable policy fields can remove stored overrides.

> [!WARNING]
>
> **Migration note**
>
> In TypeScript, `apiKey: null` now explicitly disables project-key fallbacks. If you want the SDK to fall back to `COMPOSIO_API_KEY` or the CLI config when an environment variable is missing, pass `undefined` or omit `apiKey` instead:
>
> ```typescript theme={null}
>   import { Composio } from '@composio/core';
>
>   const composio = new Composio({
>     apiKey: process.env.COMPOSIO_API_KEY,
>   });
> ```
>
> Session updates now reject stale writes with `ComposioSessionConfigConflictError` in TypeScript or `SessionConfigConflictError` in Python. Re-fetch the session and retry, or pass `expectedConfigVersion: false` (`expected_config_version=False` in Python) when you explicitly need last-writer-wins behavior.

> [!NOTE]
>
> `connectedAccounts.refresh()` is deprecated because the API deprecated its endpoint. The API also removed credential validation from refresh, so TypeScript now ignores `validateCredentials` and logs a warning when you set it.

**Sep 21, 2026**

You can now fetch up to 200 auth configs in a single request, up from the previous limit of 50. Fixed a bug where reading multiple toolkits required a write-scoped API key instead of a read-scoped one TypeSafe support for Python, TypeSafe fixes for TypeScript, session connection helpers, clearer SDK errors, and stricter network safeguards are now available.

## Auth Configs Fetch Limit Raised to 200

### Improvements

* Raised the auth configs fetch limit from 50 to 200, so teams with many configured auth providers can retrieve them all in a single call without pagination.

## Scoped API Keys: Tools Read Now Accepts Read-Scoped Keys

When creating a scoped API key through the API key creation flow, you can assign either read or write scope. Reading multiple toolkits at once was incorrectly requiring a write-scoped API key. This has been fixed to accept read-scoped keys as intended.

### Bug Fixes

* Fetching and listing tools across multiple toolkits previously required a write-scoped API key. The scope check was corrected so that read-scoped API keys are now accepted for these read operations.

### Backward Compatibility

This is a backward-compatible fix. Existing API keys with write scope continue to work exactly as before. Read-scoped keys can now be used for tools read operations without needing to upgrade to write scope.

## Python SDK 0.22.0 and TypeScript SDK 0.19.0 add safer TypeSafe and session workflows

Python SDK `0.22.0` adds a TypeSafe provider. TypeScript SDK `0.19.0` improves session and connection workflows, returns clearer errors, and strengthens network safeguards. The accompanying `@composio/typesafe` `0.1.1` release updates the package first published as `0.1.0` on September 17.

### Release versions

| SDK | Version |
| - | - |
| Python `composio` | `0.22.0` |
| Python `composio-typesafe` | `0.22.0` |
| TypeScript `@composio/core` | `0.19.0` |
| TypeScript `@composio/slim` | `0.19.0` |
| TypeScript `@composio/typesafe` | `0.1.1` |
| TypeScript `@composio/experimental` | `0.2.5` |

### TypeSafe support turns Jev decisions into Composio calls

The new `composio-typesafe` package and the existing `@composio/typesafe` package integrate Composio tools with TypeSafe's Jev model. They compile tools into typed questions, return a complete call, partial call, or abstention with a confidence score, and require explicit confirmation before destructive tool execution.

You can also shortlist tools before a decision and apply a confidence gate when a workflow needs a minimum judgement score.

TypeScript `0.1.1` rejects root schema composition that can hide required arguments, requires explicit values for prototype-named arguments, and preserves `__proto__` as caller data during execution.

### Sessions expose more state and avoid duplicate authorization

TypeScript sessions now expose the server-returned configuration through `session.config`. `session.update()` returns the updated configuration, and `session.ensureConnected()` reuses an active connection before starting a new authorization flow.

Python and TypeScript MCP updates now preserve tool-only allowlists, auth config selections, and manual connection-management intent. Python mixed local and remote multi-tool execution also preserves request order and retains completed local results when the remote request fails.

> [!NOTE]
>
> If you implement the TypeScript `Session` interface yourself, add the required `config` member. Sessions created by the SDK already provide it.

### Errors are easier to handle

Tool lookup failures now distinguish a missing tool from authentication, server, and network failures. Trigger subscription setup errors can be handled through a callback instead of escaping asynchronously, and HTTP status errors in Python remain catchable as `ComposioError`.

### Network safeguards cover redirects and transition ranges

Both SDKs now apply standard redirect method and body rules, remove credentials on cross-origin redirects, and reject additional IPv4, IPv6, and transition-network ranges. TypeScript also offers a strict SSRF mode for callers that require the connection to stay pinned to the validated address.

The TypeScript JSON Schema converter rejects invalid or oversized regular-expression patterns with a path-aware error. Provider dependency ranges have also moved to the upstream versions used by the release test matrix.

**Sep 4, 2026**

CLI 0.4.1, Python SDK 0.21.1, and TypeScript SDK updates keep credentials private, bound file downloads, improve JSON Schema conversion, and route custom tools predictably.

## CLI 0.4.1 and SDK updates protect credentials, file transfers, and JSON Schema behavior

CLI `@composio/cli` `0.4.1`, Python SDK `composio` `0.21.1`, and TypeScript SDK updates strengthen credential handling and file transfers. This release also improves JSON Schema conversion across Python and TypeScript, preserves referenced definitions across TypeScript providers, and makes custom tools with shared child slugs route predictably in both SDKs.

### Release versions

| Package | Version |
| - | - |
| CLI `@composio/cli` | `0.4.1` |
| Python `composio` | `0.21.1` |
| TypeScript `@composio/core` | `0.18.1` |
| TypeScript `@composio/slim` | `0.18.1` |
| TypeScript `@composio/experimental` | `0.2.4` |
| TypeScript `@composio/claude-agent-sdk` | `0.12.0` |
| TypeScript `@composio/google` | `0.11.0` |
| TypeScript `@composio/langchain` | `0.11.0` |
| TypeScript `@composio/llamaindex` | `0.11.0` |
| TypeScript `@composio/openai` | `0.12.2` |
| TypeScript `@composio/openai-agents` | `0.11.0` |
| TypeScript `@composio/vercel` | `0.12.0` |
| TypeScript `@composio/json-schema-to-effect-schema` | `0.1.1` |
| TypeScript `@composio/json-schema-to-zod` | `0.3.2` |

### Credentials stay private in files and logs

The CLI now creates user data, pending login sessions, and agent identity files with owner-only `0600` permissions. When it encounters a credential file created by an older CLI with broader `0644` permissions, it tries to repair the mode before reading the file. A permission-repair failure does not prevent a valid file from being read. Writes remain atomic, so tightening permissions does not trade away protection against partial files.

The Python and TypeScript SDKs now redact credential-shaped values at their shared log boundaries. Redaction covers structured metadata, serialized JSON, nested values, exception tracebacks, authorization headers, and URLs with sensitive query parameters. The OpenAI Responses provider also stops printing credential-bearing MCP server URLs to standard output and logs only server names at debug level.

> [!WARNING]
>
> If an MCP server URL from an older `@composio/openai` release was captured in application or infrastructure logs, treat that URL as exposed and regenerate the endpoint.

Credit to independent security researcher Syed Anas Mohiuddin for reporting the legacy CLI credential-file permission issue.

### File transfers have bounded sizes and consistent errors

Automatic S3 downloads in both SDKs now stop at a fixed 100 MiB limit, including responses that omit or misreport `Content-Length`.

Python removes partial files when a download fails and maps transport or filesystem failures to `ErrorDownloadingFile`. TypeScript maps connection and streamed-body failures from `RemoteFile` to `RemoteFileDownloadError`, closes unused response bodies, and applies the same 100 MiB bound to `buffer()`, `blob()`, `text()`, and `save()`.

CLI URL uploads now use the SDK's SSRF protections for both the source URL and the API-provided upload destination. Redirects are checked again, Node.js and Bun connect to the validated address, and internal destinations are rejected before file bytes are sent.

### Referenced tool schemas retain their types

The Claude Agent SDK, Google, LangChain, LlamaIndex, OpenAI Agents, and Vercel providers now resolve internal `$ref` and `$defs` references before translating a tool's input schema. Properties reachable only through a reference previously became untyped values or dangling references in the provider-facing schema.

For example, a tool schema can define an object once and reuse it:

```json theme={null}
{
  "$defs": {
    "Recipient": {
      "type": "object",
      "properties": {
        "email": { "type": "string" }
      },
      "required": ["email"]
    }
  },
  "type": "object",
  "properties": {
    "recipient": { "$ref": "#/$defs/Recipient" }
  }
}
```

Provider adapters now preserve the `recipient.email` string constraint instead of reducing `recipient` to an untyped value. The OpenAI Agents strict structured-output path is unchanged because OpenAI handles `$defs` and `$ref` natively, including recursive references.

When a `$ref` has no matching entry in `$defs`, provider translation now falls back to a permissive object schema instead of throwing an error.

> [!NOTE]
>
> This changes the provider-facing JSON Schema for tools that use `$ref`. Snapshot tests on translated tool definitions may need updates. Runtime calls that do not inspect or snapshot those schemas do not need migration work.

### Schema conversion matches JSON Schema dialects more closely

Python schema conversion and `@composio/json-schema-to-zod` now preserve Draft 7 acceptance across primitive, composed, referenced, conditional, and typeless schemas. Converted validators no longer accept booleans as integers, and they correctly handle tuple schemas with `additionalItems`, object and scalar `allOf` rules, internal `$ref` values, conditional branches, and constraints without an explicit `type`.

`@composio/json-schema-to-effect-schema` now enforces the OpenAPI 3.0 and Draft 4 boolean forms of `exclusiveMinimum` and `exclusiveMaximum`, so an exclusive bound no longer accepts the boundary value.

Credit to [simpleqt](https://github.com/simpleqt) for originally surfacing the schema conversion cases.

### Custom tool slugs are qualified by toolkit

Python and TypeScript sessions now distinguish custom tools by toolkit and original slug. Two custom toolkits can both define a child such as `GREP`, `SEARCH`, or `VERSION` without one handler replacing or hiding the other.

Toolkit-qualified final slugs such as `LOCAL_ALPHA_GREP` and `LOCAL_BETA_GREP` route to the matching handler. A bare `GREP` alias remains available when it identifies exactly one local tool. When it is ambiguous, the SDK raises an error that lists the final slugs you can use instead of choosing a handler silently.

### CLI and SDK reliability fixes

* CLI spinners stay on one terminal row when a message is wider than the terminal, so `composio upgrade` no longer prints hundreds of progress lines in a narrow pane.
* TypeScript trigger subscriptions now apply the requested `authConfigId` filter before invoking callbacks.
* Python uploads `.jpg` files with the standard `image/jpeg` content type while continuing to accept `image/jpg` from external responses.

### Backward compatibility

This release does not remove or rename public APIs. Provider packages receive minor version bumps because referenced schemas now retain their real shape, which can change schema snapshots. Corrected JSON Schema conversion may also change whether previously misclassified inputs pass generated validators. Ambiguous bare custom-tool slugs now fail with the qualified alternatives rather than routing unpredictably.

**Aug 28, 2026**

Scoped project API keys now separate session management from session tool execution.

## Granular session permissions for scoped API keys

Scoped project API keys now give you separate controls for session management and session-based execution.

### What's new

* **Session management** controls creating, viewing, configuring, and deleting sessions.
* **Session tool execution** covers search, tool execution, proxy execution, and session-linked MCP access.

**Aug 27, 2026**

Python SDK 0.21.0 and TypeScript SDK 0.18.0 preserve optional parameters in strict tool schemas, reject unsafe file transfers, and improve provider reliability.

## Python SDK 0.21.0 and TypeScript SDK 0.18.0 harden strict tool schemas and file transfers

Python SDK `composio` `0.21.0` and TypeScript SDK `@composio/core` `0.18.0` make strict-mode tool schemas compatible with nested and optional parameters, harden automatic file transfers, and improve reliability across providers and runtimes.

### SDK versions

| SDK | Version |
| - | - |
| Python `composio` | `0.21.0` |
| TypeScript `@composio/core` | `0.18.0` |
| TypeScript `@composio/slim` | `0.18.0` |
| TypeScript `@composio/openai` | `0.12.1` |
| TypeScript `@composio/openai-agents` | `0.10.2` |
| TypeScript `@composio/mastra` | `0.10.4` |
| TypeScript `@composio/vercel` | `0.11.2` |

### Strict tool schemas keep optional parameters

OpenAI-compatible strict mode now normalizes schemas recursively across nested objects, unions, array items, and local references. Every object declares all properties as required and rejects undeclared properties, while fields that were optional accept `null`. Before tool execution, the SDK removes a `null` argument when the tool's original schema does not accept it.

Schemas that strict mode cannot represent, such as arbitrary-key objects, unsupported intersections, tuple-style arrays, or unresolved references, now fall back to non-strict mode with a warning that names the tool and incompatible path. This avoids silently narrowing the tool's accepted input.

TypeScript users can apply the same behavior directly with the new `toStrictJsonSchema()` and `omitNullToolArguments()` exports. `OpenAIAgentsProvider({ strict: true })` now honors the option, and Mastra and Vercel use the same normalization rules.

Python's `OpenAIResponsesProvider` now accepts `strict=True`, emits `strict: true` on compatible tools, and follows the same recursive schema rules. Existing provider construction remains unchanged unless strict mode is enabled.

### Safer file uploads and downloads

* Automatic uploads reject sensitive paths even when a symlink hides the sensitive directory or filename.
* Empty-string file arguments are omitted instead of being sent to the API or treated as upload candidates.
* Nullable and nested file arguments retain their original structure during Python request preparation.
* TypeScript URL fetching now connects to the exact IP address that passed SSRF validation, closing a DNS-rebinding window while preserving the original hostname for HTTP and TLS verification. Redirect destinations are validated and pinned independently.

### Runtime and reliability updates

* Published TypeScript packages now require Node.js 22.22.3 or newer. Package managers report unsupported runtimes during installation instead of allowing later ESM loading failures.
* Best-effort TypeScript telemetry requests now time out, so an unreachable telemetry endpoint cannot keep an SDK call pending indefinitely.
* TypeScript error subclasses now report their own names for accurate telemetry grouping.
* Python preserves explicit empty tool schemas and isolates provider dependency conflicts more reliably.

### Backward compatibility

Strict mode remains opt-in. Python users who do not pass `strict=True` keep the existing provider behavior. TypeScript users on Node.js versions older than 22.22.3 must upgrade Node.js before installing this release.

**Aug 19, 2026**

Python SDK 0.20.0 and TypeScript SDK 0.17.0 let OpenAI and Anthropic provider helpers execute through a Tool Router session, validate API-response URLs before fetching them, and fix a Python import-time crash on read-only filesystems.

## Python SDK 0.20.0 and TypeScript SDK 0.17.0 route provider tool calls through sessions

Python SDK `composio` `0.20.0` and TypeScript SDK `@composio/core` `0.17.0` let the OpenAI and Anthropic provider tool-call helpers execute through a supplied Tool Router session, close an SSRF gap around API-response URLs, and fix several Python file-handling issues.

### SDK versions

| SDK | Version |
| - | - |
| Python `composio` | `0.20.0` |
| TypeScript `@composio/core` | `0.17.0` |
| TypeScript `@composio/slim` | `0.17.0` |
| TypeScript `@composio/anthropic` | `0.11.0` |
| TypeScript `@composio/openai` | `0.12.0` |

### Session-aware provider tool-call helpers

> [!WARNING]
>
> **Type-level breaking change**
>
> `handleToolCalls`/`executeToolCall` (TypeScript) and `handle_tool_calls`/`execute_tool_call` (Python) now accept an explicit execution target — a user ID or a Tool Router session. Custom provider subclasses that override these methods may need updates to match the new signatures. Existing user-ID calls are unchanged and keep using direct execution.

Previously, calling these helpers with tools obtained from `session.tools()` still executed through the globally injected direct `Tools.execute` function, discarding the Tool Router session context. Session meta-tools such as `COMPOSIO_SEARCH_TOOLS` failed as a result. Calling `session.execute()` directly preserved the session but skipped provider-specific behavior, such as Anthropic's input normalization and schema-alias restoration.

The helpers now route normalized provider arguments through the supplied session when one is given, while keeping provider-specific normalization intact. Anthropic helper failures now preserve their error text in `{ error }` results without changing successful payloads.

### API-response URL validation

Both SDKs already validated user-supplied URLs against SSRF before fetching them. That guard did not cover URLs that arrive inside an API response. It now does, across every response-driven fetch: tool-execution downloads, S3 presigned uploads, Tool Router session file downloads and uploads, and `RemoteFile.buffer()`/`blob()`/`text()`/`save()`. Redirect hops are re-validated on each hop, so a validated URL cannot redirect into private address space. Edge runtimes that cannot resolve DNS to check keep their current behavior for session file transfers, since a Worker's `fetch` does not originate inside the caller's network.

### Python file handling fixes

* Importing `composio` no longer creates the local cache directory or fails on a read-only filesystem. Directory creation is deferred to the first actual file download, so environments like AWS Lambda, distroless containers, and read-only Kubernetes root filesystems can import the SDK without ever touching disk. `COMPOSIO_CACHE_DIR` is also now honored correctly when it is set, instead of eagerly resolving the home directory first.
* File uploads to S3 presigned URLs now send the `Content-Type` the presign request was signed with on every upload path, and a rejected upload raises with its HTTP status instead of a path-only error. A malformed or negative `Content-Length` on a fetched URL now degrades to an unknown size instead of raising.
* Filesystem path construction for API-provided slugs and filenames is now centralized and rejects traversal, Windows-invalid names, invalid Unicode, and overlong encoded filenames before creating directories or writing files.

### Dependency updates

Runtime dependencies across the TypeScript SDK packages and the Python core and provider packages have been refreshed.

### Backward compatibility

Existing user-ID based provider helper calls are unchanged. Custom provider subclasses overriding the tool-call helpers should review the updated signatures.

**Aug 7, 2026**

Python SDK 0.18.2 and TypeScript SDK 0.15.0 redact secrets inside JSON telemetry payloads, replace the loose JSON Schema property type with a recursive one, and add OpenAI v6 and v7 support.

## Python SDK 0.18.2 and TypeScript SDK 0.15.0 tighten JSON Schema types and secret redaction

Python SDK `composio` `0.18.2` and TypeScript SDK `@composio/core` `0.15.0` redact secrets that appear inside JSON payloads in telemetry, give `JSONSchemaProperty` a precise recursive type, and harden several request and upload paths. `@composio/openai` `0.11.0` adds support for OpenAI v6 and v7.

### SDK versions

| SDK | Version |
| - | - |
| Python `composio` | `0.18.2` |
| TypeScript `@composio/core` | `0.15.0` |
| TypeScript `@composio/slim` | `0.15.0` |
| TypeScript `@composio/openai` | `0.11.0` |
| TypeScript `@composio/experimental` | `0.2.2` |
| TypeScript `@composio/json-schema-to-zod` | `0.2.2` |

### Secret redaction in telemetry

Telemetry error text is redacted before it leaves the process, but the key/value rule required the separator to follow the key name directly. In JSON — and in a Python `dict` repr — the key's own closing quote sits between the name and the colon, so a serialized body such as `{"api_key": "sk-live-..."}` never matched and the value was sent verbatim. That is the shape error messages usually carry: an API error envelope, or a rejected request body echoed back.

Both SDKs now redact these values.

**Before:**

```text theme={null}
Request failed: {"api_key": "sk-live-abc123", "user_id": "u_42"}
```

**After:**

```text theme={null}
Request failed: {"api_key": "[REDACTED]", "user_id": "u_42"}
```

### Typed JSON Schema properties

> [!WARNING]
>
> **Type-level breaking change**
>
> `JSONSchemaProperty` — re-exported from `@composio/core` and reachable through `Tool.input_parameters` and `Tool.output_parameters` — is now a concrete recursive interface instead of effectively `any`. Runtime behavior is unchanged, but code that indexed into it without narrowing may see new type errors: `properties` entries are now possibly `undefined`, and `default` and `enum` values are `unknown`.

**Before:**

```typescript theme={null}
const type = tool.input_parameters.properties.query.type;
const fallback: string = tool.input_parameters.properties.query.default;
```

**After:**

```typescript theme={null}
const type = tool.input_parameters.properties?.query?.type;
const rawDefault = tool.input_parameters.properties?.query?.default;
const fallback = typeof rawDefault === 'string' ? rawDefault : undefined;
```

`@composio/json-schema-to-zod` now also models the parser-supported `min`, `max`, and `example` JSON Schema extensions in its exported recursive schema type.

### What's new

* `@composio/openai` supports OpenAI versions 6 and 7. The OpenAI runtime dependency in `@composio/core` and `@composio/slim` has been refreshed to version 7.

### Improvements

* The background npm version check is now bounded by an abort timeout, so a registry outage cannot leave the request pending indefinitely.
* Sensitive upload path segments are matched using the target filesystem's actual case sensitivity, so case-insensitive mounts cannot bypass the denylist and distinct paths on case-sensitive mounts are not over-blocked.
* Unread response bodies are released on the paths the SDK knowingly abandons: every intermediate redirect body in `ssrfSafeFetch`, and the response body before throwing on a failed URL upload.

### Dependency updates

Runtime dependencies across the TypeScript SDK packages and the Python core and provider packages have been refreshed.

### Backward compatibility

Runtime behavior is unchanged in both SDKs. The only upgrade impact is at the TypeScript type level, for consumers that read `JSONSchemaProperty` fields without narrowing.

**Aug 6, 2026**

Tool arguments declared as bare objects are no longer rejected or silently emptied, and Python now enforces the same unknown-key rules as TypeScript

## Free-Form Object Arguments Are Preserved Across SDKs

### SDK Versions

| SDK | Version |
| - | - |
| Python `composio` | `0.19.0` |
| TypeScript `@composio/core` | `0.16.0` |
| TypeScript `@composio/slim` | `0.16.0` |
| TypeScript `@composio/json-schema-to-zod` | `0.3.0` |
| TypeScript `@composio/claude-agent-sdk` | `0.11.0` |
| TypeScript `@composio/google` | `0.10.2` |

***

A tool argument declared as a bare `{"type": "object"}` — with no `properties` of its own — was rejected or silently emptied at every schema conversion boundary. This affects any tool that takes a free-form payload, such as `dataset_query` on `METABASE_POST_API_CARD`.

### What Changed

An object schema that names no properties is now treated as open, unless it sets `additionalProperties: false`: arbitrary content is accepted and preserved, at the root, nested inside another object, and inside array items.

#### Google Gemini schema compatibility

`@composio/google` now adds `type: "object"` to schema nodes that declare `properties` without a type before emitting Google GenAI function declarations. The normalization follows only schema-bearing keywords, so property maps — including a field literally named `properties` — and instance values under `const`, `default`, `enum`, and `examples` remain unchanged. This provider release requires `@composio/core >=0.16.0 <1.0.0`.

**Before:**

```python theme={null}
# tool comes from Composio(provider=LangchainProvider()).tools.get(...)
# dataset_query is declared as {"type": "object"} with no properties
tool.run({"dataset_query": {"database": 1, "query": {"source-table": 2}}})
# The argument was accepted, then arrived at execution as an empty object
```

**After:**

```python theme={null}
tool.run({"dataset_query": {"database": 1, "query": {"source-table": 2}}})
# The full payload reaches execution intact
```

In TypeScript the same schema was rejected outright rather than emptied, both in the Zod converter and in CLI tool-input validation:

```text theme={null}
<root>: Unknown key "database". Allowed top-level keys: dataset_query
```

Those inputs are now accepted.

The CLI-side fix ships with the CLI binary rather than the npm packages above. Upgrade it with `composio upgrade`.

#### Dynamic keys apply only where they should

Where a schema declares `patternProperties` or a schema-valued `additionalProperties`, each key is now validated against exactly the schemas that claim it. In TypeScript a key could previously pass by satisfying an unrelated pattern instead of its own. In Python neither keyword was read at all, so dynamic keys were never validated.

* Every matching `patternProperties` entry validates its key.
* `additionalProperties` applies only to keys that no declared property and no pattern matches.
* A key declared in `properties` is still checked against every pattern it matches.

Root-level `patternProperties` and boolean- or schema-valued `additionalProperties` also survive tool schema parsing; they were previously dropped before any converter could see them.

> [!WARNING]
>
> **Behavior change**
>
> Because the Python converter read neither keyword, an object that declared no properties became an empty Pydantic model: every dynamic key was dropped and the call ran without it. Those keys are now validated — at the root, nested under a declared property, and inside array items — and preserved when they pass.

**Before:**

```python theme={null}
# `metadata` is {"type": "object"} with "patternProperties": {"^count_": {"type": "integer"}}
wrapped.run({"metadata": {"count_a": "not-an-integer"}})
# The tool executed with {"metadata": {}} - every dynamic key was dropped in silence
```

**After:**

```python theme={null}
wrapped.run({"metadata": {"count_a": "not-an-integer"}})
# Raises ValidationError before execution

wrapped.run({"metadata": {"count_a": 3}})
# The tool executes with {"metadata": {"count_a": 3}} intact
```

In Python, an invalid `patternProperties` or schema-valued `additionalProperties` schema now raises while the tool is wrapped instead of being ignored. This includes an external, anchored, or unresolvable `$ref`, a `patternProperties` key that is not a valid regular expression, or a dynamic-key subschema that is not valid Draft 7. A `$ref` in these schemas must be a local JSON Pointer such as `#/properties/foo`. The rule is transitive: a local pointer whose target carries a non-local reference raises too. A `$ref`-shaped value under `const`, `default`, `enum`, or `examples` is instance data rather than a reference, and is left alone.

The CLI's validator fails early on the two of those it can detect: a `patternProperties` key that is not a valid regular expression, and a reference inside a dynamic-key subschema that does not resolve, following local pointers transitively. Both are now reported as a schema compile failure naming the cached schema path, rather than as an input error blaming the arguments. A reference outside a dynamic-key subschema is still left to the validator, so a tool whose unused branch carries a dangling reference keeps working.

### Behavior Change for Python Agentic Providers

> [!WARNING]
>
> **Behavior change**
>
> In the Python SDK, an object schema that **does** name properties and omits `additionalProperties` now rejects unknown keys instead of silently dropping them.
>
> This affects the providers that build a Pydantic `args_schema` from a tool schema: `composio_langchain`, `composio_langgraph`, and `composio_crewai`. If a model emits an argument the tool does not declare, the call now raises a `ValidationError` instead of executing with that argument removed.

**Before:**

```python theme={null}
# Tool declares only `name`. The model also emits `typo`.
wrapped.run({"name": "a", "typo": 1})
# The tool executed with {"name": "a"} - the extra argument was dropped in silence
```

**After:**

```python theme={null}
wrapped.run({"name": "a", "typo": 1})
# Raises ValidationError before execution, so the agent can correct and retry
```

This brings Python in line with the TypeScript SDK, where the Zod converter has always rejected unknown keys for schemas that name properties. Strictness applies only when `additionalProperties` is omitted; `additionalProperties: true` and schema-valued forms behave as declared.

#### Provider argument presence is preserved

CrewAI, LangChain, and LangGraph now keep the difference between an omitted optional field and a field explicitly set to `None`. JSON Schema defaults are included, while optional fields with no default stay absent. The same rules apply inside nested objects, arrays, maps, combiners, and dynamic-key values.

```python theme={null}
# The schema requires `query`, allows a nullable `note`, and defaults `page` to 5.
wrapped.run({"query": "agents", "note": None})
# The tool receives {"query": "agents", "note": None, "page": 5}.
```

If you omit `note`, the tool does not receive it. Before this release, provider serialization could add an omitted nullable field as `None`, or drop an explicit `None`, a declared default, or a dynamic extra.

#### Not affected

* **`composio_openai`, `composio_anthropic`, and the other non-agentic providers.** These hand the raw JSON schema to the model API and pass the returned arguments straight through, so they never build a Pydantic model from a tool schema.
* **`composio_gemini`.** Gemini builds a typed signature through `json_schema_to_pydantic_type`, so free-form object arguments now use `Dict[str, Any]` instead of an empty model. It does not use `json_schema_to_model`, so the unknown-key rejection above does not apply.
* **Provider APIs and invocation signatures.** You wrap and call tools the same way. The change is limited to validated arguments passed to the tool.

### Behavior Change for the Claude Agent SDK Provider

> [!WARNING]
>
> **Behavior change**
>
> `@composio/claude-agent-sdk` now registers each tool with its complete object schema rather than a raw property shape.
>
> A raw shape carries only the per-property map, so root-level `additionalProperties` and `patternProperties` were dropped before the Claude Agent SDK ever saw them. An unknown key was stripped from the arguments and the tool executed anyway. It is now rejected before the tool runs, and the caller receives an error result instead, matching every other TypeScript provider.

This is also what makes free-form object arguments reach execution intact through this provider: the content of a bare `{"type": "object"}` argument survives registration instead of being discarded with the rest of the root constraints.

#### Not affected

* **`@composio/vercel`, `@composio/langchain`, and `@composio/llamaindex`.** These already registered complete schemas, so they picked the fix up with no change.

### Backward Compatibility

Accepting and preserving free-form object content is backward compatible: payloads that previously failed now succeed, and payloads that previously arrived empty now arrive complete.

The two unknown-key rejections described above (Python agentic providers and the Claude Agent SDK provider) are two of the three behavior changes at call time. The third is [Python dynamic-key validation](#dynamic-keys-apply-only-where-they-should): a key that used to be dropped in silence now raises a `ValidationError` when it does not match the `patternProperties` or `additionalProperties` schema that claims it.

`additionalProperties: true` still opts an object out of unknown-key rejection. Declaring no properties does too, unless the object sets `additionalProperties: false` — an explicit `false` closes it, and Python now raises on the unknown keys it used to drop there, the same drop-to-raise transition as the first change. Neither opt-out covers the third change: if the object carries `patternProperties` or a schema-valued `additionalProperties`, its keys are validated against those schemas. An open object with no dynamic-key constraints is unaffected by it.

The remaining changes are about the schema itself rather than the arguments checked against it: an invalid dynamic-key schema now fails instead of being ignored. Only tools whose `patternProperties` or schema-valued `additionalProperties` carry such a defect are affected, and the two SDKs get there differently.

In Python it is a raise while the tool is wrapped, covering an invalid reference, regular expression, or Draft 7 subschema. Neither keyword was read before, so the defect never surfaced at all and every dynamic key was dropped. A tool carrying one now fails when it is wrapped, for every caller, rather than on a particular payload.

In the CLI it is a schema compile failure, covering an invalid `patternProperties` regular expression or an unresolvable reference inside a dynamic-key subschema. There the defect did surface, but only when validation descended into that part of the schema, and it was reported as though the arguments were at fault. A payload that stayed out of the affected branch validated against a schema that could not fully check it, and is now rejected.

**Aug 5, 2026**

curl | sh now infers your login shell and writes a managed PATH block, with COMPOSIO\_INSTALL\_SHELL=none as the install-only opt-out.

## The CLI installer configures your shell by default

The Composio CLI installer now puts `composio` on `PATH` for future terminals automatically. This replaces the install-only default announced in [Install the Composio CLI with a POSIX shell](https://composio-preview.mintlify.site/docs/changelog/2026/07/31).

> [!WARNING]
>
> **Behavior change: `curl | sh` now edits shell startup files by default**
>
> The previous installer copied files into place and left `PATH` alone. It now infers your login shell from `$SHELL` and writes a managed `PATH` block to that shell's startup files, so new terminals find `composio` without manual setup:
>
> * zsh: `~/.zshrc`
> * bash: `~/.bashrc` and your login file — `~/.bash_profile`, or `~/.bash_login` when that is the only login file present
> * fish: `~/.config/fish/config.fish`
>
> On bash systems with no login file at all, the installer **creates `~/.bash_profile`**. When `~/.profile` exists, the new file is seeded to keep sourcing it, so your existing login settings still load.
>
> To keep the previous install-only behavior, opt out with `COMPOSIO_INSTALL_SHELL=none`:
>
> ```sh theme={null}
> curl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_SHELL=none sh
> ```

### What's new

* The default flow infers your shell from `$SHELL` and configures `PATH` for future terminals. Set `COMPOSIO_INSTALL_SHELL=none` for an install-only run in CI, Docker images, or when a dotfile manager owns your startup files.
* `COMPOSIO_INSTALL_SHELL=zsh|bash|fish` still forces a specific shell, for example `curl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_SHELL=zsh sh`.
* If your `$SHELL` is not zsh, bash, or fish, the installer degrades to an install-only run and prints the command to configure `PATH` yourself.
* Agent plugin installation and login remain opt-in.
* Re-running the installer reconciles the managed block instead of appending a second one, so repeated installs leave exactly one block per startup file.

### Download verification

* Every download uses HTTPS — plain HTTP is accepted only for loopback addresses or a host you explicitly allow with `COMPOSIO_INSTALL_ALLOW_HTTP_HOST` — and redirects can only ever lead to HTTPS URLs.
* Official releases — the default `github.com/ComposioHQ/composio` source — must now pass checksum verification: a missing `checksums.txt`, a manifest with no entry for your platform's archive, a malformed entry, or a checksum mismatch aborts the install. Previously a missing manifest warned and continued.
* On systems with no SHA-256 utility (`sha256sum` or `shasum`), rare outside minimal containers, the installer warns that checksum verification was skipped and continues.
* Overridden sources (`COMPOSIO_GITHUB_URL`, `COMPOSIO_GITHUB_OWNER`, `COMPOSIO_GITHUB_REPO`, or a custom API base) stay lenient: a missing manifest or entry warns and continues, and only a checksum mismatch or malformed entry aborts.

**Jul 31, 2026**

The CLI installer now runs on POSIX sh, keeps the release bundle separate from the entry point, and makes shell configuration opt-in.

## Install the Composio CLI with a POSIX shell

The Composio CLI installer now separates the release bundle from the command you run, works with POSIX `sh`, and leaves shell configuration opt-in.

### What's new

* `curl -fsSL https://composio.dev/install | sh` installs the verified release bundle in `~/.composio` and creates `~/.local/bin/composio`.
* The default flow does not edit shell files, install agent plugins, or log you in.
* `COMPOSIO_INSTALL_SHELL=zsh|bash|fish` configures the requested shell explicitly, for example `curl -fsSL https://composio.dev/install | COMPOSIO_INSTALL_SHELL=zsh sh`.
* `COMPOSIO_INSTALL_VERSION`, `COMPOSIO_BIN_DIR`, `COMPOSIO_QUIET`, and `COMPOSIO_DEBUG` give you control over version, layout, and output.
* Existing `COMPOSIO_INSTALL_DIR` configurations keep their bundle-directory meaning.

The opt-in default described here was later replaced: see [the installer now configures your shell by default](https://composio-preview.mintlify.site/docs/changelog/2026/08/05).

**Jul 30, 2026**

Opt-in, per-project callback identity verification: confirm the returning user before an OAuth connection activates. Python SDK 0.18.1 and TypeScript SDK 0.14.1 strengthen URL uploads, improve trigger subscription reliability, and fix schema and MIME type handling.

## Callback identity verification for OAuth connections

You can now add an identity check to your OAuth connections. Set a verifier URL on your project, and Composio hands each OAuth return to your server, activating the connection only after your server confirms the signed-in user is the one it was created for.

It is opt-in per project and, once set, covers every OAuth connection in the project. Because it confirms the returning user, it holds however the user comes back from the provider. Turn it on in Settings → General.

[Learn more](https://composio-preview.mintlify.site/reference/api-reference/connected-accounts#callback-identity-verification)

## Python SDK 0.18.1 and TypeScript SDK 0.14.1 harden uploads and event handling

Python SDK `composio` `0.18.1` and TypeScript SDK `@composio/core` `0.14.1` strengthen URL upload validation and address reliability issues in file handling, trigger subscriptions, and schema conversion.

### SDK versions

| SDK | Version |
| - | - |
| Python `composio` | `0.18.1` |
| TypeScript `@composio/core` | `0.14.1` |
| TypeScript `@composio/slim` | `0.14.1` |
| TypeScript `@composio/experimental` | `0.2.1` |
| TypeScript `@composio/mastra` | `0.10.3` |

### URL upload security

* Python URL uploads now validate the canonical URL that Requests will connect to. Backslash parser differentials, malformed ports, and destinations that resolve to non-public addresses are rejected before a connection is made.
* TypeScript Tool Router session URL uploads now use the SDK's SSRF-safe fetch path, revalidate every redirect target, and stream responses with a 100 MiB limit. Edge runtimes that cannot validate DNS fail closed for URL inputs.
* TypeScript path handling on Cloudflare Workers and other edge runtimes now avoids backtracking regular expressions that could hang on long runs of slash characters.

### Python reliability and correctness

* Calling `TriggerSubscription.stop()` from a trigger callback no longer deadlocks. Timed-out subscription attempts also disconnect their websocket instead of leaving a reconnecting background thread behind.
* Malformed chunked trigger frames are contained at the callback boundary, so one bad frame no longer tears down an otherwise healthy subscription.
* File extensions are matched case-insensitively when inferring MIME types, so names such as `photo.PNG` and `scan.PDF` receive the correct content type.
* JSON Schema `allOf` combinations containing an impossible schema remain rejecting through nested objects, arrays, and local definitions instead of being widened to an accepting type.

### Dependency updates

Runtime dependencies across the TypeScript SDK packages and Python core and provider packages have been refreshed.

**Jul 16, 2026**

Python SDK 0.18.0 blocks unsafe URL file inputs, redacts secrets from telemetry, aligns trigger connection resolution, and improves provider schema compatibility.

## Python SDK 0.18.0 hardens file uploads and provider schemas

Python SDK `composio` `0.18.0` closes URL-upload and telemetry exposure paths, aligns trigger creation with the current backend contract, and improves provider compatibility with modern tool schemas. All Python provider packages are also aligned at `0.18.0`.

### SDK versions

| SDK | Version |
| - | - |
| Python `composio` | `0.18.0` |

### File and telemetry security

* `FileUploadable.from_url()` and Tool Router session-file imports now accept only HTTP(S) hosts whose resolved addresses are public. Redirects are rejected, and blocked inputs raise `BlockedInternalUrlError`.
* Error telemetry now applies best-effort redaction to error messages and stack traces before transport, covering URL queries, bearer and basic credentials, and recognized secret-like key-value pairs.

### Trigger creation

`triggers.create()` now sends `user_id` to the backend rather than listing connected accounts in the SDK. When no `connected_account_id` is supplied, the backend selects the most recently created active connection for the user and toolkit. Self-hosted deployments need the backend version that supports this resolution.

Invalid trigger slugs now raise `TriggerTypeNotFound`. Omitting both `user_id` and `connected_account_id`, or passing blank values for both, raises `InvalidParams`. When the supplied user has no matching active connection, the backend upsert error now surfaces instead of the SDK raising `NoItemsFound` locally.

### Provider and schema compatibility

* OpenAI provider tool-call handling now executes every call from the first assistant choice, including multiple calls returned in one response.
* Tool signature generation accepts list-valued JSON Schema types, unbounded `anyOf` and `oneOf` options, and title-less top-level schemas.
* LangChain, LangGraph, and AutoGen provider signatures now honor the configured `skip_default` value.
* The OpenAI Agents provider preserves valid array-item schemas instead of coercing type-less items to strings.
* Toolkit version pins are case-insensitive in both environment variables and user-provided mappings.

### AutoGen dependency

> [!WARNING]
>
> **Compatibility change**
>
> `composio-autogen` now depends on `ag2` instead of the abandoned `pyautogen` package. Update dependency constraints or lockfiles that explicitly require `pyautogen` before upgrading.

**Jul 15, 2026**

TypeScript SDK 0.14.0 blocks unsafe URL uploads, redacts secrets from telemetry, and makes tool execution more reliable.

## TypeScript SDK 0.14.0 hardens file uploads and tool execution

TypeScript SDK `@composio/core` `0.14.0` closes file-upload and telemetry exposure paths, prevents duplicate tool side effects after retries, and aligns trigger creation with backend connection resolution.

### SDK versions

| SDK | Version |
| - | - |
| TypeScript `@composio/core` | `0.14.0` |

### File and telemetry security

* URL file uploads and automatic uploads during tool execution reject private, loopback, link-local, carrier-grade NAT, and reserved addresses. Redirects are checked at every hop, and blocked requests raise `ComposioBlockedInternalUrlError`.
* Error telemetry redacts URL query strings, authorization credentials, and secret-like key-value pairs before transport.
* The package root exports `assertSafeFileUploadPath`, `isBlockedSensitiveFileUploadPath`, and `BUILTIN_FILE_UPLOAD_PATH_DENY_SEGMENTS` so downstream packages can apply the same sensitive-file denylist.

### Tool execution reliability

* `tools.execute()` and `tools.proxyExecute()` no longer retry non-idempotent writes, preventing a timeout from repeating side effects such as sending the same email twice.
* `OpenAIProvider.handleToolCalls()` executes every tool call from the first assistant choice and returns one result for each `tool_call_id` in deterministic order.
* Provider tool schemas normalize duplicate JSON Schema `required` entries before they are emitted.

### Trigger and toolkit behavior

`triggers.create()` now sends `user_id` directly to the backend when `connectedAccountId` is omitted. This removes the extra connected-account lookup and lets the backend select the first active connection for the user and toolkit.

> [!WARNING]
>
> **Behavior change**
>
> A missing or invalid connection now surfaces the backend upsert error instead of `ComposioConnectedAccountNotFoundError`. Self-hosted deployments need a backend version that resolves trigger connections from `user_id`.

Toolkit version pins are also case-insensitive in configuration objects and environment variables, so casing differences no longer fall back silently to `latest`.

**Jun 28, 2026**

Python SDK 0.17.1 adds Tool Router session deletion through the sessions API and a session instance method.

## Python SDK 0.17.1 adds session deletion

Python SDK `composio` `0.17.1` adds deletion to the Tool Router session lifecycle. This matches the TypeScript SDK surface released in `@composio/core` `0.13.1`.

### SDK versions

| SDK | Version |
| - | - |
| Python `composio` | `0.17.1` |

Delete a session from the client or from the session itself:

```python theme={null}
composio.sessions.delete(session_id)

session.delete()
```

**Jun 27, 2026**

Python SDK 0.17.0 adds the sessions API, opt-in MCP, webhook helpers, shared-connection ACL updates, and sandbox configuration.

## Python SDK 0.17.0 makes sessions first-class

Python SDK `composio` `0.17.0` moves Tool Router onto a sessions-first API. It also adds webhook helpers and makes the current shared-connection ACL API easier to discover.

### SDK versions

| SDK | Version |
| - | - |
| Python `composio` | `0.17.0` |

### Sessions and MCP

`composio.sessions.create(...)` is now the canonical sessions entry point. `composio.create(...)` and `composio.use(...)` remain supported shortcuts, while `composio.tool_router` is deprecated as an alias for the same object.

Sessions return native tools by default. Set `mcp=True` when a typed MCP session is required. The runtime object is unchanged, but the explicit option makes the MCP dependency visible in application code.

### New APIs and behavior

* `triggers.parse()` parses an incoming webhook request and can verify its signature. Passing an empty `verify_secret` now raises instead of silently skipping verification.
* `triggers.set_webhook_subscription()` creates or updates the project webhook subscription.
* `connected_accounts.update_acl()` is the primary shared-connection ACL patch helper. `experimental.update_acl()` remains as a deprecated alias.
* Prefer `sandbox` for session code-execution configuration. `workbench` remains an accepted alias.

**Jun 26, 2026**

TypeScript SDK 0.13.0 makes sessions first-class and MCP opt-in. Version 0.13.1 adds session deletion.

## TypeScript SDK 0.13.0 adds sessions and 0.13.1 adds deletion

TypeScript SDK `@composio/core` `0.13.0` makes the sessions API the primary way to work with Tool Router. Version `0.13.1` completes the lifecycle with session deletion.

### SDK versions

| SDK | Version |
| - | - |
| TypeScript `@composio/core` | `0.13.0` |
| TypeScript `@composio/core` | `0.13.1` |

### Sessions are first-class

Use `composio.sessions.create()` as the canonical entry point. `composio.create()` remains an alias. The shared-connection ACL helper also graduates to `connectedAccounts.updateAcl()`, while `experimental.updateAcl()` remains as a compatibility alias.

MCP is now opt-in at the type level. Sessions return native tools by default. Create a session with `{ mcp: true }` before reading `session.mcp` in TypeScript.

```typescript theme={null}
import { Composio } from '@composio/core';

const composio = new Composio({ apiKey: 'your-api-key' });
const session = await composio.sessions.create('user_123', { mcp: true });

const mcp = session.mcp;
```

### Other session and trigger updates

* Session responses expose the resolved workbench configuration. Prefer `sandbox` for code-execution configuration; `workbench` remains an accepted alias.
* `triggers.parse()` parses incoming webhook requests and can verify their signatures.
* `triggers.setWebhookSubscription()` creates or updates a project webhook subscription.
* `composio.sessions.delete(sessionId)` and `session.delete()` remove a Tool Router session in `0.13.1`.

**Jun 25, 2026**

TypeScript SDK 0.12.0 adds request cancellation and becomes ESM-only. Python SDK 0.16.0 fixes file transfer, retries, schema handling, and provider aliases.

## TypeScript SDK 0.12.0 and Python SDK 0.16.0

This release improves failure handling on both SDKs. TypeScript callers can cancel a request rather than waiting for a slow network operation. Python fixes file handling, request timeouts, retry safety, and schema compatibility that could otherwise produce incorrect tool calls.

### SDK versions

| SDK | Version |
| - | - |
| TypeScript `@composio/core` | `0.12.0` |
| Python `composio` | `0.16.0` |

### TypeScript: request cancellation and ESM-only packages

Public TypeScript SDK methods accept a trailing `{ signal?: AbortSignal }` request-options argument. Caller-initiated aborts are normalized to `ComposioRequestCancelledError`, including custom tools that cooperatively use `SessionContext.signal`.

> [!WARNING]
>
> **Breaking change**
>
> The TypeScript SDK packages are ESM-only in `0.12.0`. Use Node.js `22.22.3` or newer and ESM imports. The SDK no longer ships `.cjs` artifacts or its prior CommonJS compatibility layer.

**Before:**

```javascript theme={null}
const { Composio } = require('@composio/core');
```

**After:**

```javascript theme={null}
import { Composio } from '@composio/core';
```

The deprecated auth-config `uuid` response field was also removed. Use the canonical `id` field instead.

### TypeScript improvements

* `authConfigs.list()` adds `search` and `showDisabled` filters.
* Tool schema handling preserves and resolves internal `$defs` and `$ref` values for automatic file upload and download.
* Custom tools correctly convert both Zod 3 and Zod 4 schemas to JSON Schema.
* The Anthropic provider sanitizes unsupported input-schema property names and restores the original tool arguments before execution.

### Python fixes

* File fields hidden behind `$ref` or `$defs` are resolved before automatic upload and download handling.
* `tools.execute()` and `tools.proxy()` no longer retry non-idempotent writes, preventing duplicate side effects after timeouts, 429s, or 5xx responses.
* Session file transfers and presigned S3 requests now use bounded connect and read timeouts, surfacing typed file errors rather than hanging.
* Provider tool schemas safely alias Python-invalid parameter names, preserve the original names for execution, and avoid mutating OpenAI Agents source schemas.

**Jun 19, 2026**

TypeScript SDK 0.11.0 removes the legacy custom-tool registry and improves trigger ownership, schemas, file handling, and provider tool arguments.

## TypeScript SDK 0.11.0 moves custom tools to Tool Router

TypeScript SDK `@composio/core` `0.11.0` removes the old in-memory custom-tool registry. Custom tools now have one home: Tool Router sessions.

### SDK versions

| SDK | Version |
| - | - |
| TypeScript `@composio/core` | `0.11.0` |

### Breaking change

> [!WARNING]
>
> **Breaking change**
>
> `composio.tools.createCustomTool(...)` was removed. Because the SDK is still pre-1.0, this shipped as a minor release. Existing `^0.10.0` ranges do not upgrade to `0.11.0` automatically.

**Before:**

```typescript theme={null}
const tool = composio.tools.createCustomTool({ /* ... */ });
```

**After:**

```typescript theme={null}
import { experimental_createTool } from '@composio/core';

const tool = experimental_createTool('GREP', {
  name: 'Grep Search',
  description: 'Search local files',
  inputParams: /* zod schema */,
  execute: async (input) => ({ input }),
});

await composio.create('user_123', {
  experimental: { customTools: [tool] },
});
```

Use `experimental_createToolkit(...)` when several local tools belong together. The `experimental_*` names are intentional: this API is still evolving.

### Improvements and fixes

* `triggers.create()` now forwards `userId`, enabling trigger 2FA ownership checks.
* Telemetry sends no longer delay SDK results or rethrown errors.
* Automatic file handling now selects the correct branch for schemas that accept either one file or a list of files.
* Providers normalize model-produced JSON-string tool arguments and raise `ComposioInvalidToolArgumentsError` for invalid values instead of leaking raw parser errors.
* MCP-backed toolkits with empty or missing output schemas no longer fail validation. Mastra also tolerates unresolved backend `$ref` values without making the whole tool list unusable.

**Jun 18, 2026**

Python SDK 0.15.0 forwards user\_id when creating triggers so 2FA-enabled projects can verify connected-account ownership.

## Python SDK 0.15.0 supports trigger 2FA ownership checks

Python SDK `composio` `0.15.0` forwards `user_id` from `triggers.create()` to the trigger upsert request. This lets projects with trigger 2FA verify that the connected account belongs to the caller.

### SDK versions

| SDK | Version |
| - | - |
| Python `composio` | `0.15.0` |

No call-site migration is required. Pass `user_id` to `triggers.create()` when the trigger should be associated with a specific user.

**Jun 17, 2026**

The PostHog region is now a per-connection setting. Existing connections keep their current region, so nothing changes for you.

## PostHog connections: set your data region (US or EU) per connection

The PostHog **region** (`us` or `eu`) now lives on the **connection** instead of the auth config. Region is genuinely per-connection — different users can sit in different PostHog regions — so fixing it at the auth config forced everyone through one region. Each connection now carries its own.

You don't need to do anything. We migrated every existing connection with no re-auth: connections on the default (`us`) stay on `us`, and any that used another region such as `eu` keep that value.

### Going forward

* Set `us` (US Cloud) or `eu` (EU Cloud) on the connection. The host is built as `<region>.posthog.com`, so a full URL won't work and self-hosted PostHog isn't supported.
* [**Link flow**](https://composio-preview.mintlify.site/reference/api-reference/connected-accounts/postConnectedAccountsLink.md): the Region field appears when the user connects, prefilled with your default and editable.
* [**Initiate flow**](https://composio-preview.mintlify.site/reference/api-reference/connected-accounts/postConnectedAccounts.md): you set the region, and the end user never sees it.

### Setting a default on your auth config

An auth config's region default lives in its `shared_credentials`. If you were on the default (`us`), nothing was written there. To pin a region explicitly, set `shared_credentials` when you [create an auth config](https://composio-preview.mintlify.site/reference/api-reference/auth-configs/postAuthConfigs.md), or [patch an existing one](https://composio-preview.mintlify.site/reference/api-reference/auth-configs/patchAuthConfigsByNanoid.md).

See the [PostHog toolkit docs](https://composio-preview.mintlify.site/toolkits/posthog) for the current connection fields.

**Jun 16, 2026**

Python SDK 0.14.0 removes the legacy in-memory custom-tool registry. Tool Router custom tools remain the supported path.

## Python SDK 0.14.0 removes the legacy custom-tool registry

Python SDK `composio` `0.14.0` removes the legacy `composio.tools.custom_tool` registry. It was an older, separate custom-tool path that duplicated the Tool Router model and made it unclear which execution surface a tool belonged to.

### SDK versions

| SDK | Version |
| - | - |
| Python `composio` | `0.14.0` |

### Breaking change

> [!WARNING]
>
> **Breaking change**
>
> `composio.tools.custom_tool`, `core.models.custom_tools`, and their legacy execution wiring were removed. Use `composio.experimental.tool()` and `composio.experimental.Toolkit` with a Tool Router session instead.

The current custom-tool APIs support inline execution and Tool Router preload, attach, and reuse flows. They are the only custom-tool path supported by the SDK.

### Migration

1. Replace `@composio.tools.custom_tool` with `@composio.experimental.tool`.
2. Change the tool signature from a request object plus execution callback to `input, ctx`.
3. Attach the tool when creating the session through `experimental.custom_tools`.

Before:

```python theme={null}
from composio import Composio

composio = Composio()

@composio.tools.custom_tool
def add_two_numbers(request: AddTwoNumbersInput) -> int:
    return request.a + request.b
```

After:

```python theme={null}
from composio import Composio

composio = Composio()

@composio.experimental.tool
def add_two_numbers(input: AddTwoNumbersInput, ctx):
    return {"result": input.a + input.b}

session = composio.create(
    user_id="user_123",
    experimental={"custom_tools": [add_two_numbers]},
)
```

For a tool that calls a toolkit API, set `extends_toolkit` on the decorator and use `ctx.proxy_execute(...)` from the function body.

**Jun 4, 2026**

Recent changes across MCP and API authentication, Proxy Execute, connected accounts and triggers, token redaction, webhooks, rate limits, and retired legacy endpoints.

## Security, API, and platform updates

A summary of recent security, API, and platform changes you may need to act on. Most won't apply to you, so skim for the ones that do. We are continuing to ship more.

### Legacy MCP Config routes

* MCP requests now require an API key or `Authorization: Bearer` token. We recommend moving to `composio.create`

### API Keys

* IP whitelisting, choose which ip address can work from your api keys.
* Scoped API Key are slowly being rolled out with first preset for `proxyExecute`. You will be able to control what actions your api keys can take.

### Proxy Execute

* Proxy Execute is disabled on `v3` api, please use `v3.1` or update your sdks.
* Proxy Execute is now an opt-in capability on an API key, it is a superset of regular capabilities + proxy execute.
* Proxy Execute requests have a 250MB payload cap.

### Connections

* Connected-account tokens are redacted in API responses, for both Composio-managed and custom auth configs. Please use [Proxy Execute](https://composio-preview.mintlify.site/reference/api-reference/tools) instead. If you need this for some special case please reach out to support.
* Reiterating: Composio-managed OAuth connections are moving from `initiate` to `link`. The cutover for remaining organizations is July 3, 2026.

### Workbench

* Code execution through the remote workbench (`COMPOSIO_REMOTE_WORKBENCH`, `COMPOSIO_REMOTE_BASH_TOOL`) now runs only inside a [Composio session](https://composio-preview.mintlify.site/docs/how-composio-works.md). If your code execution stopped working, run it within a Composio session.

### Webhooks

* Webhook URLs must be publicly reachable; internal and loopback targets are now rejected.
* Deliveries are now signed (verify the `webhook-signature` header), and there is a new `composio.trigger.disabled` event. Manage subscriptions with the [Webhook Subscriptions API](https://composio-preview.mintlify.site/reference/api-reference/webhook-subscriptions).

### Rate limits

* Per-IP rate limits now apply; requests that exceed them receive `429` responses.

### Endpoints

* The legacy v1 and v2 endpoints, deprecated last year, have now been removed. Any calls to `/v1` or `v2` endpoints now return `410`, please use the class of `v3` and `v3.1` endpoints, if you need a guide to migration you can use [this](https://composio-preview.mintlify.site/docs/migration-guide/new-sdk.md)

**May 13, 2026**

Python SDK 0.13.1 adds experimental shared connected accounts, ACL helpers, and fixes legacy initiate warnings.

## Python SDK 0.13.1 adds experimental shared connections

Python SDK `composio` `0.13.1` adds experimental shared connected accounts. A shared connection can be pinned in a Tool Router session and used by another `user_id` only when its per-user ACL permits it.

### SDK versions

| SDK | Version |
| - | - |
| Python `composio` | `0.13.1` |

### Shared connections

Create a shared connection with `connected_accounts.link(..., experimental={...})`, update its ACL with `experimental.update_acl(...)`, and use the same experimental shape from `session.authorize(...)`. `connected_accounts.list()` also accepts the `PRIVATE`, `SHARED`, and `ALL` account-type filters.

> [!NOTE]
>
> Shared connections are experimental. Their shape may change, so pin a specific SDK version if your application depends on the current API.

This release also fixes false-positive `initiate()` deprecation warnings for custom and non-OAuth auth configs, preserves null-only `anyOf` schema branches, and adds typed errors for invalid shared-connection operations.

**May 12, 2026**

Programmatically revoke a connected account's tokens at the upstream provider

## New Endpoint: Revoke OAuth 2.0 Tokens for a Connected Account

You can now programmatically revoke a connected account's OAuth 2.0 tokens at the upstream provider, giving you explicit control over when credentials are killed at the third-party — instead of relying on deletion or natural token expiry.

### The Endpoint

```http theme={null}
POST /api/v3.1/connected_accounts/{nanoid}/revoke
```

On success, the connection transitions to `REVOKED` and the response reports which token subjects were killed at the provider on this call.

**Example request:**

```bash theme={null}
curl -X POST 'https://backend.composio.dev/api/v3.1/connected_accounts/ca_1a2b3c4d5e6f/revoke' \
  --header 'x-api-key: <YOUR_API_KEY>'
```

**Example response (`200 OK`):**

```json theme={null}
{
  "revoked_tokens": ["access_token", "refresh_token"],
  "connected_account": {
    "id": "ca_1a2b3c4d5e6f",
    "status": "REVOKED"
  }
}
```

The `revoked_tokens` array lists the subjects revoked at the provider during this call. An empty array means the connection was already in a revoked state and no upstream dispatch was issued.

### Status Codes

| Code | Meaning |
| - | - |
| `200` | Connection revoked (or already revoked — see `revoked_tokens`) |
| `400` | Revoke is not supported for this toolkit |
| `404` | Connected account does not exist |
| `409` | Connection is not in a revokable state (only `ACTIVE` and already-`REVOKED` are accepted) |
| `500` | Server error — revocation could not be completed |

### Revoke Is Not Automatic on Delete

Deleting a connected account or a project does **not** revoke tokens at the upstream provider — the credentials are removed from Composio but may remain live at the third-party until they expire naturally. If you need credentials killed at the provider, follow **revoke-then-delete** semantics: call `POST /revoke` first, then issue the delete.

### Revoke Is Best-Effort

Some providers do not expose a programmatic way to revoke one or both token subjects (for example, an access token but no refresh-token revoke route, or no revoke endpoint at all). In those cases, Composio revokes whatever the provider supports and the `revoked_tokens` array reflects exactly what was killed. Always read `revoked_tokens` to confirm which subjects were affected — do not assume both `access_token` and `refresh_token` were revoked on every call.

### Externally Revoked Tokens

If a user revokes the connection directly with the provider (for example, removing the app from their account on the provider's website), the upstream revoke call from this endpoint may return an error. Handle this case by treating the connection as already revoked on your side.

**May 8, 2026**

composio.use() rehydrates sessions for multi-turn chat, session.update() patches config in-place, and connectedAccounts now accepts arrays.

## Session reuse, update, and connected accounts as arrays

### Session reuse with `composio.use()`

`composio.create()` now returns a new session ID on every call, even for identical configs, for better isolation and observability. For multi-turn conversations, store the session ID and reuse it with `composio.use()`:

> [tab] Python
>
> ```python theme={null}
> from composio import Composio
>
> composio = Composio()
>
> # First request
> session = composio.create(user_id="user_123")
> session_id = session.session_id
>
> # Subsequent requests
> session = composio.use(session_id)
> tools = session.tools()
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from '@composio/core';
> const composio = new Composio({ apiKey: 'your_api_key' });
> // First request
> const session = await composio.create("user_123");
> const sessionId = session.sessionId;
>
> // Subsequent requests
> const session = await composio.use(sessionId);
> const tools = await session.tools();
> ```

Custom tools can also be attached when reusing a session. See [Reusing a session](https://composio-preview.mintlify.site/docs/how-composio-works.md#how-sessions-behave) and [Custom tools](https://composio-preview.mintlify.site/docs/extending-sessions/custom-tools-and-toolkits.md#reusing-a-session-with-custom-tools).

### Update session config with `session.update()`

Modify a session's toolkits, auth configs, connected accounts, and other settings without creating a new session. Only the fields you pass are changed:

> [tab] Python
>
> ```python theme={null}
> session.update(
>     toolkits=["gmail", "slack"],
>     auth_configs={"gmail": "ac_new_config"},
> )
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from '@composio/core';
> const composio = new Composio({ apiKey: 'your_api_key' });
> const session = await composio.create("user_123");
> await session.update({
>   toolkits: ["gmail", "slack"],
>   authConfigs: { gmail: "ac_new_config" },
> });
> ```

See [Updating a session](https://composio-preview.mintlify.site/docs/how-composio-works.md#how-sessions-behave).

### `connectedAccounts` accepts arrays

`connectedAccounts` (TypeScript) and `connected_accounts` (Python) now accept an array of connected account IDs per toolkit. A single string is still accepted for backwards compatibility and is automatically coerced to an array.

> [tab] Python
>
> ```python theme={null}
> session = composio.create(
>     user_id="user_123",
>     connected_accounts={
>         "gmail": ["ca_work_gmail"],
>     },
> )
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from '@composio/core';
> const composio = new Composio({ apiKey: 'your_api_key' });
> const session = await composio.create("user_123", {
>   connectedAccounts: {
>     gmail: ["ca_work_gmail"],
>   },
> });
> ```

Only one account per toolkit is allowed when [multi-account mode](https://composio-preview.mintlify.site/docs/authentication/managing-multiple-connected-accounts.md) is disabled.

### SDK versions

| SDK | Minimum version |
| - | - |
| TypeScript `@composio/core` | `0.9.1` |
| Python `composio` | `0.13.0` |

**May 7, 2026**

Sessions can now expose frequently used tools directly from session.tools(), and specialized agents can use a direct tools preset with selected meta tools enabled as needed.

## Sessions add preloaded tools and direct tools preset

Sessions now support preloading frequently used tools into `session.tools()` and the session MCP tool list, so agents can call them without searching each time. This works for Composio-managed tools, while SDK custom tools can be exposed directly from `session.tools()` with `preload: true`.

Keep the preloaded set focused, generally fewer than 20 tools, to avoid context bloat.

### SDK versions

| SDK | Minimum version |
| - | - |
| TypeScript `@composio/core` | `0.9.0` |
| Python `composio` | `0.13.0` |

> [tab] Python
>
> ```python theme={null}
> from composio import Composio
> from composio_openai_agents import OpenAIAgentsProvider
>
> composio = Composio(
>     api_key="your_api_key",
>     provider=OpenAIAgentsProvider(),
> )
>
> session = composio.create(
>     user_id="user_123",
>     toolkits=["gmail"],
>     preload={
>         "tools": ["GMAIL_FETCH_EMAILS", "GMAIL_CREATE_EMAIL_DRAFT"],
>     },
> )
>
> tools = session.tools()
> print([tool.name for tool in tools])
> # GMAIL_FETCH_EMAILS
> # GMAIL_CREATE_EMAIL_DRAFT
> # COMPOSIO_SEARCH_TOOLS
> # ... other default meta tools
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from '@composio/core';
> import { OpenAIAgentsProvider } from '@composio/openai-agents';
>
> const composio = new Composio({
>   apiKey: 'your_api_key',
>   provider: new OpenAIAgentsProvider(),
> });
>
> const session = await composio.create('user_123', {
>   toolkits: ['gmail'],
>   preload: {
>     tools: ['GMAIL_FETCH_EMAILS', 'GMAIL_CREATE_EMAIL_DRAFT'],
>   },
> });
>
> const tools = await session.tools();
> console.log(tools.map((tool) => tool.name));
> // GMAIL_FETCH_EMAILS
> // GMAIL_CREATE_EMAIL_DRAFT
> // COMPOSIO_SEARCH_TOOLS
> // ... other default meta tools
> ```

### Direct tools preset

Specialized agents with a narrow tool set can use the direct tools preset to load every tool allowed by session filters into the session's tool list and disable session meta tools by default.

> [tab] Python
>
> ```python theme={null}
> from composio import Composio, SESSION_PRESET_DIRECT_TOOLS
> from composio_openai_agents import OpenAIAgentsProvider
>
> composio = Composio(
>     api_key="your_api_key",
>     provider=OpenAIAgentsProvider(),
> )
>
> session = composio.create(
>     user_id="user_123",
>     toolkits=["gmail"],
>     tools={
>         "gmail": {
>             "enable": ["GMAIL_FETCH_EMAILS", "GMAIL_CREATE_EMAIL_DRAFT"],
>         },
>     },
>     session_preset=SESSION_PRESET_DIRECT_TOOLS,
> )
>
> tools = session.tools()
> print([tool.name for tool in tools])
> # GMAIL_FETCH_EMAILS
> # GMAIL_CREATE_EMAIL_DRAFT
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio, SessionPreset } from '@composio/core';
> import { OpenAIAgentsProvider } from '@composio/openai-agents';
>
> const composio = new Composio({
>   apiKey: 'your_api_key',
>   provider: new OpenAIAgentsProvider(),
> });
>
> const session = await composio.create('user_123', {
>   toolkits: ['gmail'],
>   tools: {
>     gmail: {
>       enable: ['GMAIL_FETCH_EMAILS', 'GMAIL_CREATE_EMAIL_DRAFT'],
>     },
>   },
>   sessionPreset: SessionPreset.DIRECT_TOOLS,
> });
>
> const tools = await session.tools();
> console.log(tools.map((tool) => tool.name));
> // GMAIL_FETCH_EMAILS
> // GMAIL_CREATE_EMAIL_DRAFT
> ```

For agents that still need selected helper behavior, supported meta tool groups can be enabled alongside the preset:

> [tab] Python
>
> ```python theme={null}
> from composio import Composio, SESSION_PRESET_DIRECT_TOOLS
> from composio_openai_agents import OpenAIAgentsProvider
>
> composio = Composio(
>     api_key="your_api_key",
>     provider=OpenAIAgentsProvider(),
> )
>
> session = composio.create(
>     user_id="user_123",
>     toolkits=["gmail"],
>     tools={
>         "gmail": {
>             "enable": ["GMAIL_FETCH_EMAILS", "GMAIL_CREATE_EMAIL_DRAFT"],
>         },
>     },
>     session_preset=SESSION_PRESET_DIRECT_TOOLS,
>     manage_connections={"enable": True},
>     workbench={"enable": True},
> )
>
> tools = session.tools()
> print([tool.name for tool in tools])
> # GMAIL_FETCH_EMAILS
> # GMAIL_CREATE_EMAIL_DRAFT
> # COMPOSIO_MANAGE_CONNECTIONS
> # COMPOSIO_REMOTE_WORKBENCH
> # COMPOSIO_REMOTE_BASH_TOOL
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio, SessionPreset } from '@composio/core';
> import { OpenAIAgentsProvider } from '@composio/openai-agents';
>
> const composio = new Composio({
>   apiKey: 'your_api_key',
>   provider: new OpenAIAgentsProvider(),
> });
>
> const session = await composio.create('user_123', {
>   toolkits: ['gmail'],
>   tools: {
>     gmail: {
>       enable: ['GMAIL_FETCH_EMAILS', 'GMAIL_CREATE_EMAIL_DRAFT'],
>     },
>   },
>   sessionPreset: SessionPreset.DIRECT_TOOLS,
>   manageConnections: {
>     enable: true,
>   },
>   workbench: {
>     enable: true,
>   },
> });
>
> const tools = await session.tools();
> console.log(tools.map((tool) => tool.name));
> // GMAIL_FETCH_EMAILS
> // GMAIL_CREATE_EMAIL_DRAFT
> // COMPOSIO_MANAGE_CONNECTIONS
> // COMPOSIO_REMOTE_WORKBENCH
> // COMPOSIO_REMOTE_BASH_TOOL
> ```

See [Preloading tools](https://composio-preview.mintlify.site/docs/configuring-sessions.md#preloading-tools), [Direct tools preset](https://composio-preview.mintlify.site/docs/configuring-sessions.md#direct-tools-preset), and [Preloading custom tools](https://composio-preview.mintlify.site/docs/extending-sessions/custom-tools-and-toolkits.md#preloading-custom-tools) for Python examples and full guidance.

**Apr 28, 2026**

TypeScript and Python `connectedAccounts.link()` now refuse to create a second active connection on the same auth config unless `allowMultiple` / `allow_multiple` is set, mirroring `initiate()`. Patch releases. TypeScript and Python SDKs gain `workbench.sandboxSize` / `workbench.sandbox_size` to pick the workbench sandbox tier (standard, medium, large, xlarge). Patch releases.

## SDKs: `link()` matches `initiate()` for the multi-connection guard

`composio.connectedAccounts.link()` (TypeScript) and `composio.connected_accounts.link()` (Python) now match the multi-connection guard that `initiate()` already had. With Composio-managed redirectable-OAuth callers being [migrated off `POST /api/v3/connected_accounts` onto `POST /api/v3/connected_accounts/link`](https://composio-preview.mintlify.site/docs/changelog/2026/04/24), the guard moves with them — so the migration doesn't quietly drop the duplicate-connection check.

> [!WARNING]
>
> **Behavior change**
>
> Before: `link()` would happily create a second `ACTIVE` connection for the same `(user_id, auth_config_id)` pair without checking for an existing `ACTIVE` connection first.
>
> After: `link()` first calls `connectedAccounts.list({ userIds, authConfigIds, statuses: ['ACTIVE'] })`. If any active connection exists, `link()` throws `ComposioMultipleConnectedAccountsError` unless the caller passes `allowMultiple: true` (TypeScript) / `allow_multiple=True` (Python).

### SDK versions (patch releases)

| Package | Previous | This release |
| - | - | - |
| TypeScript `@composio/core` | v0.8.0 | **v0.8.1** |
| Python `composio` | v0.12.0 | **v0.12.1** |

### Migration

Most callers don't need to do anything — `link()` raised an unrelated error or succeeded by accident in the duplicate-connection case before, and now raises a typed error you can handle. Two scenarios that need attention:

**1. You intentionally create multiple connections per `(user, auth_config)`** — for example, two Gmail accounts for the same user. Opt in:

> [tab] Python
>
> ```python theme={null}
> connection_request = composio.connected_accounts.link(
>     user_id="user_123",
>     auth_config_id="ac_xxx",
>     alias="work-gmail",
>     allow_multiple=True,
> )
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from '@composio/core';
> const composio = new Composio({ apiKey: process.env.COMPOSIO_API_KEY! });
> const connectionRequest = await composio.connectedAccounts.link(
>   'user_123',
>   'ac_xxx',
>   { alias: 'work-gmail', allowMultiple: true },
> );
> ```

Pair with a session-level `multiAccount` / `multi_account` config so the agent can disambiguate at execution time. See [Managing multiple connected accounts](https://composio-preview.mintlify.site/docs/authentication/managing-multiple-connected-accounts.md) for the session shape.

**2. You're migrating from `initiate()` to `link()`** as part of the [Composio-managed OAuth migration](https://composio-preview.mintlify.site/docs/changelog/2026/04/24). Pass `allow_multiple` / `allowMultiple` through unchanged — same flag name, same default (`False`), same exception (`ComposioMultipleConnectedAccountsError`).

### Why

The migration changelog moves callers off `connected_accounts/create` onto `/link`. `initiate()` had `allow_multiple` and the duplicate-connection check; `link()` didn't. Without this fix, every customer who migrates would silently lose the guard and start creating duplicate `ACTIVE` connections on auth configs that were never meant to hold more than one. This release closes that gap.

## SDKs add sandbox compute tier for Tool Router workbench

The Composio SDKs now let you pick the compute tier of the [sandbox](https://composio-preview.mintlify.site/docs/sandbox/remote.md) when creating a Tool Router session. Heavier code execution and larger in-memory data benefit from a bigger sandbox.

| Tier | vCPU | RAM |
| - | - | - |
| `standard` | 1 | 1 GB |
| `medium` | 2 | 2 GB |
| `large` | 4 | 4 GB |
| `xlarge` | 8 | 8 GB |

The field is optional and defaults to `standard` server-side when omitted, so existing code keeps working unchanged.

> [!NOTE]
>
> **Pricing:** Sandboxes are not billed today. Composio plans to begin billing for sandbox usage soon (metered by tier and runtime). Pick a tier that matches your workload — but expect future pricing to track actual usage.

### SDK versions (patch releases)

| Package | Previous | This release |
| - | - | - |
| TypeScript `@composio/core` | v0.8.0 | **v0.8.1** |
| Python `composio` | v0.12.0 | **v0.12.1** |

### Usage

**TypeScript** (camelCase on the SDK surface):

```typescript theme={null}
import { Composio } from '@composio/core';
const composio = new Composio({ apiKey: process.env.COMPOSIO_API_KEY! });

const session = await composio.create('user_123', {
  workbench: {
    enable: true,
    sandboxSize: 'large',
  },
});
```

The `SandboxSize` literal type and `SandboxSizeSchema` zod enum are exported from `@composio/core`.

**Python** (snake\_case throughout):

```python theme={null}
session = composio.create(
    user_id="user_123",
    workbench={
        "sandbox_size": "large",
    },
)
```

The `SandboxSize` literal alias is available at `composio.core.models.tool_router.SandboxSize`.

### Updating an existing session

Calling `session.update()` (or the equivalent `PATCH /api/v3/tool_router/sessions/{id}`) with a different `sandbox_size` recreates the sandbox on next access. The sandbox's in-memory filesystem state is lost, but the persistent `/mnt/files/` mount survives the restart.

See [Configuring Sessions → Sandbox compute tier](https://composio-preview.mintlify.site/docs/configuring-sessions.md#sandbox-compute-tier) for the full reference.

**Apr 27, 2026**

Dedicated webhook endpoint per OAuth app, ingress-level signature verification, per-user authorization for private channels and DMs, and config-level event filters. Opt-in; V1 is unchanged.

## Webhook Triggers V2

Webhook Triggers V2 introduces a first-class `webhook_endpoints` resource with a dedicated ingress URL per OAuth app. V2 is **opt-in** and scoped to new trigger slugs — existing V1 triggers, URLs, and payload formats are unchanged.

## Summary

| Change | Action required |
| - | - |
| New `webhook_endpoints` API | None (opt-in) |
| New ingress path `/api/v3.1/webhook_ingress/{toolkit}/{we_*}/trigger_event` | None (opt-in) |
| Ingress-level signature verification | Automatic for V2 endpoints |
| New Slack V2 slugs (`SLACK_CHANNEL_MESSAGE_RECEIVED`, `SLACK_DIRECT_MESSAGE_RECEIVED`, `SLACK_MESSAGE_REACTION_ADDED`) | Opt-in |
| V1 ingress path and all legacy trigger slugs | None — unchanged |

## What's in V2

**Dedicated endpoint per OAuth app.** Each `webhook_endpoint` is keyed by `(toolkit_slug, project_id, client_id)` and exposes its own URL containing a random `we_*` identifier:

```text theme={null}
https://backend.composio.dev/api/v3.1/webhook_ingress/{toolkit}/{we_xxx}/trigger_event
```

This replaces V1's shared `/handle` URL per toolkit. Events arriving on a V2 URL are fanned out only to trigger instances on that endpoint's project.

**Signature verification at ingress.** Composio cryptographically verifies every V2 request against the signing secret stored on the endpoint, using HMAC-SHA256, Ed25519, or shared-token matching depending on the toolkit. Unsigned or tampered payloads are rejected, so third parties cannot spoof events onto your triggers. For providers that sign a request timestamp (e.g. Slack), replay protection additionally rejects requests whose timestamp falls outside the allowed skew window.

**Per-user authorization for app-level events.** On toolkits with per-user visibility — Slack being the first — V2 uses an app-level token (for Slack, an `xapp-…` token with `authorizations:read`) to resolve which connected users are authorized for a given event, so only those users' triggers fire. This underpins a new class of triggers for private channels, direct messages, and other per-recipient events, each routed only to the user the event was intended for.

**Automatic handshakes and cleanup.** Composio responds to provider verification challenges — Slack `url_verification`, Asana `X-Hook-Secret`, Outlook validation tokens, and so on — so callback URLs verify without any custom code. User-level webhooks are also deregistered on the provider side when the trigger is deleted.

## API reference

All endpoints require a project API key (`x-api-key`).

| Method | Path | Purpose |
| - | - | - |
| `GET` | `/api/v3.1/webhook_endpoints/schema?toolkit_slug={slug}` | List required setup fields for a toolkit |
| `POST` | `/api/v3.1/webhook_endpoints` | Create an endpoint (idempotent per `toolkit_slug + client_id` within a project) |
| `GET` | `/api/v3.1/webhook_endpoints` | List endpoints in the current project |
| `GET` | `/api/v3.1/webhook_endpoints/{id}` | Get a single endpoint, including `verified_at` |
| `POST` | `/api/v3.1/webhook_endpoints/{id}` | Replace `setup_data` |
| `PATCH` | `/api/v3.1/webhook_endpoints/{id}` | Update one or more fields in `setup_data` |

Provider events are posted to:

| Method | Path |
| - | - |
| `POST` | `/api/v3.1/webhook_ingress/{toolkit_slug}/{webhook_endpoint_nano_id}/trigger_event` |

## Migration walkthrough (Slack)

Slack is the first toolkit on V2. The same flow applies to every toolkit added later.

### 1. Discover required fields

```bash theme={null}
curl "https://backend.composio.dev/api/v3.1/webhook_endpoints/schema?toolkit_slug=slack" \
  -H "x-api-key: YOUR_API_KEY"
```

Sample response:

```json theme={null}
{
  "toolkit_slug": "slack",
  "setup_fields": {
    "webhook_signing_secret": {
      "display_name": "Signing Secret",
      "description": "Webhook request signing secret from your Slack app dashboard",
      "is_required": true,
      "is_secret": true
    },
    "app_token": {
      "display_name": "App-Level Token",
      "description": "Slack xapp- token with authorizations:read scope for event authorization",
      "is_required": true,
      "is_secret": true
    }
  }
}
```

### 2. Create the endpoint

```bash theme={null}
curl -X POST "https://backend.composio.dev/api/v3.1/webhook_endpoints" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "toolkit_slug": "slack", "client_id": "YOUR_SLACK_CLIENT_ID" }'
```

Sample response:

```json theme={null}
{
  "id": "we_abc123",
  "toolkit_slug": "slack",
  "client_id": "YOUR_SLACK_CLIENT_ID",
  "webhook_url": "https://backend.composio.dev/api/v3.1/webhook_ingress/slack/we_abc123/trigger_event",
  "data": null,
  "created_at": "2026-04-24T10:00:00.000Z"
}
```

Hold on to two values from the response: `id` (used as `ENDPOINT_ID` in the next steps) and `webhook_url` (the URL you'll paste into your Slack app dashboard in step 5). The call is idempotent — calling it again with the same `toolkit_slug` and `client_id` returns the existing endpoint.

### 3. Store the signing secret

```bash theme={null}
curl -X PATCH "https://backend.composio.dev/api/v3.1/webhook_endpoints/ENDPOINT_ID" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "data": { "webhook_signing_secret": "YOUR_SIGNING_SECRET" } }'
```

> [!WARNING]
>
> Store the signing secret before switching the provider's callback URL. If Slack posts to a V2 URL without a secret available, every request fails with `400` and Slack may auto-disable the endpoint after \~36 hours of failures.

### 4. Add an app-level token for private-scope events

The app-level token is what lets Composio resolve per-user authorization for Slack's private-scope events.

* `SLACK_DIRECT_MESSAGE_RECEIVED` always requires it.
* `SLACK_CHANNEL_MESSAGE_RECEIVED` requires it for events from **private channels** and **multi-person DMs**; public-channel messages are delivered without it.

Skip this step if you only need public-channel messages today — you can add the token later.

```bash theme={null}
curl -X PATCH "https://backend.composio.dev/api/v3.1/webhook_endpoints/ENDPOINT_ID" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "data": { "app_token": "xapp-..." } }'
```

Generate the token from **Slack app → Basic Information → App-Level Tokens** with scope `authorizations:read`.

### 5. Point your Slack app at the V2 URL

Set **Event Subscriptions → Request URL** in your Slack app to the `webhook_url` returned in step 2. Composio verifies the endpoint with Slack automatically — no extra action needed on your side.

### 6. Create V2 trigger instances

Three new Slack triggers go live on V2 today, with more to follow on V2 — both for Slack and for other toolkits. The table below maps your existing V1 slugs to the new V2 equivalents:

| V1 slug (still supported) | V2 replacement | `app_token` required? |
| - | - | - |
| `SLACK_RECEIVE_MESSAGE` | `SLACK_CHANNEL_MESSAGE_RECEIVED` | Only for private channels and multi-person DMs; public channels work without it |
| `SLACK_RECEIVE_DIRECT_MESSAGE` | `SLACK_DIRECT_MESSAGE_RECEIVED` | Always |
| `SLACK_REACTION_ADDED` | `SLACK_MESSAGE_REACTION_ADDED` | Always (reactions don't carry channel type, so per-user authz runs unconditionally) |

```bash theme={null}
curl -X POST "https://backend.composio.dev/api/v3.1/trigger_instances/SLACK_CHANNEL_MESSAGE_RECEIVED/upsert" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "connected_account_id": "CONNECTED_ACCOUNT_ID",
    "trigger_config": {}
  }'
```

## Heads up: OAuth apps are project-scoped on V2

> [!WARNING]
>
> **Action required if you share a single OAuth app across multiple Composio projects or organizations today.** V2 ties each OAuth app (`client_id`) to exactly one project. Before moving such an app to V2, either consolidate to a single project or register separate OAuth apps per project.

The provider dashboard accepts only one callback URL per OAuth app, and each V2 URL resolves to exactly one project — so a single OAuth app cannot feed multiple projects on V2.

The signing secret also lives on the endpoint, so the reverse holds too: two different OAuth apps cannot share one V2 endpoint — Composio only verifies signatures against the secret stored on that endpoint, so requests signed by a different OAuth app would be rejected.

In return, every project graduates to a first-class webhook tenant on V2 — with its own:

* Ingress rate-limit and backpressure budget
* Clean fan-out — events reach only that project's trigger instances
* Signing secret and app-level token, scoped to this project alone
* Per-project metering and billing

Your V1 endpoints are unaffected. Any OAuth app you leave on V1 continues to work across projects exactly as it does today.

## Backward compatibility

**Everything you have today keeps working — same URLs, same trigger slugs, same payload shapes, no data migration.**

* The V1 ingress URL (`/api/v3/trigger_instances/{toolkit}/{project_id}/handle`) is not deprecated.
* Every existing trigger slug — `SLACK_RECEIVE_*`, `SLACKBOT_*`, and the equivalent legacy slugs on other toolkits — continues to route through V1.

You only need to set up a V2 webhook endpoint in two cases:

1. **You want to use one of the new V2 trigger slugs** (e.g. `SLACK_CHANNEL_MESSAGE_RECEIVED`, `SLACK_DIRECT_MESSAGE_RECEIVED`). A V2 endpoint is required at setup; without one, the upsert returns `400`.
2. **You want to move an OAuth app that's currently shared across multiple projects or organizations onto V2.** Pick the project that should own it on V2 and set up an endpoint there, or register separate OAuth apps per project (see [Heads up: OAuth apps are project-scoped on V2](#heads-up-oauth-apps-are-project-scoped-on-v2)).

Even outside these two cases, we recommend moving your OAuth apps to V2 at your own pace. Every endpoint you migrate inherits the signature verification, ingress isolation, and per-user authorization called out above.

**Apr 24, 2026**

SDKs remove deprecated `autoUploadDownloadFiles` / `auto_upload_download_files`. Automatic file handling is off unless you set `dangerouslyAllowAutoUploadDownloadFiles` / `dangerously_allow_auto_upload_download_files`. Minor releases. POST /api/v3/connected\_accounts will stop creating Composio-managed OAuth1/OAuth2/DCR\_OAUTH connections. Callers must migrate to POST /api/v3/connected\_accounts/link. Rollout begins Friday, May 8, 2026 for new organizations. The /api/v3/tools/execute/proxy endpoint rejects requests whose endpoint URL is on a different registrable domain than the connected account's base URL.

## SDKs remove legacy automatic file handling config

The Composio SDKs no longer accept the legacy flags that previously controlled automatic file upload and download during tool execution. Automatic handling of `file_uploadable` fields stays **off by default**; you opt in with the explicit `dangerously*` option only.

> [!WARNING]
>
> **Breaking change**
>
> Those legacy properties are removed from the public constructors and config types. Code that still passes them must migrate. Anyone who **relied on the old default-on behavior** (no file flag in the constructor) must now **explicitly** set the `dangerously*` flag to `true` to keep automatic path/URL file handling.

### SDK versions (minor releases)

| Package | Previous | This release |
| - | - | - |
| TypeScript `@composio/core` | v0.6.11 | **v0.8.0** |
| Python `composio` | v0.11.6 | **v0.12.0** |

Other `@composio/*` npm packages that depend on core are published as **patch** bumps in the same release train (via the changesets `updateInternalDependencies: "patch"` setting) so they pick up the updated `ComposioConfig` surface — they have no public-API changes of their own.

### Migration

Earlier SDK versions treated automatic file upload/download for `file_uploadable` tool fields as **on by default** (TypeScript: `autoUploadDownloadFiles` defaulted to `true` when unset; Python followed the same idea for `auto_upload_download_files` in prior releases). **That default is now off.** If you still want that behavior, you must **explicitly** set `dangerouslyAllowAutoUploadDownloadFiles: true` (TypeScript) or `dangerously_allow_auto_upload_download_files=True` (Python).

**TypeScript — before (legacy):**

```typescript theme={null}
// If you omitted autoUploadDownloadFiles, it used to default to true
new Composio({
  apiKey: process.env.COMPOSIO_API_KEY!,
});

// Equivalent when you set it explicitly:
new Composio({
  apiKey: process.env.COMPOSIO_API_KEY!,
  autoUploadDownloadFiles: true,
});
```

**TypeScript — going forward** (set `true` to match either legacy pattern above):

```typescript theme={null}
new Composio({
  apiKey: process.env.COMPOSIO_API_KEY!,
  dangerouslyAllowAutoUploadDownloadFiles: true,
});
```

To leave automatic file handling **off** (new default), omit `dangerouslyAllowAutoUploadDownloadFiles` or set it to `false`.

**Python — before (legacy):**

```python theme={null}
# If you omitted auto_upload_download_files, it used to default to True (prior releases)
Composio(api_key="...")

# Equivalent when you set it explicitly:
Composio(api_key="...", auto_upload_download_files=True)
```

**Python — going forward** (set `True` to match either legacy pattern above):

```python theme={null}
Composio(api_key="...", dangerously_allow_auto_upload_download_files=True)
```

If you construct `ToolRouterSession` directly (unusual), the keyword argument is now `dangerously_allow_auto_upload_download_files` instead of `auto_upload_download_files`.

### Local paths must live inside an allowlisted directory

Even with `dangerouslyAllowAutoUploadDownloadFiles` enabled, the SDK will **only** auto-upload local file paths that resolve inside an allowlisted directory. Paths outside the allowlist are rejected with `ComposioFileUploadPathNotAllowed` (TypeScript) / `FileUploadPathNotAllowed` (Python) before any file is read or sent.

This is a behavior change. Earlier SDK versions had no allowlist: any local path the legacy default-on flag saw was uploaded.

**Default allowlist:**

| `fileUploadDirs` value | Effective allowlist |
| - | - |
| omitted / `undefined` | `[ <home>/.composio/temp ]` (default staging dir) |
| `false` | `[]` — **all** local paths rejected (URLs and `File` objects still work) |
| `[]` | `[]` — same as `false`; explicit "no local paths" |
| `[<dir1>, <dir2>, …]` | exactly those directories (replaces the default; `~` is expanded, paths are `realpath`-resolved, comparison is on a path-component boundary) |

URLs (`http://…` / `https://…`) and JavaScript `File` objects are **not** subject to the allowlist — only local string paths are.

**TypeScript:**

```typescript theme={null}
// Match the *broadest* legacy behavior: auto-upload on, allowlist widened to
// the directories your code actually reads from. Set this scope as tightly
// as you can — every path inside these dirs becomes uploadable to Composio.
new Composio({
  apiKey: process.env.COMPOSIO_API_KEY!,
  dangerouslyAllowAutoUploadDownloadFiles: true,
  fileUploadDirs: ['/srv/uploads', '~/data/inbox'],
});

// Disallow local-path uploads entirely; the SDK will only stage URLs and
// File objects, and reject string paths outright.
new Composio({
  apiKey: process.env.COMPOSIO_API_KEY!,
  dangerouslyAllowAutoUploadDownloadFiles: true,
  fileUploadDirs: false,
});
```

**Python:**

```python theme={null}
# Equivalent of the TypeScript example above.
Composio(
    api_key="...",
    dangerously_allow_auto_upload_download_files=True,
    file_upload_dirs=["/srv/uploads", "~/data/inbox"],
)

# Reject all local paths.
Composio(
    api_key="...",
    dangerously_allow_auto_upload_download_files=True,
    file_upload_dirs=False,
)
```

**Manual staging (TypeScript only):**

If you don't want to widen the allowlist, the TypeScript SDK lets you stage files yourself via `composio.files.upload(...)`. That call **bypasses the allowlist** by design (the caller is expected to control the path), and the returned `{ name, mimetype, s3key }` descriptor can be passed straight into `tools.execute`:

```typescript theme={null}
const staged = await composio.files.upload({
  file: '/anywhere/on/disk/report.pdf',
  toolSlug: 'GOOGLEDRIVE_UPLOAD_FILE',
  toolkitSlug: 'googledrive',
});

await composio.tools.execute('GOOGLEDRIVE_UPLOAD_FILE', {
  userId: 'user-1',
  arguments: { file_to_upload: staged },
});
```

The Python SDK does not currently expose a top-level manual-staging API; opt in with `dangerously_allow_auto_upload_download_files=True` and configure `file_upload_dirs` to cover the directories your code reads from.

### What else changed

* TypeScript: `resolveAutoUploadDownloadFilesEnabled` only considers `dangerouslyAllowAutoUploadDownloadFiles`; the old deprecation warning for the legacy property is removed.
* Python: the small `composio.utils.auto_upload_download` helper that merged legacy + new flags is removed; `Tools` and `ToolRouter` take only the explicit opt-in boolean.

Documentation for [executing tools](https://composio-preview.mintlify.site/docs/tools-direct/executing-tools.md) and the TypeScript [Composio reference](https://composio-preview.mintlify.site/reference/sdk-reference/typescript/composio.md) is updated to describe defaults and the opt-in flag.

## Link Auth Migration for Composio-Managed OAuth Connections

`POST /api/v3/connected_accounts` is being retired for **Composio-managed OAuth connections**. New organizations begin migrating on **Friday, May 8, 2026**, and all remaining organizations follow on **Friday, July 3, 2026**. Once migrated, affected requests receive `400 BadRequest` with a message pointing at the replacement endpoint.

This does **not** affect custom auth configs (your own OAuth app) or non-OAuth schemes (API key, bearer token, basic auth, etc.) — those continue to work on `POST /api/v3/connected_accounts` unchanged. Only the specific combination of **Composio-managed auth config + redirectable OAuth scheme** (OAuth1, OAuth2, DCR\_OAUTH) is moving.

> [!WARNING]
>
> **Breaking Change (phased rollout)**
>
> If your integration calls `POST /api/v3/connected_accounts` for a Composio-managed OAuth1, OAuth2, or DCR\_OAUTH auth config, it will start returning `400 BadRequest` on the dates below. Migrate to `POST /api/v3/connected_accounts/link` before your organization's cutover.
>
> * **Friday, May 8, 2026 (00:00 UTC)** — organizations created on or after this timestamp are blocked.
> * **Friday, July 3, 2026 (00:00 UTC)** — all remaining organizations are blocked.

### What's Changing

| Request | Before | After (once rollout reaches your org) |
| - | - | - |
| `POST /api/v3/connected_accounts`, Composio-managed + OAuth1 / OAuth2 / DCR\_OAUTH | Creates a connected account (redirect URL returned) | **`400 BadRequest`** — use `/link` instead |
| `POST /api/v3/connected_accounts`, custom auth config | Creates a connected account | Unchanged |
| `POST /api/v3/connected_accounts`, API key / bearer / other non-OAuth | Creates a connected account | Unchanged |
| `POST /api/v3/connected_accounts/link` | Creates a link session | Unchanged — the recommended path going forward |

### Why

When a connection is initiated through a default (Composio-managed) auth config, a Composio-owned OAuth application is acting on behalf of your integration. We want the end user to explicitly understand and acknowledge, at the moment of connection, that they are granting a third-party application access to their account on the external service. That acknowledgement is enforced by the `/link` flow, which routes the user through a consent screen before the connection is created. The legacy `POST /api/v3/connected_accounts` path allowed that step to be bypassed when credentials were passed in directly, which this change closes.

Custom auth configs are unaffected because they are backed by your own OAuth application — the consent screen is served by your app, so you already own that experience. This change is scoped specifically to default auth configs on redirectable schemes, where the third-party relationship is with Composio rather than with the developer.

### Migration

**Before** — legacy create (will be rejected for Composio-managed OAuth):

```bash theme={null}
curl -X POST https://backend.composio.dev/api/v3/connected_accounts \
  -H "Content-Type: application/json" \
  -H "x-api-key: <YOUR_API_KEY>" \
  -d '{
    "auth_config": { "id": "ac_your_composio_managed_oauth_config" },
    "connection": { "user_id": "your_end_user_id" }
  }'
```

**After** — link session (recommended, works for all schemes including non-OAuth and custom):

```bash theme={null}
curl -X POST https://backend.composio.dev/api/v3/connected_accounts/link \
  -H "Content-Type: application/json" \
  -H "x-api-key: <YOUR_API_KEY>" \
  -d '{
    "auth_config_id": "ac_your_composio_managed_oauth_config",
    "user_id": "your_end_user_id"
  }'
```

The response contains a `redirect_url` (valid for 10 minutes) that the end user opens to authorize the integration, plus a `connected_account_id` you can use to poll for status or associate with your own records.

### Error Response (after rollout)

Requests that hit the retired combination receive:

```json theme={null}
{
  "error": {
    "code": "BadRequest",
    "message": "Creating connections on this endpoint for Composio-managed OAuth auth configs is no longer supported. Use POST /api/v3/connected_accounts/link instead.",
    "suggestedFix": "Call POST /api/v3/connected_accounts/link with the same auth_config_id and user_id to get a redirect URL for the end user."
  }
}
```

### What to Do

* **If you use Composio-managed OAuth auth configs** (OAuth1, OAuth2, or DCR\_OAUTH) via `POST /api/v3/connected_accounts`: switch to `POST /api/v3/connected_accounts/link` before your org's cutover — **Friday, May 8, 2026** for organizations created on or after that date, **Friday, July 3, 2026** for all others.
* **If you already use `/link`**: no action required.
* **If you use custom OAuth apps (your own `client_id` / `client_secret`) or non-OAuth auth (API key, bearer, etc.)**: no action required — the legacy endpoint continues to serve those cases.

## Proxy execute now enforces same-domain endpoints

To prevent a connection's `Authorization` header from being forwarded to an unintended host, the proxy execute endpoint (`POST /api/v3/tools/execute/proxy`) now requires that the outbound `endpoint` URL share the same scheme and registrable domain (eTLD+1) as the connection's resolved `base_url`.

Cross-subdomain requests on the same registrable domain continue to work — for example, a Gmail connection with base `https://gmail.googleapis.com` can still call `https://www.googleapis.com/...`. Relative endpoints (`/users/me/messages`) are resolved against the connection's `base_url` as before and are unaffected.

> [!WARNING]
>
> **Breaking Change**
>
> Existing proxy calls that pass an absolute `endpoint` URL whose registrable domain does not match the connection's `base_url` will now fail with `400 OriginMismatch` instead of being forwarded. Calls that omit both `connected_account_id` and `custom_connection_data` will fail with `400 MissingAuthContext` instead of being forwarded without auth.

### Migration

If you currently pass an absolute URL that points at a different domain than your connection's `base_url`, switch to a relative endpoint (resolved against `base_url`) or an absolute URL under the same registrable domain.

**Before** — absolute URL on a different domain (will be rejected):

```json theme={null}
{
  "endpoint": "https://api.someservice.com/v1/items",
  "method": "GET",
  "connected_account_id": "ca_..."
}
```

**After** — relative endpoint (recommended):

```json theme={null}
{
  "endpoint": "/v1/items",
  "method": "GET",
  "connected_account_id": "ca_..."
}
```

**Or** — absolute URL on the same registrable domain as the connection's `base_url`:

```json theme={null}
{
  "endpoint": "https://uploads.someservice.com/v1/items",
  "method": "GET",
  "connected_account_id": "ca_..."
}
```

If your integration legitimately needs to call a different registrable domain for the same connection, reach out so we can add the additional host to the toolkit allowlist.

### What changed

* Absolute `endpoint` URLs on a different registrable domain than the connection's `base_url` are rejected with HTTP `400 OriginMismatch`. The upstream request is never made.
* Proxy calls that provide neither `connected_account_id` nor `custom_connection_data` now return HTTP `400 MissingAuthContext` instead of being forwarded without auth.

### Examples

Assume a connected account whose toolkit `base_url` is `https://api.linear.app`.

**Allowed — relative endpoint:**

```bash theme={null}
curl -X POST https://backend.composio.dev/api/v3/tools/execute/proxy \
  -H 'x-api-key: <YOUR_API_KEY>' \
  -H 'Content-Type: application/json' \
  -d '{
    "endpoint": "/graphql",
    "method": "POST",
    "connected_account_id": "ca_..."
  }'
```

**Allowed — same registrable domain (different subdomain):**

```json theme={null}
{ "endpoint": "https://uploads.linear.app/...", "connected_account_id": "ca_..." }
```

**Rejected — different registrable domain:**

```json theme={null}
{ "endpoint": "https://attacker.example/leak", "connected_account_id": "ca_..." }
```

Response:

```json theme={null}
{
  "error": {
    "code": "OriginMismatch",
    "message": "Endpoint host does not match the connection's base_url host."
  }
}
```

### What to do

* If you call proxy execute with absolute URLs, make sure the host matches (or is a subdomain of) the connection's `base_url`.
* Prefer relative endpoints (`/path`) — they are resolved against `base_url` and are not affected by this change.
* If your integration legitimately needs to span multiple registrable domains for the same connection, reach out to us so we can add the additional host to the toolkit allowlist.

**Apr 23, 2026**

TypeScript and Python SDKs now block automatic uploads from common credential locations by default, support extra denylist segments, and offer a before-upload hook. New error types when a path is blocked or a hook aborts the upload. New composio.trigger.disabled event fires when Composio disables a trigger on your behalf — expired connection, webhook refresh failure, or unhealthy polling. Opt-in, V3-only.

## SDK file upload hardening: sensitive path blocking and upload hooks

The Composio SDKs add defense-in-depth for **automatic file uploads** (when a tool input is marked `file_uploadable` and the SDK reads a local path and sends the file to Composio storage). The goal is to reduce the risk of agent or app code accidentally exfiltrating secrets, SSH keys, or project env files that sit under well-known paths on disk.

**URLs and `File` objects are not subject to the path-based denylist** in the same way as string paths; the checks apply to resolved local filesystem paths used for auto-upload and the programmatic upload helpers that accept paths.

### SDK versions

| SDK | Version (includes this behavior) |
| - | - |
| TypeScript | `@composio/core` v0.6.11 or later |
| Python | `composio` v0.11.6 or later |

### What changed

* **Default sensitive path protection** — Before reading and uploading, the SDK checks the resolved local path against a built-in list of path segments (for example `.ssh`, `.aws`, `.claude`, `.kube`) and file-name patterns (for example `.env`, default SSH private key names, `credentials`). If the path matches, the upload is refused unless you change configuration.
* **Extra denylist segments** — You can add path component names to merge with the built-in list (for example a proprietary secrets directory name).
* **`beforeFileUpload` / `before_file_upload` hook** — Optional hook for each file upload: return a different path, return `false` to abort, or throw. TypeScript: pass `beforeFileUpload` on the third argument to `tools.execute`. Python: use [`@before_file_upload`](https://composio-preview.mintlify.site/reference/sdk-reference/python#before_file_upload) in the `modifiers` list (same as other Python modifiers), not a separate keyword. Use this to enforce app-specific policies, audit logging, or copy-on-write to a safe temp file before upload. See [Before file upload (Python)](https://composio-preview.mintlify.site/docs/tools-direct/modify-tool-behavior/before-execution-modifiers.md#before-file-upload-python).
* **New errors** — `ComposioSensitiveFilePathBlockedError` / `SensitiveFilePathBlockedError` when a path is blocked, and `ComposioFileUploadAbortedError` / `FileUploadAbortedError` when the hook returns `false` or a hook throws in an aborting way.
* **Python: modifier order** — `substitute_file_uploads` runs before `before_execute` modifiers, matching TypeScript behavior (including Tool Router `execute_meta`).

### Examples

#### Configure the client (defaults + extra denylist segments)

Keep the built-in blocklist enabled and add path **component** names (anywhere in the resolved path) that your app treats as secret:

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from '@composio/core';
>
> const composio = new Composio({
>   apiKey: process.env.COMPOSIO_API_KEY!,
>   sensitiveFileUploadProtection: true,
>   fileUploadPathDenySegments: ['company-secrets', 'private-keys'],
> });
> ```

> [tab] Python
>
> ```python theme={null}
> from composio import Composio
>
> composio = Composio(
>     api_key="your_composio_key",
>     sensitive_file_upload_protection=True,
>     file_upload_path_deny_segments=("company-secrets", "private-keys"),
> )
> ```

#### Run a hook before each automatic file read

Return a new path, return `false` / `False` to abort, or throw. TypeScript passes `beforeFileUpload` in the **third** argument to `tools.execute`. In Python, use [`@before_file_upload`](https://composio-preview.mintlify.site/reference/sdk-reference/python#before_file_upload) in `modifiers`:

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio, type beforeFileUploadModifier } from '@composio/core';
> import path from 'node:path';
>
> const composio = new Composio({ apiKey: process.env.COMPOSIO_API_KEY! });
>
> const beforeFileUpload: beforeFileUploadModifier = async ctx => {
>   // e.g. log, rewrite path, or return false to block
>   return ctx.path;
> };
>
> await composio.tools.execute(
>   'GOOGLEDRIVE_UPLOAD_FILE',
>   {
>     userId: 'user-123',
>     arguments: { file_to_upload: path.join(__dirname, 'document.pdf') },
>     dangerouslySkipVersionCheck: true,
>   },
>   { beforeFileUpload },
> );
> ```

> [tab] Python
>
> ```python theme={null}
> import os
>
> from composio import Composio, before_file_upload
>
> @before_file_upload(tools=["GOOGLEDRIVE_UPLOAD_FILE"])
> def before_upload(path: str, tool: str, toolkit: str) -> "str | bool":
>     return path
>
> composio = Composio()
>
> composio.tools.execute(
>     "GOOGLEDRIVE_UPLOAD_FILE",
>     {"file_to_upload": os.path.join(os.getcwd(), "document.pdf")},
>     user_id="user-123",
>     modifiers=[before_upload],
> )
> ```

### Opting out

Set **`sensitiveFileUploadProtection: false`** (TypeScript) or **`sensitive_file_upload_protection=False`** (Python) only if you have a clear reason and accept the security tradeoff. Prefer copying files to a non-sensitive path or using the hook to gate uploads.

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from '@composio/core';
>
> const composio = new Composio({
>   apiKey: process.env.COMPOSIO_API_KEY!,
>   sensitiveFileUploadProtection: false,
> });
> ```

> [tab] Python
>
> ```python theme={null}
> from composio import Composio
>
> composio = Composio(
>     api_key="your_composio_key",
>     sensitive_file_upload_protection=False,
> )
> ```

### Where to read more

* [Executing tools: automatic file handling and security options](https://composio-preview.mintlify.site/docs/tools-direct/executing-tools.md#security-for-local-file-paths) — configuration and code patterns.
* [TypeScript `Composio` client](https://composio-preview.mintlify.site/reference/sdk-reference/typescript/composio) — related constructor options in the reference.
* TypeScript SDK (repository): `ts/docs/advanced/auto-upload-download.md` — extended guide with error types and edge cases.

## Webhook Event for Auto-Disabled Triggers

`composio.trigger.disabled` is a new V3 webhook event that fires when Composio disables one of your triggers without a request from you — expired credentials, a failed webhook-subscription refresh, or unhealthy polling. It's opt-in: add it to a webhook subscription's `enabled_events` to receive it. Existing subscriptions for `composio.trigger.message` and `composio.connected_account.expired` are unaffected.

## When it fires

The event is emitted only for platform-initiated disables. `data.disabled_reason` names the cause:

| `disabled_reason` | What it means |
| - | - |
| `connection_expired` | The connected account entered `EXPIRED` and the trigger was paused. Auto-re-enabled when the account returns to `ACTIVE`. |
| `subscription_auth_failure` | The provider rejected the credentials when Composio tried to refresh the webhook subscription. Re-auth the connection to resolve. |
| `subscription_refresh_failure` | Composio could not reach the provider to refresh the webhook subscription (provider error, timeout, or network issue). Re-enable the trigger once the provider is healthy. |
| `polling_failure_in_composio_infra` | Composio's polling service failed to fetch events for this trigger after repeated retries. Rare in practice. |

The event does not fire when you disable a trigger yourself — neither through `PATCH /api/v3/trigger_instances/manage/{id}` nor by deactivating the connected account via `PATCH /api/v3/connected_accounts/{id}/status`.

## Subscribe

Add `composio.trigger.disabled` to your subscription's `enabled_events` — via the [dashboard webhook settings](https://dashboard.composio.dev/~/project/settings/webhook?utm_source=docs\&utm_medium=content\&utm_campaign=changelog-04-24-26-trigger-disabled-event) or the Webhook Subscriptions API:

```bash theme={null}
curl -X PATCH https://backend.composio.dev/api/v3/webhook_subscriptions/ws_your-subscription-id \
  -H "X-API-KEY: <your-composio-api-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "enabled_events": [
      "composio.trigger.message",
      "composio.trigger.disabled"
    ]
  }'
```

The event is V3-only. Subscriptions on V1 or V2 payloads cannot enable it.

## Payload

```json theme={null}
{
  "id": "msg_847cdfcd-d219-4f18-a6dd-91acd42ca94a",
  "type": "composio.trigger.disabled",
  "metadata": {
    "project_id": "pr_your-project-id"
  },
  "data": {
    "id": "ti_your-trigger-id",
    "connected_account_id": "ca_your-connected-account-id",
    "trigger_name": "GITHUB_COMMIT_EVENT",
    "user_id": "your-user-id",
    "trigger_config": { "owner": "composio", "repo": "hermes" },
    "disabled_at": "2026-04-23T11:59:59.000Z",
    "disabled_reason": "connection_expired"
  },
  "timestamp": "2026-04-23T12:00:00.000Z"
}
```

See [subscribing to triggers](https://composio-preview.mintlify.site/docs/setting-up-triggers/subscribing-to-events.md) for handler setup and [subscribing to connection expiry events](https://composio-preview.mintlify.site/docs/authentication#connection-lifecycle) for re-auth flows on `connection_expired`.

**Apr 22, 2026**

Composio-managed auth configs and their connections now redact sensitive fields in API responses. Customer-owned auth configs mask every credential field except the public OAuth identifiers.

## Credential Redaction for Composio-Managed Auth Configs and Connections

Two related security changes are rolling out together:

1. **Connections on Composio-managed auth configs** now always redact `access_token`, `refresh_token`, and the `Authorization` header in `connected-accounts` responses — independent of your project's `mask_secret_keys_in_connected_account` flag.
2. **Auth-config GET responses** now redact (for Composio-managed) or mask (for customer-owned) every sensitive credential field.

Auth-config credential redaction is **not controlled by `mask_secret_keys_in_connected_account`**. That project flag only applies to runtime connected-account credentials (access tokens, refresh tokens, and the like). Auth-config credentials are developer-owned static fields — `client_id`, `client_secret`, `developer_token`, etc. — and are always redacted or masked regardless of the `mask_secret_keys_in_connected_account` project flag.

**Most integrations need no changes.**

* Tool execution through the SDK, Tool Router, and MCP is unchanged. Composio uses the unredacted values server-side.
* Connections on customer-owned auth configs continue to follow your project's `mask_secret_keys_in_connected_account` setting for runtime tokens.

### What is a Composio-managed auth config?

When you connect a user through a toolkit's default integration — for example, Gmail or Slack without registering your own OAuth application — Composio uses an OAuth application it owns and shares across every team on that default. Tokens the provider issues are bound to that shared Composio-owned client.

You can identify a Composio-managed auth config or connection by `is_composio_managed: true` on the auth-config or connected-account resource.

### 1. Connected-account tokens

Access tokens, refresh tokens, and all header and query-parameter values are now replaced with the literal string `"REDACTED"` for Composio-managed connections. No prefix, no suffix — nothing that reveals the underlying value.

Before, with `mask_secret_keys_in_connected_account: false` on a Composio-managed Gmail connection:

```json theme={null}
{
  "state": {
    "val": {
      "access_token": "ya29.a0ARrdaM9...full token...",
      "refresh_token": "1//04...full token..."
    }
  },
  "data": {
    "headers": {
      "Authorization": "Bearer ya29.a0ARrdaM9...full token..."
    }
  }
}
```

After:

```json theme={null}
{
  "state": {
    "val": {
      "access_token": "REDACTED",
      "refresh_token": "REDACTED"
    }
  },
  "data": {
    "headers": {
      "Authorization": "REDACTED"
    }
  }
}
```

Connections on customer-owned auth configs are unaffected — token visibility follows your existing `mask_secret_keys_in_connected_account` setting (`xxxx...` truncation when enabled, raw passthrough when disabled).

If you were reading Composio-managed access or refresh tokens from these responses — typically because you use Composio for OAuth and then call the provider's APIs yourself — register your own OAuth application with the provider and [create a custom auth config](https://composio-preview.mintlify.site/reference/api-reference/auth-configs/postAuthConfigs.md) against those credentials. Tokens issued against an OAuth application you own belong to you and are returned in full (subject to `mask_secret_keys_in_connected_account`).

### 2. Auth-config credentials

`GET /api/v3/auth_configs` and `GET /api/v3/auth_configs/{id}` no longer return sensitive credentials in a recoverable form.

* **Composio-managed auth configs** — every credential field is redacted.
* **Customer-owned auth configs** — public OAuth identifiers (`client_id`, `consumer_key`) still pass through so you can debug OAuth flows. Every other credential field is obfuscated.

If your code reads a secret — for example `client_secret` or `developer_token` — out of these responses, you will need to keep that value alongside the code that created the auth config (typically in your own secret manager at upload time).

### Why this change

A single OAuth application backs every team on a Composio-managed default integration, and the tokens and client secrets bound to it are shared. If a provider throttles, restricts, or suspends that app in response to misuse of one of its credentials, the integration becomes unavailable for every team on the default at once. Redacting the values keeps them out of API responses; Composio still uses them server-side, so tool execution is unchanged.

For customer-owned auth configs, masking a freshly re-read `client_secret` or `developer_token` limits the blast radius of a compromised project API key without breaking your ability to identify which credential was uploaded.

### Affected endpoints

Connected accounts:

* [`GET /api/v3/connected_accounts/{id}`](https://composio-preview.mintlify.site/reference/api-reference/connected-accounts/getConnectedAccountsByNanoid)
* [`GET /api/v3/connected_accounts`](https://composio-preview.mintlify.site/reference/api-reference/connected-accounts/getConnectedAccounts)
* [`POST /api/v3/connected_accounts`](https://composio-preview.mintlify.site/reference/api-reference/connected-accounts/postConnectedAccounts)
* Webhook payloads that include connection credentials

Auth configs:

* [`GET /api/v3/auth_configs/{id}`](https://composio-preview.mintlify.site/reference/api-reference/auth-configs/getAuthConfigsByNanoid)
* [`GET /api/v3/auth_configs`](https://composio-preview.mintlify.site/reference/api-reference/auth-configs/getAuthConfigs)

> [!NOTE]
>
> If your integration relies on reading `access_token`, `refresh_token`, `client_secret`, or `developer_token` from Composio API responses, you will need to act. All other integrations continue to work as before.

**Apr 17, 2026**

Query individual tool execution logs and aggregated usage counts for your org or project via v3.1 REST endpoints.

## Observability APIs: tool execution logs and usage metering

Two new v3.1 observability API surfaces are live.

## Tool execution logs

Search, filter, and paginate individual tool execution events. Use this for debugging failures, inspecting request/response payloads, and tracing user activity.

* `POST /api/v3.1/logs/tool_execution` — list with filters, time range, and cursor pagination.
* `GET /api/v3.1/logs/tool_execution/{id}` — full detail including request payload, response body, timings, and source metadata.

Authentication: project API key (`x-api-key`) or session cookie.

See the [tool execution logs guide](https://composio-preview.mintlify.site/reference/api-reference/logs).

## Usage metering

Aggregated counts of tool calls and sessions. Summary endpoints return totals; breakdown endpoints group results by tool, toolkit, user, session, or project.

* `POST /api/v3.1/org/usage/summary` and `POST /api/v3.1/org/usage/{entity_type}` — org scope (`x-org-api-key` or org JWT).
* `POST /api/v3.1/project/usage/summary` and `POST /api/v3.1/project/usage/{entity_type}` — project scope (`x-api-key` or cookie).

Entity types: `tool_calls`, `sessions`. Time ranges are epoch milliseconds; max range 366 days.

See the [usage metering guide](https://composio-preview.mintlify.site/reference/api-reference/organization).

**Apr 9, 2026**

Enable multiple connected accounts per toolkit and label them with human-readable aliases

## Multi-Account Mode & Connection Aliases

This release adds two features for managing multiple accounts per toolkit.

## Multi-account mode

Sessions now support a `multiAccount` config that lets users connect and use multiple accounts for the same toolkit (e.g., work and personal Gmail) within a single session.

```typescript theme={null}
import { Composio } from '@composio/core';
const composio = new Composio({ apiKey: 'your_api_key' });
const session = await composio.create('user_123', {
  toolkits: ['gmail'],
  multiAccount: {
    enable: true,
    maxAccountsPerToolkit: 3,
  },
});
```

By default, multi-account mode is disabled and each session uses one account per toolkit.

## Connection aliases

Connected accounts can now have human-readable aliases (e.g., `"work-gmail"`, `"personal-github"`). Aliases can be set during connection or updated after.

```typescript theme={null}
import { Composio } from '@composio/core';
const composio = new Composio({ apiKey: 'your_api_key' });
const session = await composio.create('user_123');
// Set alias during connection
await session.authorize('gmail', { alias: 'work-gmail' });

// Update alias on an existing account
await composio.connectedAccounts.update('ca_abc123', { alias: 'work-gmail' });
```

Aliases must be unique per user and toolkit within a project.

See the [multi-account guide](https://composio-preview.mintlify.site/docs/authentication/managing-multiple-connected-accounts.md) for full details.

**Apr 8, 2026**

API v3.1 endpoints now default to the latest toolkit version for tool-related endpoints instead of the legacy pinned version.

## Introducing API v3.1 - Latest Tool Versions by Default

We're rolling out API v3.1 endpoints that change how tool versions are resolved. The key difference: **tool-related endpoints now default to the latest toolkit version** instead of the legacy pinned version (`00000000_00`).

### What Changed

In API v3 (`/api/v3/tools/*`), tool-related endpoints default the version parameter to `00000000_00` (the initial pinned version). This means callers must explicitly pass `version: "latest"` (or `toolkit_versions: "latest"` for `GET /tools`) to get the most recent tool definitions.

In API v3.1 (`/api/v3.1/tools/*`), the default is flipped: **tool-related endpoints default to the latest toolkit version**. If you're already passing `version: "latest"` in your requests, switching to v3.1 changes nothing for you. If you were relying on the `00000000_00` default, you'll now get the latest version unless you explicitly pin.

**Affected tool endpoints (those with a version parameter):**

| Endpoint | Version Parameter | v3 Default | v3.1 Default |
| - | - | - | - |
| `GET /tools` | `toolkit_versions` (query) | `00000000_00` | `latest` |
| `GET /tools/{tool_slug}` | `version` (query) | `00000000_00` | `latest` |
| `POST /tools/execute/{tool_slug}` | `version` (body) | `00000000_00` | `latest` |
| `POST /tools/execute/{tool_slug}/input` | `version` (body) | `00000000_00` | `latest` |
| `POST /tools/scopes/required` | `version` (body) | `00000000_00` | `latest` |

### Triggers Are Unchanged

Trigger endpoints already default the `version` parameter to `latest` in both v3 and v3.1, so there is **no behavior change** for triggers. If you're using triggers, switching to v3.1 requires no changes.

### All Other Endpoints Are Unchanged

Every non-tool endpoint (`/auth_configs`, `/connected_accounts`, `/triggers`, `/toolkits`, etc.) behaves identically between v3 and v3.1. They are served at both `/api/v3/` and `/api/v3.1/` paths with the same request and response contracts.

### Migration Guide

**If you're using the Composio SDK:** No action needed. The SDK will adopt v3.1 endpoints in an upcoming release.

**If you're calling the API directly:**

1. Replace `/api/v3/` with `/api/v3.1/` in your tool endpoint URLs
2. If you depend on a specific pinned version, pass it explicitly — `version=00000000_00` for most endpoints, or `toolkit_versions=00000000_00` for `GET /tools` (see table above)
3. If you were already passing `version: "latest"` (or `toolkit_versions: "latest"`), you can drop the parameter entirely on v3.1

**Before (v3):**

```bash theme={null}
curl "https://backend.composio.dev/api/v3/tools/GMAIL_SEND_EMAIL?version=latest" \
  -H "x-api-key: YOUR_KEY"
```

**After (v3.1):**

```bash theme={null}
curl "https://backend.composio.dev/api/v3.1/tools/GMAIL_SEND_EMAIL" \
  -H "x-api-key: YOUR_KEY"
```

**Apr 7, 2026**

Import bearer tokens for any OAuth toolkit and update credentials in place

## Bearer Token Connections & Credential Patching

Two features for teams managing their own authentication credentials.

## Bearer Token for OAuth Toolkits

All OAuth2 toolkits (Gmail, GitHub, Slack, Google Docs, and more) now support `BEARER_TOKEN` as an auth scheme. Import your own access tokens directly without setting up an OAuth app.

BEARER\_TOKEN is injected as an alternative scheme alongside OAuth2, so existing OAuth connections are unaffected.

### How to use

1. Create a custom auth config with `authScheme: "BEARER_TOKEN"` for the toolkit
2. Create a connected account with your access token
3. Pass the auth config or connection ID to `composio.create()` for use with Tool Router

> [!NOTE]
>
> Creating bearer token auth configs is currently available only via API and SDK — not yet supported in the dashboard UI.

See the [importing connections guide](https://composio-preview.mintlify.site/docs/authentication/importing-existing-connections.md) for full examples.

## Credential Patching

New `PATCH /api/v3/connected_accounts/{nanoid}` endpoint and SDK method — update credentials and alias on existing connections without recreating them.

```typescript theme={null}
import { Composio } from '@composio/core';
const composio = new Composio({ apiKey: 'your-api-key' });
await composio.connectedAccounts.update('ca_abc123', {
  connection: {
    state: {
      authScheme: 'BEARER_TOKEN',
      val: { token: 'rotated-access-token' },
    },
  },
});
```

* **Keep access tokens updated** — call PATCH whenever you refresh the token on your end (e.g., after an OAuth refresh flow)
* **Partial updates** — omitted fields are preserved, fields set to `null` are removed
* **Supported schemes** — BEARER\_TOKEN, API\_KEY, BASIC, BASIC\_WITH\_JWT, GOOGLE\_SERVICE\_ACCOUNT, SERVICE\_ACCOUNT

**Mar 28, 2026**

Consolidated overlapping tools, deprecated 52 high-usage duplicates, and renamed 1,445 enum slugs across 37 toolkits for agent-friendly naming.

## Tool consolidation and improved enum naming

We've completed a major effort to make Composio tools more agent-friendly. This release consolidates overlapping tools, deprecates redundant ones, and renames enum slugs to be cleaner and more intuitive for AI agents.

## What's changing?

### 1. Consolidated overlapping tools

Many toolkits had multiple tools that performed similar functions — sometimes originating from different API versions or slightly different wrappers around the same endpoint. We've unified these into single, well-defined tools. The consolidated tools retain full functionality while reducing noise for agents selecting tools.

**This affects 30+ toolkits.** Tools that didn't add meaningful value to agent workflows have been removed, and their functionality is covered by the remaining tools.

### 2. Deprecated high-usage duplicates

For tools that had significant active usage, we've soft-deprecated them rather than removing them outright. These tools still work but will return a deprecation notice pointing to the recommended replacement. We encourage migrating to the replacement tools listed below.

### 3. Renamed enum slugs for agent clarity

We've renamed 1,445 tool enum slugs across 37 toolkits to be shorter, more consistent, and easier for agents to understand. The old names often contained unnecessary filler words (`A`, `AN`, `THE`, `FOR_THE_AUTHENTICATED_USER`) or verbose patterns that made it harder for agents to match the right tool. The new names follow a consistent `APP_VERB_NOUN` pattern.

## No action required

**If you are using `latest` toolkit versions** or fetching tools dynamically, these changes will not break your integration. The SDK automatically resolves the correct tool names.

If you are pinning tool enums by name in your code, check the tables below for any renames or deprecations that affect you.

***

## Deprecated tools

These tools still work but now point to a recommended replacement. Migrate when convenient.

> [accordion] Gmail (1 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `GMAIL_LIST_MESSAGES` | `GMAIL_FETCH_EMAILS` |

> [accordion] Google Calendar (2 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `GOOGLECALENDAR_FREEBUSY_QUERY` | `GOOGLECALENDAR_FIND_FREE_SLOTS` |
> | `GOOGLECALENDAR_GET_CALENDAR_PROFILE` | `GOOGLECALENDAR_CALENDAR_LIST_GET` |

> [accordion] Google Docs (2 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `GOOGLEDOCS_UPDATE_DOCUMENT_BATCH` | `GOOGLEDOCS_UPDATE_EXISTING_DOCUMENT` |
> | `GOOGLEDOCS_CREATE_DOCUMENT_2` | `GOOGLEDOCS_CREATE_DOCUMENT` |

> [accordion] Google Drive (5 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `GOOGLEDRIVE_ADD_FILE_SHARING_PREFERENCE` | `GOOGLEDRIVE_CREATE_PERMISSION` |
> | `GOOGLEDRIVE_COPY_FILE` | `GOOGLEDRIVE_COPY_FILE_ADVANCED` |
> | `GOOGLEDRIVE_DOWNLOAD_FILE_2` | `GOOGLEDRIVE_DOWNLOAD_FILE_OPERATION` |
> | `GOOGLEDRIVE_GET_FILE_V2` | `GOOGLEDRIVE_GET_FILE_METADATA` |
> | `GOOGLEDRIVE_LIST_FILES` | `GOOGLEDRIVE_FIND_FILE` |

> [accordion] Google Sheets (2 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `GOOGLESHEETS_FIND_WORKSHEET_BY_TITLE` | `GOOGLESHEETS_GET_SPREADSHEET_INFO` |
> | `GOOGLESHEETS_GET_BATCH_VALUES` | `GOOGLESHEETS_BATCH_GET` |

> [accordion] Google Tasks (2 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `GOOGLETASKS_BULK_INSERT_TASKS` | `GOOGLETASKS_BATCH_EXECUTE` |
> | `GOOGLETASKS_UPDATE_TASK` | `GOOGLETASKS_PATCH_TASK` |

> [accordion] Outlook (3 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `OUTLOOK_CREATE_MASTER_CATEGORY` | `OUTLOOK_CREATE_USER_MASTER_CATEGORY` |
> | `OUTLOOK_DELETE_EVENT` | `OUTLOOK_DELETE_CALENDAR_EVENT` |
> | `OUTLOOK_OUTLOOK_LIST_CONTACTS` | `OUTLOOK_LIST_USER_CONTACTS` |

> [accordion] Slack (1 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `SLACK_FIND_USER_BY_EMAIL_ADDRESS` | `SLACK_FIND_USERS` |

> [accordion] HubSpot (0 deprecated, see consolidated)
>
> No high-usage tools deprecated. Overlapping tools were consolidated (see removed section).

> [accordion] Instagram (7 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `INSTAGRAM_CREATE_MEDIA_CONTAINER` | `INSTAGRAM_POST_IG_USER_MEDIA` |
> | `INSTAGRAM_CREATE_POST` | `INSTAGRAM_POST_IG_USER_MEDIA_PUBLISH` |
> | `INSTAGRAM_GET_POST_COMMENTS` | `INSTAGRAM_GET_IG_MEDIA_COMMENTS` |
> | `INSTAGRAM_GET_POST_INSIGHTS` | `INSTAGRAM_GET_IG_MEDIA_INSIGHTS` |
> | `INSTAGRAM_GET_POST_STATUS` | `INSTAGRAM_GET_IG_MEDIA` |
> | `INSTAGRAM_GET_USER_MEDIA` | `INSTAGRAM_GET_IG_USER_MEDIA` |
> | `INSTAGRAM_REPLY_TO_COMMENT` | `INSTAGRAM_POST_IG_COMMENT_REPLIES` |

> [accordion] Notion (1 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `NOTION_GET_ABOUT_ME` | `NOTION_GET_ABOUT_USER` |

> [accordion] GitHub (2 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `GITHUB_REPO_S_GET_CONTENT` | `GITHUB_GET_RAW_REPOSITORY_CONTENT` |
> | `GITHUB_LIST_NOTIFICATIONS_FOR_THE_AUTHENTICATED_USER` | `GITHUB_LIST_NOTIFICATIONS` |

> [accordion] Airtable (2 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `AIRTABLE_CREATE_RECORD` | `AIRTABLE_CREATE_RECORDS` |
> | `AIRTABLE_CREATE_MULTIPLE_RECORDS` | `AIRTABLE_CREATE_RECORDS` |

> [accordion] Attio (4 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `ATTIO_CREATE_ENTRY` | `ATTIO_ATTIO_POST_V2_LISTS_LIST_ENTRIES` |
> | `ATTIO_LIST_ENTRIES` | `ATTIO_ATTIO_POST_V2_LISTS_LIST_ENTRIES_QUERY` |
> | `ATTIO_LIST_LIST_ENTRIES` | `ATTIO_ATTIO_POST_V2_LISTS_LIST_ENTRIES_QUERY` |
> | `ATTIO_UPDATE_ENTRY` | `ATTIO_ATTIO_PATCH_V2_LISTS_LIST_ENTRIES_ENTRY_ID` |

> [accordion] Jira (2 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `JIRA_FIND_USERS` | `JIRA_FIND_USERS2` |
> | `JIRA_GET_ISSUE_WORKLOGS` | `JIRA_GET_WORKLOG` |

> [accordion] Linear (1 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `LINEAR_GET_ALL_LINEAR_TEAMS` | `LINEAR_LIST_LINEAR_TEAMS` |

> [accordion] Microsoft Teams (3 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `MICROSOFT_TEAMS_LIST_CHAT` | `MICROSOFT_TEAMS_CHATS_GET_ALL_CHATS` |
> | `MICROSOFT_TEAMS_CHATS_GET_ALL_MESSAGES` | `MICROSOFT_TEAMS_LIST_USER_CHAT_MESSAGES` |
> | `MICROSOFT_TEAMS_TEAMS_LIST_CHAT_MESSAGES` | `MICROSOFT_TEAMS_LIST_USER_CHAT_MESSAGES` |

> [accordion] Pipedrive (2 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `PIPEDRIVE_ADD_A_NOTE` | `PIPEDRIVE_PIPEDRIVE_ADD_NOTE` |
> | `PIPEDRIVE_GET_DETAILS_OF_A_PERSON` | `PIPEDRIVE_PIPEDRIVE_GET_PERSON` |

> [accordion] Reddit (1 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `REDDIT_GET_NEW` | `REDDIT_RETRIEVE_REDDIT_POST` |

> [accordion] Salesforce (3 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `SALESFORCE_COMPOSITE_GRAPH_ACTION` | `SALESFORCE_POST_COMPOSITE_GRAPH` |
> | `SALESFORCE_EXECUTE_SOQL_QUERY` | `SALESFORCE_RUN_SOQL_QUERY` |
> | `SALESFORCE_QUERY` | `SALESFORCE_RUN_SOQL_QUERY` |

> [accordion] Shopify (4 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `SHOPIFY_COUNT_ORDER` | `SHOPIFY_RETRIEVES_AN_ORDER_COUNT` |
> | `SHOPIFY_CREATE_PRODUCT` | `SHOPIFY_CREATES_A_NEW_PRODUCT` |
> | `SHOPIFY_CREATE_PRODUCT_IMAGE` | `SHOPIFY_CREATE_A_NEW_PRODUCT_IMAGE` |
> | `SHOPIFY_DELETE_CUSTOM_COLLECTION` | `SHOPIFY_DELETES_A_CUSTOM_COLLECTION` |

> [accordion] Stripe (2 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `STRIPE_DELETE_CUSTOMER` | `STRIPE_DELETE_CUSTOMERS_CUSTOMER` |
> | `STRIPE_GET_BALANCE_HISTORY` | `STRIPE_LIST_BALANCE_TRANSACTIONS` |

> [accordion] YouTube (1 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `YOUTUBE_LIST_COMMENT_THREADS` | `YOUTUBE_LIST_COMMENT_THREADS2` |

> [accordion] Gemini (1 deprecated)
>
> | Deprecated Tool | Use Instead |
> | - | - |
> | `GEMINI_GET_VIDEOS_OPERATION` | `GEMINI_WAIT_FOR_VIDEO` |
>
> ***

## Consolidated (removed) tools

These tools have been removed because their functionality is fully covered by other existing tools. If you were using any of these, switch to the canonical tool for that operation.

> [accordion] Google Drive (35 removed)
>
> `GOOGLEDRIVE_ADD_SHARED_DRIVE_MEMBER`, `GOOGLEDRIVE_COPY_FILE_V2`, `GOOGLEDRIVE_INSERT_COMMENT`, `GOOGLEDRIVE_DELETE_FILE`, `GOOGLEDRIVE_DELETE_PERMISSION_V2`, `GOOGLEDRIVE_DELETE_REPLY_V2`, `GOOGLEDRIVE_DELETE_TEAM_DRIVE_V2`, `GOOGLEDRIVE_GET_ABOUT_V2`, `GOOGLEDRIVE_GET_CHANGES_START_PAGE_TOKEN_V2`, `GOOGLEDRIVE_GET_PERMISSION_V2`, `GOOGLEDRIVE_GET_REVISION_V2`, `GOOGLEDRIVE_GET_TEAM_DRIVE_V2`, `GOOGLEDRIVE_INSERT_FILE`, `GOOGLEDRIVE_INSERT_PERMISSION`, `GOOGLEDRIVE_LIST_CHANGES_V2`, `GOOGLEDRIVE_LIST_CHILDREN_V2`, `GOOGLEDRIVE_LIST_DRIVE_COMMENTS`, `GOOGLEDRIVE_LIST_DRIVE_REPLIES`, `GOOGLEDRIVE_LIST_FILE_LABELS_V2`, `GOOGLEDRIVE_LIST_PARENTS_V2`, `GOOGLEDRIVE_LIST_PERMISSIONS_V2`, `GOOGLEDRIVE_LIST_REVISIONS_V2`, `GOOGLEDRIVE_LIST_TEAM_DRIVES_V2`, `GOOGLEDRIVE_PATCH_COMMENT`, `GOOGLEDRIVE_STOP_CHANNEL_V2`, `GOOGLEDRIVE_TOUCH_FILE_V2`, `GOOGLEDRIVE_TRASH_FILE_V2`, `GOOGLEDRIVE_UPDATE_COMMENT_V2`, `GOOGLEDRIVE_UPDATE_DRIVE_V2`, `GOOGLEDRIVE_UPDATE_PERMISSION_V2`, `GOOGLEDRIVE_UPDATE_REPLY_V2`, `GOOGLEDRIVE_UPDATE_TEAM_DRIVE_V2`, `GOOGLEDRIVE_UPLOAD_MEDIA_FILE`, `GOOGLEDRIVE_WATCH_CHANGES_V2`, `GOOGLEDRIVE_WATCH_FILE_V2`

> [accordion] Outlook (79 removed)
>
> `OUTLOOK_CANCEL_CALENDAR_EVENT`, `OUTLOOK_CANCEL_EVENT`, `OUTLOOK_CANCEL_CALENDAR_GROUP_CALENDAR_EVENT`, `OUTLOOK_COPY_MAIL_FOLDER`, `OUTLOOK_COPY_MESSAGE_FROM_MAIL_FOLDER`, `OUTLOOK_CREATE_CALENDAR_EVENT_IN_CALENDAR`, `OUTLOOK_CREATE_CALENDAR_GROUP_CALENDAR_EVENT_ATTACHMENT`, `OUTLOOK_CREATE_CONTACT_FOLDER_CHILD_FOLDER`, `OUTLOOK_CREATE_EVENT_ATTACHMENT`, `OUTLOOK_CREATE_FORWARD_DRAFT`, `OUTLOOK_CREATE_MAIL_FOLDER_MESSAGE_RULE`, `OUTLOOK_CREATE_ME_CHILD_FOLDER_MESSAGE`, `OUTLOOK_CREATE_ME_CONTACT_FOLDERS_CONTACTS`, `OUTLOOK_CREATE_ME_CONTACT_FOLDERS_CONTACTS_EXTENSIONS`, `OUTLOOK_CREATE_ME_CONTACT_IN_CHILD_FOLDER`, `OUTLOOK_CREATE_ME_CONTACTS`, `OUTLOOK_CREATE_ME_EVENT`, `OUTLOOK_CREATE_ME_FORWARD_DRAFT`, `OUTLOOK_CREATE_ME_INFERENCE_CLASSIFICATION_OVERRIDE`, `OUTLOOK_CREATE_ME_MESSAGE_REPLY_ALL_DRAFT`, `OUTLOOK_CREATE_ME_REPLY_ALL_DRAFT`, `OUTLOOK_CREATE_ME_REPLY_DRAFT`, `OUTLOOK_DELETE_CALENDAR_EVENT_ATTACHMENT`, `OUTLOOK_DELETE_CALENDAR_FROM_GROUP`, `OUTLOOK_DELETE_CALENDAR_GROUP_CALENDAR_EVENT`, `OUTLOOK_DELETE_CALENDAR_PERMISSION`, `OUTLOOK_DELETE_CONTACT_FOLDER_CHILD_FOLDER`, `OUTLOOK_DELETE_CONTACT_FROM_CHILD_FOLDER_PERMANENTLY`, `OUTLOOK_DELETE_ME_CALENDAR_PERMISSION`, `OUTLOOK_DELETE_ME_CONTACT_EXTENSION`, `OUTLOOK_DELETE_ME_CONTACT_FOLDER_CONTACT_EXTENSION`, `OUTLOOK_DELETE_ME_EVENT_EXTENSION`, `OUTLOOK_DELETE_ME_EVENTS_ATTACHMENTS`, `OUTLOOK_DELETE_ME_INFERENCE_CLASSIFICATION_OVERRIDE`, `OUTLOOK_DELETE_ME_MAIL_FOLDER_CHILD_FOLDER`, `OUTLOOK_DELETE_ME_MAIL_FOLDER_MESSAGE_RULE`, `OUTLOOK_DELETE_ME_MAIL_FOLDERS`, `OUTLOOK_DELETE_ME_MAIL_FOLDERS_CHILD_FOLDERS_MESSAGES_EXTENSIONS`, `OUTLOOK_DELETE_ME_MAIL_FOLDERS_MESSAGES_ATTACHMENTS`, `OUTLOOK_DELETE_PRIMARY_CALENDAR_PERMISSION`, `OUTLOOK_DISMISS_CALENDAR_EVENT_REMINDER`, `OUTLOOK_DISMISS_EVENT_REMINDER_FROM_GROUP`, `OUTLOOK_GET_CALENDAR_GROUP_SCHEDULE`, `OUTLOOK_GET_CALENDAR_PERMISSION`, `OUTLOOK_GET_CALENDAR_PERMISSION_FROM_CALENDAR`, `OUTLOOK_GET_CONTACT_FOLDERS`, `OUTLOOK_GET_MAIL_FOLDER_MESSAGE_RULE`, `OUTLOOK_GET_ME_CONTACT_FOLDERS_CHILD_FOLDER`, `OUTLOOK_GET_ME_CONTACTS`, `OUTLOOK_GET_ME_CONTACTS_EXTENSIONS`, `OUTLOOK_GET_ME_EVENT_ATTACHMENT`, `OUTLOOK_GET_ME_EVENT_CALENDAR`, `OUTLOOK_GET_ME_MAIL_FOLDERS_MESSAGES_EXTENSIONS`, `OUTLOOK_GET_ME_OUTLOOK`, `OUTLOOK_GET_MESSAGE_EXTENSION`, `OUTLOOK_GET_SUPPORTED_TIME_ZONES`, `OUTLOOK_LIST_CALENDAR_EVENT_ATTACHMENTS`, `OUTLOOK_LIST_CALENDAR_GROUP_CALENDAR_EVENTS`, `OUTLOOK_LIST_CALENDAR_GROUP_EVENT_ATTACHMENTS`, `OUTLOOK_LIST_CHILD_FOLDER_CONTACTS`, `OUTLOOK_LIST_CONTACTS`, `OUTLOOK_LIST_ME_CALENDAR_PERMISSIONS`, `OUTLOOK_MOVE_ME_MAIL_FOLDER`, `OUTLOOK_SNOOZE_CALENDAR_EVENT_REMINDER`, `OUTLOOK_SNOOZE_CALENDAR_GROUP_EVENT_REMINDER`, `OUTLOOK_UPDATE_CALENDAR`, `OUTLOOK_UPDATE_CALENDAR_GROUPS_CALENDARS`, `OUTLOOK_UPDATE_CALENDAR_GROUPS_CALENDARS_EVENTS`, `OUTLOOK_UPDATE_CONTACT_FOLDER`, `OUTLOOK_UPDATE_CONTACT_FOLDER_CHILD_FOLDER`, `OUTLOOK_UPDATE_ME_CALENDAR`, and others

> [accordion] Stripe (75+ removed)
>
> Removed duplicate API endpoint wrappers including: `STRIPE_CREATE_BILLING_CREDIT_GRANT`, `STRIPE_CREATE_CARD`, `STRIPE_CREATE_SETUP_INTENT`, `STRIPE_DELETE_COUPON`, `STRIPE_DELETE_CUSTOMER_DISCOUNT`, `STRIPE_DELETE_CUSTOMER_TAX_ID`, `STRIPE_DELETE_INVOICEITEM`, `STRIPE_DELETE_PLAN`, `STRIPE_DELETE_SUBSCRIPTION_ITEM`, `STRIPE_DELETE_TAX_ID`, `STRIPE_DELETE_TERMINAL_LOCATION`, `STRIPE_DOWNLOAD_QUOTE_PDF`, `STRIPE_FIND_APPS_SECRET`, `STRIPE_GET_BALANCE_HISTORY_2`, and many more `get_v1_*` and `post_v1_*` duplicates.

> [accordion] Shopify (56 removed)
>
> `SHOPIFY_ADD_PRODUCT_TO_COLLECTION`, `SHOPIFY_CANCEL_FULFILLMENT_ORDER`, `SHOPIFY_CANCEL_ORDER`, `SHOPIFY_CLOSE_ORDER`, `SHOPIFY_COUNT_LOCATION`, `SHOPIFY_COUNT_WEBHOOK`, `SHOPIFY_CREATE_A_METAFIELD_2`, `SHOPIFY_CREATE_A_NEW_WEBHOOK`, `SHOPIFY_CREATE_COUNTRY`, `SHOPIFY_CREATE_FULFILLMENT_ORDER`, `SHOPIFY_CREATES_A_FULFILLMENT_EVENT`, `SHOPIFY_CREATES_A_GIFT_CARD`, `SHOPIFY_CREATES_A_PRICE_RULE`, `SHOPIFY_CREATES_A_REDIRECT`, `SHOPIFY_CREATE_REFUND`, `SHOPIFY_DEL_FULFILLMENT_EVENT`, `SHOPIFY_DEL_METAFIELD`, `SHOPIFY_DEL_SCRIPTTAG`, `SHOPIFY_DEL_WEBHOOK`, `SHOPIFY_DELETE_AN_ARTICLE`, `SHOPIFY_DELETES_A_PRODUCT`, `SHOPIFY_DELETE_REDIRECT`, `SHOPIFY_DISABLE_GIFT_CARD`, `SHOPIFY_GET_CUSTOM_COLLECTION`, `SHOPIFY_GET_CUSTOMER`, `SHOPIFY_GET_GIFT_CARD`, `SHOPIFY_GET_GIFT_CARDS`, `SHOPIFY_GET_GIFT_CARDS_COUNT`, `SHOPIFY_SEARCH_CUSTOMERS`, `SHOPIFY_SEARCHES_FOR_GIFT_CARDS`, and others.

> [accordion] Pipedrive (44 removed)
>
> `PIPEDRIVE_ADD_A_COMMENT_TO_A_NOTE`, `PIPEDRIVE_ADD_A_FOLLOWER_TO_A_PERSON`, `PIPEDRIVE_ADD_A_FOLLOWER_TO_A_PRODUCT`, `PIPEDRIVE_ADD_A_FOLLOWER_TO_AN_ORGANIZATION`, `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL`, `PIPEDRIVE_DELETE_A_DEAL`, `PIPEDRIVE_DELETE_A_DEAL_FIELD`, `PIPEDRIVE_DELETE_A_FILE`, `PIPEDRIVE_DELETE_A_FILTER`, `PIPEDRIVE_GET_DETAILS_OF_A_DEAL`, `PIPEDRIVE_GET_ONE_DEAL_FIELD`, `PIPEDRIVE_PIPEDRIVE_ADD_DEAL_PARTICIPANT`, `PIPEDRIVE_PIPEDRIVE_DEALS_DELETE_DEAL`, `PIPEDRIVE_PIPEDRIVE_DEALS_DELETE_DEAL_V2`, `PIPEDRIVE_PIPEDRIVE_DELETE_WEBHOOK`, `PIPEDRIVE_PIPEDRIVE_GET_DEAL_BY_ID`, `PIPEDRIVE_PIPEDRIVE_GET_FILE`, `PIPEDRIVE_PIPEDRIVE_GET_FILTER`, `PIPEDRIVE_PIPEDRIVE_GET_LEAD`, `PIPEDRIVE_PIPEDRIVE_GET_NOTE`, `PIPEDRIVE_PIPEDRIVE_GET_PIPELINE`, `PIPEDRIVE_PIPEDRIVE_GET_PRODUCT`, `PIPEDRIVE_PIPEDRIVE_GET_STAGE`, and others.

> [accordion] Microsoft Teams (19 removed)
>
> `MICROSOFT_TEAMS_ARCHIVE_GROUP_TEAM`, `MICROSOFT_TEAMS_CLONE_GROUP_TEAM`, `MICROSOFT_TEAMS_DELETE_ONLINE_MEETING`, `MICROSOFT_TEAMS_GET_CHAT`, `MICROSOFT_TEAMS_GET_CHAT_LAST_MESSAGE_PREVIEW`, `MICROSOFT_TEAMS_GET_CHAT_MEMBER`, `MICROSOFT_TEAMS_GET_MY_PRESENCE`, `MICROSOFT_TEAMS_GET_PRESENCE`, `MICROSOFT_TEAMS_GET_TEAM_FROM_GROUP`, `MICROSOFT_TEAMS_GET_TEAMS_APP_DEFINITION`, `MICROSOFT_TEAMS_LIST_CHANNELS`, `MICROSOFT_TEAMS_LIST_CHAT_MEMBERS`, `MICROSOFT_TEAMS_LIST_MESSAGE_REPLIES`, `MICROSOFT_TEAMS_SET_SCHEDULE`, `MICROSOFT_TEAMS_UNARCHIVE_GROUP_TEAM`, `MICROSOFT_TEAMS_UNARCHIVE_TEAM_2`, and others.

> [accordion] Salesforce (17 removed)
>
> `SALESFORCE_FETCH_MODIFIED_OR_UNMODIFIED_SOBJECTS`, `SALESFORCE_GET_A_BATCH_OF_RECORDS`, `SALESFORCE_GET_CONSENT_ACTION`, `SALESFORCE_GET_ORG_LIMITS`, `SALESFORCE_GET_QUICK_ACTIONS`, `SALESFORCE_GET_SEARCH_LAYOUT`, `SALESFORCE_GET_S_OBJECTS`, `SALESFORCE_PARAMETERIZED_SEARCH_POST`, `SALESFORCE_POST_COMPOSITE_TREE_SOBJECTNAME`, `SALESFORCE_SEARCH_RESULT_LAYOUTS`, `SALESFORCE_S_OBJECT_COLLECTIONS_CREATE`, `SALESFORCE_S_OBJECT_USER_PASSWORD`, and others.

> [accordion] GitHub (8 removed)
>
> `GITHUB_LIST_CHECK_RUNS_FOR_A_GIT_REFERENCE`, `GITHUB_LIST_COMMIT_STATUSES_FOR_A_REFERENCE`, `GITHUB_LIST_SUBSCRIPTIONS_FOR_THE_AUTHENTICATED_USER`, `GITHUB_LIST_ASSIGNED_ISSUES`, `GITHUB_UPDATE_INFORMATION_ABOUT_A_GITHUB_PAGES_SITE`, `GITHUB_GET_GITHUB_GRAPHQL_META`, `GITHUB_GET_VIEWER_GRAPHQL_ID`, `GITHUB_LOOKUP_USER_BY_LOGIN`

> [accordion] HubSpot (7 removed)
>
> `HUBSPOT_DELETE_CONTACT_FOR_GDPR_COMPLIANCE`, `HUBSPOT_GDPR_DELETE`, `HUBSPOT_PERMANENTLY_DELETE_CONTACT_FOR_GDPR`, `HUBSPOT_PERMANENTLY_DELETE_CONTACT_GDPR_COMPLIANCE`, `HUBSPOT_PERMANENTLY_DELETE_GDPR_CONTACT_AND_CONTENT`, `HUBSPOT_GET_MARKETING_EMAILS`, `HUBSPOT_GET_WORKFLOW_EMAIL_CAMPAIGNS`

> [accordion] Canvas (13 removed)
>
> `CANVAS_GET_USERS_SELF_CONTENT_SHARES_RECEIVED`, `CANVAS_CREATE_USERS_SELF_CONTENT_SHARES`, `CANVAS_DELETE_USERS_SELF_CONTENT_SHARES`, `CANVAS_GET_A_SINGLE_GROUP`, `CANVAS_GET_COURSES_PREVIEW_HTML`, `CANVAS_GET_GROUPS_PREVIEW_HTML`, `CANVAS_GET_TERM`, `CANVAS_GET_USERS_SELF_CONTENT_SHARES`, `CANVAS_LIST_AVAILABLE_TABS_FOR_COURSE_2`, `CANVAS_LIST_USERS_IN_ACCOUNT`, `CANVAS_MARK_MODULE_ITEM_AS_DONE_NOT_DONE`, `CANVAS_RESOLVE_PATH`, `CANVAS_UPDATE_USERS_SELF_CONTENT_SHARES`

> [accordion] Other apps
>
> | App | Removed Tools |
> | - | - |
> | **Airtable** | `AIRTABLE_AIRTABLE_UPLOAD_ATTACHMENT_2` |
> | **Asana** | `ASANA_GET_PROJECT_MEMBERSHIPS` |
> | **Attio** | `ATTIO_ATTIO_POST_V2_OBJECTS_RECORDS_SEARCH`, `ATTIO_DELETE_ENTRY`, `ATTIO_ATTIO_GET_V2_WORKSPACE_MEMBERS`, `ATTIO_UPDATE_ATTRIBUTE` |
> | **Box** | `BOX_FIND_WEB_LINK_FOR_SHARED_LINK`, `BOX_GET_CLASSIFICATION_ON_FILE`, `BOX_GET_CLASSIFICATION_ON_FOLDER`, `BOX_GET_SHARED_LINK_FOR_WEB_LINK`, `BOX_REMOVE_CLASSIFICATION_FROM_FILE`, `BOX_REMOVE_CLASSIFICATION_FROM_FOLDER` |
> | **Firecrawl** | `FIRECRAWL_CRAWL` |
> | **Google Docs** | `GOOGLEDOCS_DELETE_TABLE`, `GOOGLEDOCS_LIST_SPREADSHEET_CHARTS_ACTION` |
> | **Jira** | `JIRA_EVALUATE_JIRA_EXPRESSION` |
> | **Linear** | `LINEAR_MANAGE_DRAFT` |
> | **Reddit** | `REDDIT_GET_R_SUBREDDIT_LINK_FLAIR_V2`, `REDDIT_REDDIT_GET_R_TOP` |
> | **SerpAPI** | `SERPAPI_FIND_GOOGLE_LENS_EXACT_MATCHES`, `SERPAPI_LOCATIONS_LIST` |
> | **Slack** | `SLACK_CLEAR_STATUS`, `SLACK_SET_STATUS`, `SLACK_SLACK_TEST_AUTH` |
>
> ***

## Renamed enum slugs

We've renamed 1,445 tool enum slugs across 37 toolkits to be more concise and agent-friendly. Old slugs contained verbose patterns like `DELETE_A_GIST`, `GET_A_CODESPACE_FOR_THE_AUTHENTICATED_USER`, or `ADD_MEMBERS_FOR_PROJECT`. New slugs follow a cleaner `APP_VERB_NOUN` convention: `DELETE_GIST`, `GET_CODESPACE`, `ADD_MEMBERS_TO_PROJECT`.

> [accordion] PostHog (179 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `POSTHOG_CANCEL_INSIGHTS_FOR_A_PROJECT` | `POSTHOG_CANCEL_PROJECT_INSIGHTS` |
> | `POSTHOG_CHECK_PROJECT_S_DEMO_DATA_GENERATION_STATUS` | `POSTHOG_CHECK_PROJECT_DEMO_DATA_GENERATION_STATUS` |
> | `POSTHOG_COHORT_DUPLICATION_TO_STATIC` | `POSTHOG_DUPLICATE_COHORT_TO_STATIC` |
> | `POSTHOG_CREATE_A_NOTEBOOK_IN_A_PROJECT` | `POSTHOG_CREATE_PROJECT_NOTEBOOK` |
> | `POSTHOG_CREATE_BATCH_EXPORTS_BACKFILLS` | `POSTHOG_CREATE_BATCH_EXPORT_BACKFILL` |
> | `POSTHOG_CREATE_BATCH_EXPORTS_RUN_TEST_STEP` | `POSTHOG_CREATE_BATCH_EXPORT_TEST_RUN` |
> | `POSTHOG_CREATE_DATASET_ITEMS` | `POSTHOG_CREATE_DATASET_ITEM` |
> | `POSTHOG_CREATE_DESKTOP_RECORDINGS` | `POSTHOG_CREATE_DESKTOP_RECORDING` |
> | `POSTHOG_CREATE_DOMAIN_WITH_SAML_FOR_ORGANIZATION` | `POSTHOG_CREATE_ORGANIZATION_SAML_DOMAIN` |
> | `POSTHOG_CREATE_ERROR_TRACKING_AUTOCAPTURE_CONTROLS` | `POSTHOG_CREATE_ERROR_TRACKING_AUTOCAPTURE_CONTROL` |
> | `POSTHOG_CREATE_ERROR_TRACKING_SYMBOL_SETS_BULK_START_UPLOAD` | `POSTHOG_START_ERROR_TRACKING_SYMBOL_SETS_BULK_UPLOAD` |
> | `POSTHOG_CREATE_ERROR_TRACKING_SYMBOL_SETS_START_UPLOAD` | `POSTHOG_START_ERROR_TRACKING_SYMBOL_SET_UPLOAD` |
> | `POSTHOG_CREATE_EVENT_DEFINITIONS` | `POSTHOG_CREATE_EVENT_DEFINITION` |
> | `POSTHOG_CREATE_EXPERIMENTS_RECALCULATE_TIMESERIES` | `POSTHOG_RECALCULATE_EXPERIMENT_TIMESERIES` |
> | `POSTHOG_CREATE_GROUPS_TYPES_METRICS` | `POSTHOG_CREATE_GROUP_TYPE_METRIC` |
> | `POSTHOG_CREATE_LLM_ANALYTICS_TEXT_REPR` | `POSTHOG_CREATE_LLM_ANALYTICS_TEXT_REPRESENTATION` |
> | `POSTHOG_CREATE_MAX_TOOLS_INSIGHT` | `POSTHOG_CREATE_AI_INSIGHT` |
> | `POSTHOG_CREATE_NEW_ORGANIZATION_WITH_CONFIGURABLE_ACCESS` | `POSTHOG_CREATE_ORGANIZATION` |
> | `POSTHOG_CREATE_NEW_PROJECT_EXPERIMENT` | `POSTHOG_CREATE_PROJECT_EXPERIMENT` |
> | `POSTHOG_CREATE_ORGANIZATION_INVITE_WITH_ROLE_AND_EMAIL` | `POSTHOG_CREATE_ORGANIZATION_INVITE` |
> | `POSTHOG_CREATE_ORGANIZATION_ROLE_WITH_FEATURE_FLAG_LEVELS` | `POSTHOG_CREATE_ORGANIZATION_ROLE` |
> | `POSTHOG_CREATE_ORG_PROXY_RECORD_WITH_DOMAIN_AND_STATUS` | `POSTHOG_CREATE_ORGANIZATION_PROXY_RECORD` |
> | `POSTHOG_CREATE_PERSONS_BULK_DELETE` | `POSTHOG_BULK_DELETE_PERSONS` |
> | `POSTHOG_CREATE_PERSON_PATH_WITH_FORMAT_OPTION` | `POSTHOG_CREATE_PERSON_PATH` |
> | `POSTHOG_CREATE_PROJECT_ACTION_WITH_FORMAT` | `POSTHOG_CREATE_PROJECT_ACTION` |
> | `POSTHOG_CREATE_PROJECT_COHORTS` | `POSTHOG_CREATE_PROJECT_COHORT` |
> | `POSTHOG_CREATE_PROJECT_SUBSCRIPTION_WITH_DELIVERY_OPTIONS` | `POSTHOG_CREATE_PROJECT_SUBSCRIPTION` |
> | `POSTHOG_CREATE_PROJECT_SURVEYS_WITH_QUESTIONS_AND_TARGETS` | `POSTHOG_CREATE_PROJECT_SURVEY` |
> | `POSTHOG_CREATE_PROJECT_TIMING_INSIGHTS` | `POSTHOG_MARK_INSIGHTS_AS_VIEWED` |
> | `POSTHOG_CREATE_RETRIEVE_RETENTION_INSIGHTS_FOR_PROJECT` | `POSTHOG_CREATE_PROJECT_RETENTION_INSIGHT` |
> | `POSTHOG_CREATE_SESSION_RECORDING_IN_PLAYLIST` | `POSTHOG_ADD_SESSION_RECORDING_TO_PLAYLIST` |
> | `POSTHOG_CREATE_SESSION_RECORDING_PLAYLISTS` | `POSTHOG_CREATE_SESSION_RECORDING_PLAYLIST` |
> | `POSTHOG_CREATE_STATIC_COHORT_FOR_FEATURE_FLAG` | `POSTHOG_CREATE_FEATURE_FLAG_COHORT` |
> | `POSTHOG_CREATE_SURVEYS_SUMMARY_HEADLINE` | `POSTHOG_CREATE_SURVEY_SUMMARY_HEADLINE` |
> | `POSTHOG_CREATE_WEB_EXPERIMENTS` | `POSTHOG_CREATE_WEB_EXPERIMENT` |
> | `POSTHOG_CRUD_OPERATIONS_FOR_PROJECT_ANNOTATIONS` | `POSTHOG_MANAGE_PROJECT_ANNOTATIONS` |
> | `POSTHOG_CUSTOM_PROJECT_FUNNEL_ANALYTICS_WITH_ADVANCED_OPTIONS` | `POSTHOG_PROJECT_FUNNEL_ADVANCED_ANALYTICS` |
> | `POSTHOG_DELETE_ERROR_TRACKING_AUTOCAPTURE_CONTROLS` | `POSTHOG_DELETE_ERROR_TRACKING_AUTOCAPTURE_CONTROL` |
> | `POSTHOG_DELETE_FEATURE_FLAGS` | `POSTHOG_BULK_DELETE_FEATURE_FLAGS` |
> | `POSTHOG_DELETE_GROUPS_TYPES_METRICS` | `POSTHOG_DELETE_GROUP_TYPE_METRIC` |
> | `POSTHOG_DELETE_INSIGHT_VARIABLES` | `POSTHOG_DELETE_INSIGHT_VARIABLE` |
> | `POSTHOG_DELETE_ORGANIZATION_BY_UUID` | `POSTHOG_DELETE_ORGANIZATION` |
> | `POSTHOG_DELETE_PERSON_AND_OPTIONALLY_ASSOCIATED_EVENTS` | `POSTHOG_DELETE_PERSON` |
> | `POSTHOG_DELETE_PRODUCT_TOURS` | `POSTHOG_DELETE_PRODUCT_TOUR` |
> | `POSTHOG_DELETE_SESSION_RECORDING_BY_UUID` | `POSTHOG_DELETE_SESSION_RECORDING` |
> | `POSTHOG_DELETE_SURVEY_BY_ID` | `POSTHOG_DELETE_SURVEY` |
> | `POSTHOG_FETCH_EXPORT_UNSUBSCRIBE_SETTINGS` | `POSTHOG_GET_EXPORT_UNSUBSCRIBE_SETTINGS` |
> | `POSTHOG_FETCH_ORGANIZATION_DETAILS_BY_UUID` | `POSTHOG_GET_ORGANIZATION` |
> | `POSTHOG_FETCH_ORGANIZATION_PIPELINE_APP_REPOSITORIES` | `POSTHOG_GET_ORGANIZATION_PIPELINE_APP_REPOSITORIES` |
> | `POSTHOG_FETCH_PIPELINE_DESTINATION_DETAILS` | `POSTHOG_GET_PIPELINE_DESTINATION_DETAILS` |
> | `POSTHOG_FETCH_PIPELINE_TRANSFORMATION_DETAILS` | `POSTHOG_GET_PIPELINE_TRANSFORMATION_DETAILS` |
> | `POSTHOG_FETCH_PROJECT_SURVEY_ACTIVITY_LOG` | `POSTHOG_GET_PROJECT_SURVEY_ACTIVITY_LOG` |
> | `POSTHOG_FETCH_SESSION_RECORDING_PLAYLIST_DETAILS` | `POSTHOG_GET_SESSION_RECORDING_PLAYLIST_DETAILS` |
> | `POSTHOG_GET_DATASET_DETAILS` | `POSTHOG_GET_DATASET` |
> | `POSTHOG_GET_EXPERIMENT_SAVED_METRIC2` | `POSTHOG_GET_EXPERIMENT_SAVED_METRIC` |
> | `POSTHOG_GET_FILE_SYSTEM2` | `POSTHOG_GET_FILE_SYSTEM` |
> | `POSTHOG_GET_INSIGHT_VARIABLES2` | `POSTHOG_GET_INSIGHT_VARIABLE` |
> | `POSTHOG_GET_LIVE_DEBUGGER_BREAKPOINT2` | `POSTHOG_GET_LIVE_DEBUGGER_BREAKPOINT` |
> | `POSTHOG_GET_PRODUCT_TOURS2` | `POSTHOG_GET_PRODUCT_TOUR` |
> | `POSTHOG_LIST_BATCH_EXPORT_RUNS_WITH_PAGINATION_AND_ORDERING` | `POSTHOG_LIST_BATCH_EXPORT_RUNS` |
> | `POSTHOG_LIST_NOTEBOOKS_WITH_FILTERS_AND_PAGINATION` | `POSTHOG_LIST_NOTEBOOKS` |
> | `POSTHOG_LIST_OF_PROJECT_S_SESSION_RECORDING_PLAYLISTS` | `POSTHOG_LIST_SESSION_RECORDING_PLAYLISTS` |
> | `POSTHOG_LIST_ORGANIZATION_DOMAINS_WITH_PAGINATION` | `POSTHOG_LIST_ORGANIZATION_DOMAINS` |
> | `POSTHOG_LIST_ORGANIZATION_INVITES_WITH_PAGINATION` | `POSTHOG_LIST_ORGANIZATION_INVITES` |
> | `POSTHOG_LIST_ORGANIZATION_MEMBERS_WITH_PAGINATION` | `POSTHOG_LIST_ORGANIZATION_MEMBERS` |
> | `POSTHOG_LIST_ORGANIZATION_PLUGINS_WITH_PAGINATION` | `POSTHOG_LIST_ORGANIZATION_PLUGINS` |
> | `POSTHOG_LIST_ORGANIZATION_ROLES_WITH_PAGINATION` | `POSTHOG_LIST_ORGANIZATION_ROLES` |
> | `POSTHOG_LIST_ORGANIZATION_S_BATCH_EXPORTS_WITH_PAGINATION` | `POSTHOG_LIST_ORGANIZATION_BATCH_EXPORTS` |
> | `POSTHOG_LIST_ORGANIZATION_S_PAGINATED_PROXY_RECORDS` | `POSTHOG_LIST_ORGANIZATION_PROXY_RECORDS` |
> | `POSTHOG_LIST_ORGANIZATION_S_PIPELINE_DESTINATIONS` | `POSTHOG_LIST_ORGANIZATION_PIPELINE_DESTINATIONS` |
> | `POSTHOG_LIST_ORGANIZATION_S_PIPELINE_FRONTEND_APPS` | `POSTHOG_LIST_ORGANIZATION_PIPELINE_FRONTEND_APPS` |
> | `POSTHOG_LIST_ORGANIZATION_S_PIPELINE_IMPORT_APPS` | `POSTHOG_LIST_ORGANIZATION_PIPELINE_IMPORT_APPS` |
> | `POSTHOG_LIST_ORGANIZATION_S_PIPELINE_TRANSFORMATIONS` | `POSTHOG_LIST_ORGANIZATION_PIPELINE_TRANSFORMATIONS` |
> | `POSTHOG_LIST_PAGINATED_SURVEYS_FOR_A_PROJECT` | `POSTHOG_LIST_PROJECT_SURVEYS` |
> | `POSTHOG_LIST_PIPELINE_DESTINATION_CONFIGS_WITH_PAGINATION` | `POSTHOG_LIST_PIPELINE_DESTINATION_CONFIGS` |
> | `POSTHOG_LIST_PROJECTS_IN_ORGANIZATION_WITH_PAGINATION` | `POSTHOG_LIST_ORGANIZATION_PROJECTS` |
> | `POSTHOG_LIST_PROJECT_ACTIONS_WITH_PAGINATION_AND_FILTERS` | `POSTHOG_LIST_PROJECT_ACTIONS` |
> | `POSTHOG_LIST_PROJECT_BATCH_EXPORTS_WITH_PAGINATION` | `POSTHOG_LIST_PROJECT_BATCH_EXPORTS` |
> | `POSTHOG_LIST_PROJECT_DASHBOARDS_WITH_PAGINATION` | `POSTHOG_LIST_PROJECT_DASHBOARDS` |
> | `POSTHOG_LIST_PROJECT_EXPERIMENTS_WITH_PAGINATION` | `POSTHOG_LIST_PROJECT_EXPERIMENTS` |
> | `POSTHOG_LIST_PROJECT_EXPORT_ITEMS_WITH_PAGINATION` | `POSTHOG_LIST_PROJECT_EXPORT_ITEMS` |
> | `POSTHOG_LIST_PROJECT_GROUP_TYPES_BY_ID` | `POSTHOG_LIST_PROJECT_GROUP_TYPES` |
> | `POSTHOG_LIST_PROJECT_SUBSCRIPTIONS_WITH_PAGINATION` | `POSTHOG_LIST_PROJECT_SUBSCRIPTIONS` |
> | `POSTHOG_LIST_ROLE_MEMBERSHIPS_PAGINATED` | `POSTHOG_LIST_ROLE_MEMBERSHIPS` |
> | `POSTHOG_LIST_SPECIFIC_TYPE_GROUPS_WITH_PAGINATION` | `POSTHOG_LIST_GROUPS_BY_TYPE` |
> | `POSTHOG_MODIFY_ORG_INFO_VIA_UUID` | `POSTHOG_UPDATE_ORGANIZATION_BY_UUID` |
> | `POSTHOG_PARTIALLY_UPDATE_PROJECT_PROPERTY_DEFINITION` | `POSTHOG_PATCH_PROJECT_PROPERTY_DEFINITION` |
> | `POSTHOG_PARTIAL_EXPERIMENT_UPDATE_IN_PROJECT` | `POSTHOG_PATCH_EXPERIMENT` |
> | `POSTHOG_PARTIAL_UPDATE_OF_A_PROJECT_INSIGHT` | `POSTHOG_PATCH_PROJECT_INSIGHT` |
> | `POSTHOG_PARTIAL_UPDATE_OF_A_PROJECT_S_DASHBOARD` | `POSTHOG_PATCH_PROJECT_DASHBOARD` |
> | `POSTHOG_PARTIAL_UPDATE_OF_A_PROJECT_S_FEATURE_FLAG` | `POSTHOG_PATCH_PROJECT_FEATURE_FLAG` |
> | `POSTHOG_PARTIAL_UPDATE_OF_PROJECT_NOTEBOOK` | `POSTHOG_PATCH_PROJECT_NOTEBOOK` |
> | `POSTHOG_PARTIAL_UPDATE_PROJECT_ANNOTATION` | `POSTHOG_PATCH_PROJECT_ANNOTATION` |
> | `POSTHOG_PERSON_PARTIAL_UPDATE_VIA_PROJECT_ID` | `POSTHOG_PATCH_PERSON` |
> | `POSTHOG_PREVENT_HARD_DELETE_NOTEBOOK_BY_FLAGGING` | `POSTHOG_MARK_NOTEBOOK_AS_DELETED` |
> | `POSTHOG_REMOVE_DOMAIN_BY_UUID_FROM_ORGANIZATION` | `POSTHOG_DELETE_ORGANIZATION_DOMAIN` |
> | `POSTHOG_REMOVE_EARLY_ACCESS_FEATURE_FROM_PROJECT` | `POSTHOG_DELETE_PROJECT_EARLY_ACCESS_FEATURE` |
> | `POSTHOG_REMOVE_EXPLICIT_PROJECT_MEMBER_BY_UUID` | `POSTHOG_DELETE_PROJECT_MEMBER` |
> | `POSTHOG_REMOVE_FEATURE_FLAG_ROLE_ACCESS_BY_ID` | `POSTHOG_DELETE_FEATURE_FLAG_ROLE_ACCESS` |
> | `POSTHOG_REMOVE_MEMBER_FROM_ORGANIZATION_BY_UUID` | `POSTHOG_DELETE_ORGANIZATION_MEMBER` |
> | `POSTHOG_REMOVE_ORGANIZATION_BATCH_EXPORT_BY_UUID` | `POSTHOG_DELETE_ORGANIZATION_BATCH_EXPORT` |
> | `POSTHOG_REMOVE_ORGANIZATION_PIPELINE_DESTINATION` | `POSTHOG_DELETE_ORGANIZATION_PIPELINE_DESTINATION` |
> | `POSTHOG_REMOVE_ORGANIZATION_PIPELINE_TRANSFORMATION` | `POSTHOG_DELETE_ORGANIZATION_PIPELINE_TRANSFORMATION` |
> | `POSTHOG_REMOVE_ORGANIZATION_PLUGIN_BY_ID` | `POSTHOG_DELETE_ORGANIZATION_PLUGIN` |
> | `POSTHOG_REMOVE_ORGANIZATION_PROXY_RECORD` | `POSTHOG_DELETE_ORGANIZATION_PROXY_RECORD` |
> | `POSTHOG_REMOVE_ORGANIZATION_ROLE_BY_ID` | `POSTHOG_DELETE_ORGANIZATION_ROLE` |
> | `POSTHOG_REMOVE_ORG_PIPELINE_IMPORT_APP_BY_ID` | `POSTHOG_DELETE_ORGANIZATION_PIPELINE_IMPORT_APP` |
> | `POSTHOG_REMOVE_PROJECT_DASHBOARD_COLLABORATOR` | `POSTHOG_DELETE_PROJECT_DASHBOARD_COLLABORATOR` |
> | `POSTHOG_REMOVE_PROJECT_EVENT_DEFINITION` | `POSTHOG_DELETE_PROJECT_EVENT_DEFINITION` |
> | `POSTHOG_REMOVE_PROJECT_EXPERIMENT_BY_ID` | `POSTHOG_DELETE_PROJECT_EXPERIMENT` |
> | `POSTHOG_REMOVE_PROJECT_PLUGIN_CONFIGURATION` | `POSTHOG_DELETE_PROJECT_PLUGIN_CONFIGURATION` |
> | `POSTHOG_REMOVE_PROPERTY_DEFINITION_BY_UUID` | `POSTHOG_DELETE_PROPERTY_DEFINITION` |
> | `POSTHOG_REMOVE_ROLE_MEMBERSHIP_BY_UUID` | `POSTHOG_DELETE_ROLE_MEMBERSHIP` |
> | `POSTHOG_REMOVE_SESSION_RECORDING_FROM_PLAYLIST` | `POSTHOG_DELETE_SESSION_RECORDING_FROM_PLAYLIST` |
> | `POSTHOG_REMOVE_SPECIFIC_PROJECT_BATCH_EXPORT` | `POSTHOG_DELETE_PROJECT_BATCH_EXPORT` |
> | `POSTHOG_REMOVE_SPECIFIC_PROJECT_QUERY` | `POSTHOG_DELETE_PROJECT_QUERY` |
> | `POSTHOG_RETRIEVE_AND_DELETE_PROJECT_PERSON_TRENDS` | `POSTHOG_GET_PROJECT_PERSON_TRENDS` |
> | `POSTHOG_RETRIEVE_APP_METRICS_BY_IDS` | `POSTHOG_GET_APP_METRICS` |
> | `POSTHOG_RETRIEVE_APP_METRICS_ERROR_DETAILS` | `POSTHOG_GET_APP_METRICS_ERROR_DETAILS` |
> | `POSTHOG_RETRIEVE_BATCH_EXPORT_DETAILS` | `POSTHOG_GET_BATCH_EXPORT_DETAILS` |
> | `POSTHOG_RETRIEVE_COHORT_ACTIVITY_DETAILS` | `POSTHOG_GET_COHORT_ACTIVITY_DETAILS` |
> | `POSTHOG_RETRIEVE_COHORT_PERSON_DETAILS` | `POSTHOG_GET_COHORT_PERSON_DETAILS` |
> | `POSTHOG_RETRIEVE_DASHBOARD_TEMPLATE_DETAILS_BY_UUID` | `POSTHOG_GET_DASHBOARD_TEMPLATE_DETAILS` |
> | `POSTHOG_RETRIEVE_EVENT_DEFINITIONS_BY_PROJECT_ID` | `POSTHOG_GET_EVENT_DEFINITIONS` |
> | `POSTHOG_RETRIEVE_EVENT_DEFINITION_BY_UUID` | `POSTHOG_GET_EVENT_DEFINITION` |
> | `POSTHOG_RETRIEVE_EXPERIMENTS_REQUIRING_FLAG_IMPLEMENTATION` | `POSTHOG_GET_EXPERIMENTS_REQUIRING_FLAG_IMPLEMENTATION` |
> | `POSTHOG_RETRIEVE_EXPERIMENT_DETAILS_BY_IDS` | `POSTHOG_GET_EXPERIMENT_DETAILS` |
> | `POSTHOG_RETRIEVE_EXPORT_UNSUBSCRIBE_CONFIGS` | `POSTHOG_GET_EXPORT_UNSUBSCRIBE_CONFIGS` |
> | `POSTHOG_RETRIEVE_FEATURE_FLAGS_ACTIVITY_LOG` | `POSTHOG_GET_FEATURE_FLAGS_ACTIVITY_LOG` |
> | `POSTHOG_RETRIEVE_FEATURE_FLAGS_EVALUATION_REASONS` | `POSTHOG_GET_FEATURE_FLAGS_EVALUATION_REASONS` |
> | `POSTHOG_RETRIEVE_FEATURE_FLAG_ACTIVITY_DETAILS` | `POSTHOG_GET_FEATURE_FLAG_ACTIVITY_DETAILS` |
> | `POSTHOG_RETRIEVE_FEATURE_FLAG_DETAILS` | `POSTHOG_GET_FEATURE_FLAG_DETAILS` |
> | `POSTHOG_RETRIEVE_FEATURE_FLAG_ROLE_ACCESS_DETAILS` | `POSTHOG_GET_FEATURE_FLAG_ROLE_ACCESS_DETAILS` |
> | `POSTHOG_RETRIEVE_FILTERED_PROJECT_PROPERTY_DEFINITIONS` | `POSTHOG_GET_FILTERED_PROJECT_PROPERTY_DEFINITIONS` |
> | `POSTHOG_RETRIEVE_FUNNEL_INSIGHTS_IN_PROJECT` | `POSTHOG_GET_FUNNEL_INSIGHTS_IN_PROJECT` |
> | `POSTHOG_RETRIEVE_GROUP_PROPERTY_DEFINITIONS_BY_PROJECT_ID` | `POSTHOG_GET_GROUP_PROPERTY_DEFINITIONS` |
> | `POSTHOG_RETRIEVE_GROUP_PROPERTY_VALUES_BY_INDEX_AND_KEY` | `POSTHOG_GET_GROUP_PROPERTY_VALUES` |
> | `POSTHOG_RETRIEVE_HEDGEHOG_CONFIGURATION_BY_UUID` | `POSTHOG_GET_HEDGEHOG_CONFIGURATION` |
> | `POSTHOG_RETRIEVE_HISTORICAL_APP_METRICS_EXPORT` | `POSTHOG_GET_HISTORICAL_APP_METRICS_EXPORT` |
> | `POSTHOG_RETRIEVE_IMPORTANT_PROJECT_ACTIVITY_LOG` | `POSTHOG_GET_IMPORTANT_PROJECT_ACTIVITY_LOG` |
> | `POSTHOG_RETRIEVE_INSIGHT_SHARING_CONFIGURATIONS` | `POSTHOG_GET_INSIGHT_SHARING_CONFIGURATIONS` |
> | `POSTHOG_RETRIEVE_ORGANIZATION_S_PIPELINE_REPOSITORY_DETAILS` | `POSTHOG_RETRIEVE_ORGANIZATION_PIPELINE_REPOSITORY_DETAILS` |
> | `POSTHOG_RETRIEVE_ORGANIZATION_S_UNUSED_PIPELINE_APPS` | `POSTHOG_RETRIEVE_ORGANIZATION_UNUSED_PIPELINE_APPS` |
> | `POSTHOG_RETRIEVE_ORG_PIPELINE_TRANSFORMATION_ACTIVITY` | `POSTHOG_RETRIEVE_ORGANIZATION_PIPELINE_TRANSFORMATION_ACTIVI` |
> | `POSTHOG_RETRIEVE_PERSON_S_ACTIVITY_AND_DELETE_OPTIONS` | `POSTHOG_RETRIEVE_PERSON_ACTIVITY_AND_DELETE_OPTIONS` |
> | `POSTHOG_UPDATE_BATCH_EXPORTS2` | `POSTHOG_UPDATE_ORGANIZATION_BATCH_EXPORT` |
> | `POSTHOG_UPDATE_DATASETS` | `POSTHOG_UPDATE_DATASET` |
> | `POSTHOG_UPDATE_ERROR_TRACKING_AUTOCAPTURE_CONTROLS` | `POSTHOG_UPDATE_ERROR_TRACKING_AUTOCAPTURE_CONTROL` |
> | `POSTHOG_UPDATE_EVENT_DEFINITION_BY_UUID` | `POSTHOG_UPDATE_EVENT_DEFINITION` |
> | `POSTHOG_UPDATE_EXPERIMENT_DETAILS` | `POSTHOG_UPDATE_EXPERIMENT` |
> | `POSTHOG_UPDATE_EXPERIMENT_HOLDOUT_FULL` | `POSTHOG_UPDATE_EXPERIMENT_HOLDOUT_COMPLETE` |
> | `POSTHOG_UPDATE_EXPERIMENT_SAVED_METRICS` | `POSTHOG_UPDATE_EXPERIMENT_SAVED_METRIC` |
> | `POSTHOG_UPDATE_EXTERNAL_DATA_SOURCES` | `POSTHOG_UPDATE_EXTERNAL_DATA_SOURCE` |
> | `POSTHOG_UPDATE_FEATURE_FLAG_CONFIGURATION` | `POSTHOG_UPDATE_FEATURE_FLAG` |
> | `POSTHOG_UPDATE_GROUPS_TYPES_METRICS` | `POSTHOG_UPDATE_GROUPS_TYPES_METRIC` |
> | `POSTHOG_UPDATE_ORGANIZATION_DETAILS_BY_UUID` | `POSTHOG_UPDATE_ORGANIZATION` |
> | `POSTHOG_UPDATE_ORGANIZATION_DOMAIN_INFO_AND_SAML_CONFIG` | `POSTHOG_UPDATE_ORGANIZATION_DOMAIN` |
> | `POSTHOG_UPDATE_ORGANIZATION_DOMAIN_PROPERTIES` | `POSTHOG_PATCH_ORGANIZATION_DOMAIN` |
> | `POSTHOG_UPDATE_ORGANIZATION_MEMBER_BY_UUIDS` | `POSTHOG_UPDATE_ORGANIZATION_MEMBER` |
> | `POSTHOG_UPDATE_ORGANIZATION_MEMBER_DETAILS` | `POSTHOG_UPDATE_ORGANIZATION_MEMBER_COMPLETE` |
> | `POSTHOG_UPDATE_ORGANIZATION_S_PROXY_RECORD_DOMAIN` | `POSTHOG_UPDATE_ORGANIZATION_PROXY_RECORD` |
> | `POSTHOG_UPDATE_PARTIAL_PROJECT_COHORT_DETAILS` | `POSTHOG_PATCH_PROJECT_COHORT` |
> | `POSTHOG_UPDATE_PARTIAL_ROLE_DETAILS_IN_ORGANIZATION` | `POSTHOG_PATCH_ORGANIZATION_ROLE` |
> | `POSTHOG_UPDATE_PARTIAL_SUBSCRIPTION_DETAILS` | `POSTHOG_PATCH_PROJECT_SUBSCRIPTION` |
> | `POSTHOG_UPDATE_PARTIAL_SURVEY_DETAILS` | `POSTHOG_PATCH_PROJECT_SURVEY` |
> | `POSTHOG_UPDATE_PERSON_PROPERTY_ENDPOINT` | `POSTHOG_UPDATE_PERSON_PROPERTY` |
> | `POSTHOG_UPDATE_PROJECT_ACTION_BY_ID` | `POSTHOG_UPDATE_PROJECT_ACTION` |
> | `POSTHOG_UPDATE_PROJECT_ACTION_WITH_PARTIAL_DATA` | `POSTHOG_PATCH_PROJECT_ACTION` |
> | `POSTHOG_UPDATE_PROJECT_COHORT_DETAILS` | `POSTHOG_UPDATE_PROJECT_COHORT` |
> | `POSTHOG_UPDATE_PROJECT_DASHBOARD_DETAILS` | `POSTHOG_UPDATE_PROJECT_DASHBOARD` |
> | `POSTHOG_UPDATE_PROJECT_GROUP_TYPE_METADATA` | `POSTHOG_UPDATE_PROJECT_GROUP_TYPE` |
> | `POSTHOG_UPDATE_PROJECT_INSIGHT_DETAILS` | `POSTHOG_UPDATE_PROJECT_INSIGHT` |
> | `POSTHOG_UPDATE_PROJECT_MEMBER_ROLE_BY_UUID` | `POSTHOG_PATCH_PROJECT_MEMBER` |
> | `POSTHOG_UPDATE_PROJECT_MEMBER_S_ROLE_BY_UUID` | `POSTHOG_UPDATE_PROJECT_MEMBER` |
> | `POSTHOG_UPDATE_PROJECT_NOTEBOOK_DETAILS` | `POSTHOG_UPDATE_PROJECT_NOTEBOOK` |
> | `POSTHOG_UPDATE_PROJECT_SUBSCRIPTION_DETAILS` | `POSTHOG_UPDATE_PROJECT_SUBSCRIPTION` |
> | `POSTHOG_UPDATE_PROJECT_SURVEY_DETAILS` | `POSTHOG_UPDATE_PROJECT_SURVEY` |
> | `POSTHOG_UPDATE_ROLE_DETAILS_IN_ORGANIZATION` | `POSTHOG_UPDATE_ORGANIZATION_ROLE` |
> | `POSTHOG_UPDATE_SESSION_RECORDING_PLAYLIST_PARTIALLY` | `POSTHOG_PATCH_SESSION_RECORDING_PLAYLIST` |

> [accordion] Stripe (161 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `STRIPE_CREATE_BILLING_METER_EVENT_V2` | `STRIPE_CREATE_BILLING_METER_EVENT` |
> | `STRIPE_DELETE_COUPONS_COUPON` | `STRIPE_DELETE_COUPON` |
> | `STRIPE_DELETE_CUSTOMERS_CUSTOMER_BANK_ACCOUNTS_ID` | `STRIPE_DELETE_CUSTOMER_BANK_ACCOUNT` |
> | `STRIPE_DELETE_CUSTOMERS_CUSTOMER_DISCOUNT` | `STRIPE_DELETE_CUSTOMER_DISCOUNT` |
> | `STRIPE_DELETE_CUSTOMERS_TAX_ID` | `STRIPE_DELETE_CUSTOMER_TAX_ID` |
> | `STRIPE_DELETE_CUSTOMER_SUB_EXPOSED_ID` | `STRIPE_DELETE_CUSTOMER_SUBSCRIPTION` |
> | `STRIPE_DELETE_CUSTOMER_SUB_EXPOSED_ID_DISCOUNT` | `STRIPE_DELETE_CUSTOMER_SUBSCRIPTION_DISCOUNT` |
> | `STRIPE_DELETE_EPHEMERAL_KEYS_KEY` | `STRIPE_DELETE_EPHEMERAL_KEY` |
> | `STRIPE_DELETE_INVOICEITEMS_INVOICEITEM` | `STRIPE_DELETE_INVOICEITEM` |
> | `STRIPE_DELETE_INVOICES_INVOICE` | `STRIPE_DELETE_INVOICE` |
> | `STRIPE_DELETE_PLANS_PLAN` | `STRIPE_DELETE_PLAN` |
> | `STRIPE_DELETE_PRODUCTS_PRODUCT_FEATURES_ID` | `STRIPE_DELETE_PRODUCT_FEATURE` |
> | `STRIPE_DELETE_SUBSCRIPTION_ITEMS_ITEM` | `STRIPE_DELETE_SUBSCRIPTION_ITEM` |
> | `STRIPE_DELETE_TAX_IDS_ID` | `STRIPE_DELETE_TAX_ID` |
> | `STRIPE_DELETE_TERMINAL_CONFIGURATIONS_CONFIGURATION` | `STRIPE_DELETE_TERMINAL_CONFIGURATION` |
> | `STRIPE_DELETE_TERMINAL_LOCATIONS_LOCATION` | `STRIPE_DELETE_TERMINAL_LOCATION` |
> | `STRIPE_DELETE_TERMINAL_READERS_READER` | `STRIPE_DELETE_TERMINAL_READER` |
> | `STRIPE_DELETE_TEST_HELPERS_TEST_CLOCKS_TEST_CLOCK` | `STRIPE_DELETE_TEST_CLOCK` |
> | `STRIPE_GET_ACCOUNTS_ACCOUNT_CAPABILITIES` | `STRIPE_GET_ACCOUNT_CAPABILITIES` |
> | `STRIPE_GET_ACCOUNTS_ACCOUNT_PERSONS` | `STRIPE_GET_ACCOUNT_PERSONS` |
> | `STRIPE_GET_ACCOUNTS_ACCOUNT_PERSONS_PERSON` | `STRIPE_GET_ACCOUNT_PERSON` |
> | `STRIPE_GET_APPLE_PAY_DOMAINS` | `STRIPE_LIST_APPLE_PAY_DOMAINS` |
> | `STRIPE_GET_APPS_SECRETS` | `STRIPE_LIST_APPS_SECRETS` |
> | `STRIPE_GET_APPS_SECRETS_FIND` | `STRIPE_FIND_APPS_SECRET` |
> | `STRIPE_GET_BILLING_ALERTS` | `STRIPE_LIST_BILLING_ALERTS` |
> | `STRIPE_GET_BILLING_ALERTS_ID` | `STRIPE_GET_BILLING_ALERT` |
> | `STRIPE_GET_CHARGES_SEARCH` | `STRIPE_SEARCH_CHARGES` |
> | `STRIPE_GET_CHECKOUT_SESSIONS` | `STRIPE_LIST_CHECKOUT_SESSIONS` |
> | `STRIPE_GET_CHECKOUT_SESSIONS_SESSION` | `STRIPE_RETRIEVE_CHECKOUT_SESSION` |
> | `STRIPE_GET_CLIMATE_ORDERS` | `STRIPE_LIST_CLIMATE_ORDERS` |
> | `STRIPE_GET_CLIMATE_PRODUCTS` | `STRIPE_LIST_CLIMATE_PRODUCTS` |
> | `STRIPE_GET_CLIMATE_SUPPLIERS` | `STRIPE_LIST_CLIMATE_SUPPLIERS` |
> | `STRIPE_GET_COUNTRY_SPECS` | `STRIPE_LIST_COUNTRY_SPECS` |
> | `STRIPE_GET_DISPUTES` | `STRIPE_LIST_DISPUTES` |
> | `STRIPE_GET_ENTITLEMENTS_FEATURES` | `STRIPE_LIST_ENTITLEMENTS_FEATURES` |
> | `STRIPE_GET_FILES` | `STRIPE_LIST_FILES` |
> | `STRIPE_GET_FINANCIAL_CONNECTIONS_ACCOUNTS` | `STRIPE_LIST_FINANCIAL_CONNECTIONS_ACCOUNTS` |
> | `STRIPE_GET_FORWARDING_REQUESTS` | `STRIPE_LIST_FORWARDING_REQUESTS` |
> | `STRIPE_GET_INVOICEITEMS` | `STRIPE_LIST_INVOICEITEMS` |
> | `STRIPE_GET_INVOICE_RENDERING_TEMPLATES` | `STRIPE_LIST_INVOICE_RENDERING_TEMPLATES` |
> | `STRIPE_GET_PAYMENT_ATTEMPT_RECORDS` | `STRIPE_LIST_PAYMENT_ATTEMPT_RECORDS` |
> | `STRIPE_GET_PAYOUTS` | `STRIPE_LIST_PAYOUTS` |
> | `STRIPE_GET_PRICES_SEARCH` | `STRIPE_SEARCH_PRICES` |
> | `STRIPE_GET_PRODUCTS_PRODUCT_FEATURES` | `STRIPE_LIST_PRODUCTS_PRODUCT_FEATURES` |
> | `STRIPE_GET_QUOTES_QUOTE_PDF` | `STRIPE_DOWNLOAD_QUOTE_PDF` |
> | `STRIPE_GET_RADAR_EARLY_FRAUD_WARNINGS` | `STRIPE_LIST_RADAR_EARLY_FRAUD_WARNINGS` |
> | `STRIPE_GET_REPORTING_REPORT_RUNS` | `STRIPE_LIST_REPORTING_REPORT_RUNS` |
> | `STRIPE_GET_SUBSCRIPTIONS_SEARCH` | `STRIPE_SEARCH_SUBSCRIPTIONS` |
> | `STRIPE_GET_TAX_ASSOCIATIONS_FIND` | `STRIPE_FIND_TAX_ASSOCIATION` |
> | `STRIPE_GET_TAX_CODES_ID` | `STRIPE_GET_TAX_CODE` |
> | `STRIPE_GET_TAX_IDS_ID` | `STRIPE_GET_TAX_ID` |
> | `STRIPE_GET_TAX_REGISTRATIONS` | `STRIPE_LIST_TAX_REGISTRATIONS` |
> | `STRIPE_GET_TAX_REGISTRATIONS_ID` | `STRIPE_GET_TAX_REGISTRATION` |
> | `STRIPE_GET_TAX_TRANSACTIONS_TRANSACTION` | `STRIPE_GET_TAX_TRANSACTION` |
> | `STRIPE_GET_TERMINAL_CONFIGURATIONS` | `STRIPE_LIST_TERMINAL_CONFIGURATIONS` |
> | `STRIPE_GET_TERMINAL_CONFIGURATIONS_CONFIGURATION` | `STRIPE_GET_TERMINAL_CONFIGURATION` |
> | `STRIPE_GET_TERMINAL_LOCATIONS` | `STRIPE_LIST_TERMINAL_LOCATIONS` |
> | `STRIPE_GET_TERMINAL_LOCATIONS_LOCATION` | `STRIPE_GET_TERMINAL_LOCATION` |
> | `STRIPE_GET_TERMINAL_READERS` | `STRIPE_LIST_TERMINAL_READERS` |
> | `STRIPE_GET_TERMINAL_READERS_READER` | `STRIPE_GET_TERMINAL_READER` |
> | `STRIPE_GET_TEST_HELPERS_TEST_CLOCKS_TEST_CLOCK` | `STRIPE_GET_TEST_CLOCK` |
> | `STRIPE_GET_TOKENS_TOKEN` | `STRIPE_GET_TOKEN` |
> | `STRIPE_GET_TOPUPS` | `STRIPE_LIST_TOPUPS` |
> | `STRIPE_GET_TRANSFERS` | `STRIPE_LIST_TRANSFERS` |
> | `STRIPE_GET_V1_ACCOUNTS_CAPABILITIES_CAPABILITIES` | `STRIPE_GET_ACCOUNT_CAPABILITY` |
> | `STRIPE_GET_V1_BALANCE_SETTINGS_OVERVIEW` | `STRIPE_GET_BALANCE_SETTINGS` |
> | `STRIPE_GET_V1_BALANCE_TRANSACTIONS_THE_BALANCE_TRANSACTION` | `STRIPE_GET_BALANCE_TRANSACTION` |
> | `STRIPE_GET_V1_BILLING_CREDIT_BALANCE_TXNS_OVERVIEW_BILLING` | `STRIPE_LIST_BILLING_CREDIT_BALANCE_TRANSACTIONS` |
> | `STRIPE_GET_V1_CREDIT_NOTES_PREVIEW_CREDIT_NOTE` | `STRIPE_GET_CREDIT_NOTES_PREVIEW` |
> | `STRIPE_GET_V1_ENTITLEMENTS_ACTIVE_ENTITLEMENTS_ACTIVE` | `STRIPE_GET_ACTIVE_ENTITLEMENT` |
> | `STRIPE_GET_V1_FX_QUOTES_FX_QUOTES` | `STRIPE_GET_FX_QUOTE` |
> | `STRIPE_GET_V1_FX_QUOTES_FX_QUOTES2` | `STRIPE_LIST_FX_QUOTES` |
> | `STRIPE_GET_V1_PAYMENT_METHODS_PAYMENT_METHOD` | `STRIPE_GET_PAYMENT_METHOD` |
> | `STRIPE_GET_V1_PAYMENT_METHOD_CONFIGS_LIST_PAYMENT_METHOD` | `STRIPE_GET_PAYMENT_METHOD_CONFIGURATION` |
> | `STRIPE_GET_V1_PLANS_OVERVIEW` | `STRIPE_GET_PLAN` |
> | `STRIPE_GET_V1_RADAR_VALUE_LISTS_OVERVIEW` | `STRIPE_GET_RADAR_VALUE_LIST` |
> | `STRIPE_GET_V1_TAX_CALCULATIONS_OVERVIEW` | `STRIPE_GET_TAX_CALCULATION` |
> | `STRIPE_GET_V2_CORE_EVENTS_RETRIEVE_AN_EVENT_CORE_EVENTS` | `STRIPE_GET_V2_CORE_EVENTS_RETRIEVE_AN_EVENT` |
> | `STRIPE_LIST_ACTIVE_ENTITLEMENTS` | `STRIPE_GET_ENTITLEMENTS_ACTIVE_ENTITLEMENTS` |
> | `STRIPE_LIST_BANK_ACCOUNTS` | `STRIPE_GET_CUSTOMERS_CUSTOMER_BANK_ACCOUNTS` |
> | `STRIPE_LIST_CASH_BALANCE_TRANSACTIONS` | `STRIPE_GET_CUSTOMERS_CUSTOMER_CASH_BALANCE_TRANSACTIONS` |
> | `STRIPE_LIST_CUSTOMER_PAYMENT_METHODS` | `STRIPE_GET_CUSTOMERS_CUSTOMER_PAYMENT_METHODS` |
> | `STRIPE_POST_APPLE_PAY_DOMAINS` | `STRIPE_CREATE_APPLE_PAY_DOMAIN` |
> | `STRIPE_POST_APPS_SECRETS` | `STRIPE_CREATE_APPS_SECRET` |
> | `STRIPE_POST_BILLING_ALERTS` | `STRIPE_CREATE_BILLING_ALERT` |
> | `STRIPE_POST_BILLING_ALERTS_ID_ACTIVATE` | `STRIPE_ACTIVATE_BILLING_ALERT` |
> | `STRIPE_POST_BILLING_ALERTS_ID_ARCHIVE` | `STRIPE_ARCHIVE_BILLING_ALERT` |
> | `STRIPE_POST_BILLING_ALERTS_ID_DEACTIVATE` | `STRIPE_DEACTIVATE_BILLING_ALERT` |
> | `STRIPE_POST_BILLING_CREDIT_GRANTS` | `STRIPE_CREATE_BILLING_CREDIT_GRANT` |
> | `STRIPE_POST_BILLING_CREDIT_GRANTS_EXPIRE_CREDIT_GRANT` | `STRIPE_EXPIRE_BILLING_CREDIT_GRANT` |
> | `STRIPE_POST_BILLING_METERS` | `STRIPE_CREATE_BILLING_METER` |
> | `STRIPE_POST_BILLING_METERS_ID` | `STRIPE_UPDATE_BILLING_METER` |
> | `STRIPE_POST_BILLING_METERS_ID_DEACTIVATE` | `STRIPE_DEACTIVATE_BILLING_METER` |
> | `STRIPE_POST_BILLING_METERS_ID_REACTIVATE` | `STRIPE_REACTIVATE_BILLING_METER` |
> | `STRIPE_POST_BILLING_METER_EVENT_ADJUSTMENTS` | `STRIPE_CREATE_BILLING_METER_EVENT_ADJUSTMENT` |
> | `STRIPE_POST_BILLING_PORTAL_CONFIGURATIONS` | `STRIPE_CREATE_BILLING_PORTAL_CONFIGURATION` |
> | `STRIPE_POST_BILLING_PORTAL_CONFIGURATIONS_CONFIGURATION` | `STRIPE_UPDATE_BILLING_PORTAL_CONFIGURATION` |
> | `STRIPE_POST_CHARGES` | `STRIPE_CREATE_CHARGE` |
> | `STRIPE_POST_CHARGES_CHARGE_DISPUTE` | `STRIPE_UPDATE_CHARGE_DISPUTE` |
> | `STRIPE_POST_CHARGES_CHARGE_REFUNDS` | `STRIPE_CREATE_CHARGE_REFUND` |
> | `STRIPE_POST_CHARGES_CHARGE_REFUNDS_REFUND` | `STRIPE_UPDATE_CHARGE_REFUND` |
> | `STRIPE_POST_CHECKOUT_SESSIONS_EXPIRE_RETRIEVE_A_CHECKOUT` | `STRIPE_EXPIRE_CHECKOUT_SESSION` |
> | `STRIPE_POST_CHECKOUT_SESSIONS_SESSION` | `STRIPE_UPDATE_CHECKOUT_SESSION` |
> | `STRIPE_POST_CREDIT_NOTES_ID_VOID` | `STRIPE_VOID_CREDIT_NOTE` |
> | `STRIPE_POST_CUSTOMERS_CUSTOMER_BANK_ACCOUNTS` | `STRIPE_CREATE_CUSTOMER_BANK_ACCOUNT` |
> | `STRIPE_POST_CUSTOMERS_CUSTOMER_BANK_ACCOUNTS_ID` | `STRIPE_UPDATE_CUSTOMER_BANK_ACCOUNT` |
> | `STRIPE_POST_CUSTOMERS_CUSTOMER_CARDS` | `STRIPE_CREATE_CUSTOMER_CARD` |
> | `STRIPE_POST_CUSTOMERS_CUSTOMER_CARDS_ID` | `STRIPE_UPDATE_CUSTOMER_CARD` |
> | `STRIPE_POST_CUSTOMERS_CUSTOMER_SOURCES` | `STRIPE_CREATE_CUSTOMER_SOURCE` |
> | `STRIPE_POST_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS` | `STRIPE_CREATE_CUSTOMER_SUBSCRIPTION` |
> | `STRIPE_POST_DISPUTES_DISPUTE_CLOSE` | `STRIPE_CLOSE_DISPUTE` |
> | `STRIPE_POST_ENTITLEMENTS_FEATURES_ID` | `STRIPE_UPDATE_ENTITLEMENT_FEATURE` |
> | `STRIPE_POST_FINANCIAL_CONNECTIONS_SESSIONS` | `STRIPE_CREATE_FINANCIAL_CONNECTIONS_SESSION` |
> | `STRIPE_POST_INVOICEITEMS` | `STRIPE_CREATE_INVOICE_ITEM` |
> | `STRIPE_POST_INVOICES_INVOICE_ATTACH_PAYMENT` | `STRIPE_ATTACH_INVOICE_PAYMENT` |
> | `STRIPE_POST_INVOICES_INVOICE_MARK_UNCOLLECTIBLE` | `STRIPE_MARK_INVOICE_UNCOLLECTIBLE` |
> | `STRIPE_POST_INVOICES_INVOICE_PAY` | `STRIPE_PAY_INVOICE` |
> | `STRIPE_POST_INVOICES_INVOICE_UPDATE_LINES` | `STRIPE_UPDATE_INVOICE_LINES` |
> | `STRIPE_POST_PAYMENT_METHOD_CONFIGURATIONS` | `STRIPE_CREATE_PAYMENT_METHOD_CONFIGURATION` |
> | `STRIPE_POST_PLANS` | `STRIPE_CREATE_PLAN` |
> | `STRIPE_POST_QUOTES_QUOTE` | `STRIPE_UPDATE_QUOTE` |
> | `STRIPE_POST_SETUP_INTENTS` | `STRIPE_CREATE_SETUP_INTENT` |
> | `STRIPE_POST_SOURCES_SOURCE` | `STRIPE_UPDATE_SOURCE` |
> | `STRIPE_POST_SUBSCRIPTIONS_SUBSCRIPTION_MIGRATE` | `STRIPE_MIGRATE_SUBSCRIPTION` |
> | `STRIPE_POST_SUBSCRIPTION_SCHEDULES` | `STRIPE_CREATE_SUBSCRIPTION_SCHEDULE` |
> | `STRIPE_POST_SUBSCRIPTION_SCHEDULES_SCHEDULE` | `STRIPE_UPDATE_SUBSCRIPTION_SCHEDULE` |
> | `STRIPE_POST_SUBSCRIPTION_SCHEDULES_SCHEDULE_CANCEL` | `STRIPE_CANCEL_SUBSCRIPTION_SCHEDULE` |
> | `STRIPE_POST_TAX_CALCULATIONS` | `STRIPE_CREATE_TAX_CALCULATION` |
> | `STRIPE_POST_TAX_IDS` | `STRIPE_CREATE_TAX_ID` |
> | `STRIPE_POST_TAX_REGISTRATIONS` | `STRIPE_CREATE_TAX_REGISTRATION` |
> | `STRIPE_POST_TAX_REGISTRATIONS_ID` | `STRIPE_UPDATE_TAX_REGISTRATION` |
> | `STRIPE_POST_TAX_SETTINGS` | `STRIPE_UPDATE_TAX_SETTINGS` |
> | `STRIPE_POST_TAX_TRANSACTIONS_CREATE_FROM_CALCULATION` | `STRIPE_CREATE_TAX_TRANSACTION_FROM_CALCULATION` |
> | `STRIPE_POST_TERMINAL_CONFIGURATIONS` | `STRIPE_CREATE_TERMINAL_CONFIGURATION` |
> | `STRIPE_POST_TERMINAL_CONNECTION_TOKENS` | `STRIPE_CREATE_TERMINAL_CONNECTION_TOKEN` |
> | `STRIPE_POST_TERMINAL_LOCATIONS_LOCATION` | `STRIPE_UPDATE_TERMINAL_LOCATION` |
> | `STRIPE_POST_TERMINAL_READERS_CANCEL_ACTION_SET_READER` | `STRIPE_CANCEL_TERMINAL_READER_ACTION` |
> | `STRIPE_POST_TERMINAL_READERS_COLLECT_INPUTS_SET_READER` | `STRIPE_COLLECT_TERMINAL_READER_INPUTS` |
> | `STRIPE_POST_TERMINAL_READERS_CONFIRM_PAYMENT_INTENT_SET` | `STRIPE_CONFIRM_TERMINAL_READER_PAYMENT_INTENT` |
> | `STRIPE_POST_TERMINAL_READERS_READER` | `STRIPE_UPDATE_TERMINAL_READER` |
> | `STRIPE_POST_TERMINAL_READERS_READER_COLLECT_PAYMENT_METHOD` | `STRIPE_COLLECT_TERMINAL_READER_PAYMENT_METHOD` |
> | `STRIPE_POST_TEST_HELPERS_TERMINAL_READERS_READER_SUCCEED` | `STRIPE_SUCCEED_TEST_TERMINAL_READER_INPUT_COLLECTION` |
> | `STRIPE_POST_TEST_HELPERS_TERMINAL_READERS_READER_TIMEOUT` | `STRIPE_TIMEOUT_TEST_TERMINAL_READER_INPUT_COLLECTION` |
> | `STRIPE_POST_TEST_HELPERS_TEST_CLOCKS` | `STRIPE_CREATE_TEST_CLOCK` |
> | `STRIPE_POST_TEST_HELPERS_TEST_CLOCKS_ADVANCE_DELETE_A_TEST` | `STRIPE_ADVANCE_TEST_CLOCK` |
> | `STRIPE_POST_TOKENS` | `STRIPE_CREATE_TOKEN` |
> | `STRIPE_POST_V1_CUSTOMERS_SOURCES_SOURCES` | `STRIPE_ATTACH_CUSTOMER_SOURCE` |
> | `STRIPE_POST_V1_CUSTOMERS_SOURCES_THE_BANK_ACCOUNT` | `STRIPE_UPDATE_CUSTOMER_BANK_ACCOUNT_SOURCE` |
> | `STRIPE_POST_V1_FX_QUOTES_FX_QUOTES` | `STRIPE_CREATE_FX_QUOTE` |
> | `STRIPE_POST_V2_BILLING_METER_EVENT_SESSION_OVERVIEW` | `STRIPE_CREATE_BILLING_METER_EVENT_SESSION` |
> | `STRIPE_RETRIEVE_AN_UPCOMING_INVOICE` | `STRIPE_RETRIEVE_UPCOMING_INVOICE` |
> | `STRIPE_RETRIEVE_COUPON` | `STRIPE_GET_COUPON` |
> | `STRIPE_RETRIEVE_FILE_LINK` | `STRIPE_GET_FILE_LINKS_LINK` |
> | `STRIPE_RETRIEVE_MANDATE` | `STRIPE_GET_MANDATE` |
> | `STRIPE_RETRIEVE_PAYMENT_LINK` | `STRIPE_GET_PAYMENT_LINK` |
> | `STRIPE_RETRIEVE_PAYOUT` | `STRIPE_GET_PAYOUT` |
> | `STRIPE_RETRIEVE_SETUP_INTENT` | `STRIPE_GET_SETUP_INTENT` |
> | `STRIPE_RETRIEVE_SHIPPING_RATE` | `STRIPE_GET_SHIPPING_RATE` |
> | `STRIPE_RETRIEVE_SUBSCRIPTION` | `STRIPE_GET_SUBSCRIPTION` |
> | `STRIPE_RETRIEVE_SUBSCRIPTION_ITEM` | `STRIPE_GET_SUBSCRIPTION_ITEM` |
> | `STRIPE_RETRIEVE_UPCOMING_INVOICE_LINE_ITEMS` | `STRIPE_GET_UPCOMING_INVOICE_LINE_ITEMS` |

> [accordion] GitHub (156 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `GITHUB_ACCEPT_A_REPOSITORY_INVITATION` | `GITHUB_ACCEPT_REPOSITORY_INVITATION` |
> | `GITHUB_ADD_AN_EMAIL_ADDRESS_FOR_THE_AUTHENTICATED_USER` | `GITHUB_ADD_EMAIL_ADDRESS_FOR_AUTHENTICATED_USER` |
> | `GITHUB_ADD_A_REPOSITORY_TO_AN_APP_INSTALLATION` | `GITHUB_ADD_REPOSITORY_TO_APP_INSTALLATION` |
> | `GITHUB_ADD_A_SELECTED_REPOSITORY_TO_A_USER_SECRET` | `GITHUB_ADD_SELECTED_REPOSITORY_TO_USER_SECRET` |
> | `GITHUB_ADD_OR_UPDATE_TEAM_MEMBERSHIP_FOR_A_USER` | `GITHUB_ADD_OR_UPDATE_TEAM_MEMBERSHIP_FOR_USER` |
> | `GITHUB_ADD_SELECTED_REPOSITORY_TO_AN_ORGANIZATION_SECRET` | `GITHUB_ADD_SELECTED_REPOSITORY_TO_ORGANIZATION_SECRET` |
> | `GITHUB_ADD_SELECTED_REPOSITORY_TO_AN_ORGANIZATION_VARIABLE` | `GITHUB_ADD_SELECTED_REPOSITORY_TO_ORGANIZATION_VARIABLE` |
> | `GITHUB_ADD_SOCIAL_ACCOUNTS_FOR_THE_AUTHENTICATED_USER` | `GITHUB_ADD_SOCIAL_ACCOUNTS_FOR_AUTHENTICATED_USER` |
> | `GITHUB_ADD_USERS_TO_CODESPACES_ACCESS_FOR_AN_ORGANIZATION` | `GITHUB_ADD_USERS_TO_CODESPACES_ACCESS_FOR_ORGANIZATION` |
> | `GITHUB_ASSIGN_AN_ORGANIZATION_ROLE_TO_A_TEAM` | `GITHUB_ASSIGN_ORGANIZATION_ROLE_TO_TEAM` |
> | `GITHUB_ASSIGN_AN_ORGANIZATION_ROLE_TO_A_USER` | `GITHUB_ASSIGN_ORGANIZATION_ROLE_TO_USER` |
> | `GITHUB_BLOCK_A_USER` | `GITHUB_BLOCK_USER` |
> | `GITHUB_BLOCK_A_USER_FROM_AN_ORGANIZATION` | `GITHUB_BLOCK_USER_FROM_ORGANIZATION` |
> | `GITHUB_CANCEL_A_GITHUB_PAGES_DEPLOYMENT` | `GITHUB_CANCEL_GITHUB_PAGES_DEPLOYMENT` |
> | `GITHUB_CANCEL_A_WORKFLOW_RUN` | `GITHUB_CANCEL_WORKFLOW_RUN` |
> | `GITHUB_CHANGE_USER_STATUS` | `GITHUB_UPDATE_USER_STATUS` |
> | `GITHUB_CHECK_A_TOKEN` | `GITHUB_CHECK_TOKEN` |
> | `GITHUB_CHECK_IF_A_GIST_IS_STARRED` | `GITHUB_CHECK_IF_GIST_IS_STARRED` |
> | `GITHUB_CHECK_IF_A_PERSON_IS_FOLLOWED_BY_THE_AUTHENTICATED_USER` | `GITHUB_CHECK_PERSON_FOLLOWED_BY_AUTH_USER` |
> | `GITHUB_CHECK_IF_A_PULL_REQUEST_HAS_BEEN_MERGED` | `GITHUB_CHECK_IF_PULL_REQUEST_HAS_BEEN_MERGED` |
> | `GITHUB_CHECK_IF_A_USER_CAN_BE_ASSIGNED` | `GITHUB_CHECK_IF_USER_CAN_BE_ASSIGNED` |
> | `GITHUB_CHECK_IF_A_USER_CAN_BE_ASSIGNED_TO_A_ISSUE` | `GITHUB_CHECK_IF_USER_CAN_BE_ASSIGNED_TO_ISSUE` |
> | `GITHUB_CHECK_IF_A_USER_FOLLOWS_ANOTHER_USER` | `GITHUB_CHECK_IF_USER_FOLLOWS_ANOTHER_USER` |
> | `GITHUB_CHECK_IF_A_USER_IS_A_REPOSITORY_COLLABORATOR` | `GITHUB_CHECK_IF_USER_IS_REPOSITORY_COLLABORATOR` |
> | `GITHUB_CHECK_IF_A_USER_IS_BLOCKED_BY_AN_ORGANIZATION` | `GITHUB_CHECK_IF_USER_IS_BLOCKED_BY_ORGANIZATION` |
> | `GITHUB_CHECK_IF_A_USER_IS_BLOCKED_BY_THE_AUTHENTICATED_USER` | `GITHUB_CHECK_IF_USER_IS_BLOCKED_BY_AUTHENTICATED_USER` |
> | `GITHUB_CONFIGURE_JITRUNNER_FOR_ORG` | `GITHUB_CONFIGURE_JIT_RUNNER_FOR_ORG` |
> | `GITHUB_CONFIGURE_OIDCSUBJECT_CLAIM_TEMPLATE` | `GITHUB_CONFIGURE_OIDC_SUBJECT_CLAIM_TEMPLATE` |
> | `GITHUB_CUSTOMIZE_OIDC_SUBJECT_CLAIM_TEMPLATE` | `GITHUB_GET_OIDC_SUBJECT_CLAIM_TEMPLATE` |
> | `GITHUB_CUSTOM_OIDCSUBJECT_CLAIM_TEMPLATE` | `GITHUB_GET_ORG_OIDC_SUBJECT_CLAIM_TEMPLATE` |
> | `GITHUB_CUSTOM_OIDCSUBJECT_CLAIM_TEMPLATE_SETTER` | `GITHUB_SET_OIDC_SUBJECT_CLAIM_TEMPLATE` |
> | `GITHUB_DELETE_AN_APP_AUTHORIZATION` | `GITHUB_DELETE_APP_AUTHORIZATION` |
> | `GITHUB_DELETE_AN_APP_TOKEN` | `GITHUB_DELETE_APP_TOKEN` |
> | `GITHUB_DELETE_AN_ARTIFACT` | `GITHUB_DELETE_ARTIFACT` |
> | `GITHUB_DELETE_AN_AUTOLINK_REFERENCE_FROM_A_REPOSITORY` | `GITHUB_DELETE_AUTOLINK_REFERENCE` |
> | `GITHUB_DELETE_AN_EMAIL_ADDRESS_FOR_THE_AUTHENTICATED_USER` | `GITHUB_DELETE_EMAIL_ADDRESS` |
> | `GITHUB_DELETE_AN_ENVIRONMENT` | `GITHUB_DELETE_ENVIRONMENT` |
> | `GITHUB_DELETE_AN_ENVIRONMENT_SECRET` | `GITHUB_DELETE_ENVIRONMENT_SECRET` |
> | `GITHUB_DELETE_AN_ENVIRONMENT_VARIABLE` | `GITHUB_DELETE_ENVIRONMENT_VARIABLE` |
> | `GITHUB_DELETE_AN_ISSUE_COMMENT` | `GITHUB_DELETE_ISSUE_COMMENT` |
> | `GITHUB_DELETE_AN_ISSUE_COMMENT_REACTION` | `GITHUB_DELETE_ISSUE_COMMENT_REACTION` |
> | `GITHUB_DELETE_AN_ISSUE_REACTION` | `GITHUB_DELETE_ISSUE_REACTION` |
> | `GITHUB_DELETE_AN_ORGANIZATION` | `GITHUB_DELETE_ORGANIZATION` |
> | `GITHUB_DELETE_AN_ORGANIZATION_SECRET` | `GITHUB_DELETE_ORGANIZATION_SECRET` |
> | `GITHUB_DELETE_AN_ORGANIZATION_VARIABLE` | `GITHUB_DELETE_ORGANIZATION_VARIABLE` |
> | `GITHUB_DELETE_AN_ORGANIZATION_WEBHOOK` | `GITHUB_DELETE_ORGANIZATION_WEBHOOK` |
> | `GITHUB_DELETE_A_CODESPACE_FOR_THE_AUTHENTICATED_USER` | `GITHUB_DELETE_CODESPACE` |
> | `GITHUB_DELETE_A_CODESPACE_FROM_THE_ORGANIZATION` | `GITHUB_DELETE_ORG_CODESPACE` |
> | `GITHUB_DELETE_A_CODE_SCANNING_ANALYSIS_FROM_A_REPOSITORY` | `GITHUB_DELETE_CODE_SCANNING_ANALYSIS` |
> | `GITHUB_DELETE_A_COMMIT_COMMENT` | `GITHUB_DELETE_COMMIT_COMMENT` |
> | `GITHUB_DELETE_A_COMMIT_COMMENT_REACTION` | `GITHUB_DELETE_COMMIT_COMMENT_REACTION` |
> | `GITHUB_DELETE_A_CUSTOM_ORGANIZATION_ROLE` | `GITHUB_DELETE_CUSTOM_ORGANIZATION_ROLE` |
> | `GITHUB_DELETE_A_DEPLOYMENT` | `GITHUB_DELETE_DEPLOYMENT` |
> | `GITHUB_DELETE_A_DEPLOYMENT_BRANCH_POLICY` | `GITHUB_DELETE_DEPLOYMENT_BRANCH_POLICY` |
> | `GITHUB_DELETE_A_DEPLOY_KEY` | `GITHUB_DELETE_DEPLOY_KEY` |
> | `GITHUB_DELETE_A_DISCUSSION` | `GITHUB_DELETE_DISCUSSION` |
> | `GITHUB_DELETE_A_DISCUSSION_COMMENT` | `GITHUB_DELETE_DISCUSSION_COMMENT` |
> | `GITHUB_DELETE_A_GIST` | `GITHUB_DELETE_GIST` |
> | `GITHUB_DELETE_A_GIST_COMMENT` | `GITHUB_DELETE_GIST_COMMENT` |
> | `GITHUB_DELETE_A_GITHUB_PAGES_SITE` | `GITHUB_DELETE_GITHUB_PAGES_SITE` |
> | `GITHUB_DELETE_A_LABEL` | `GITHUB_DELETE_LABEL` |
> | `GITHUB_DELETE_A_MILESTONE` | `GITHUB_DELETE_MILESTONE` |
> | `GITHUB_DELETE_A_PACKAGE_FOR_AN_ORGANIZATION` | `GITHUB_DELETE_ORG_PACKAGE` |
> | `GITHUB_DELETE_A_PACKAGE_FOR_A_USER` | `GITHUB_DELETE_USER_PACKAGE` |
> | `GITHUB_DELETE_A_PACKAGE_FOR_THE_AUTHENTICATED_USER` | `GITHUB_DELETE_PACKAGE` |
> | `GITHUB_DELETE_A_PENDING_REVIEW_FOR_A_PULL_REQUEST` | `GITHUB_DELETE_PENDING_REVIEW` |
> | `GITHUB_DELETE_A_PROJECT` | `GITHUB_DELETE_PROJECT` |
> | `GITHUB_DELETE_A_PROJECT_CARD` | `GITHUB_DELETE_PROJECT_CARD` |
> | `GITHUB_DELETE_A_PROJECT_COLUMN` | `GITHUB_DELETE_PROJECT_COLUMN` |
> | `GITHUB_DELETE_A_PULL_REQUEST_COMMENT_REACTION` | `GITHUB_DELETE_PULL_REQUEST_COMMENT_REACTION` |
> | `GITHUB_ENABLE_REPO_FORGITHUB_ACTIONS` | `GITHUB_ENABLE_REPO_FOR_GITHUB_ACTIONS` |
> | `GITHUB_ENCRYPT_ORG_SECRETS_USING_PUBLIC_KEY` | `GITHUB_GET_ORGANIZATION_PUBLIC_KEY` |
> | `GITHUB_EXPORT_A_SOFTWARE_BILL_OF_MATERIALS_SBOM_FOR_A_REPOSITORY` | `GITHUB_EXPORT_SBOM_FOR_REPO` |
> | `GITHUB_FETCH_GRAPH_QL_NODE` | `GITHUB_GET_GRAPHQL_NODE` |
> | `GITHUB_FETCH_PUBLIC_KEY_FOR_SECRET_ENCRYPTION` | `GITHUB_GET_ORGANIZATION_PUBLIC_KEY_FOR_DEPENDABOT` |
> | `GITHUB_FOLLOW_A_USER` | `GITHUB_FOLLOW_USER` |
> | `GITHUB_FOLLOW_ORGANIZATION_GRAPH_QL` | `GITHUB_FOLLOW_ORGANIZATION_GRAPHQL` |
> | `GITHUB_FOLLOW_USER_GRAPH_QL` | `GITHUB_FOLLOW_USER_GRAPHQL` |
> | `GITHUB_FORCE_CANCEL_A_WORKFLOW_RUN` | `GITHUB_FORCE_CANCEL_WORKFLOW_RUN` |
> | `GITHUB_FORK_A_GIST` | `GITHUB_FORK_GIST` |
> | `GITHUB_GENERATE_RELEASE_NOTES_CONTENT_FOR_A_RELEASE` | `GITHUB_GENERATE_RELEASE_NOTES` |
> | `GITHUB_GET_ALL_AUTOLINKS_OF_A_REPOSITORY` | `GITHUB_LIST_REPOSITORY_AUTOLINKS` |
> | `GITHUB_GET_ALL_CODES_OF_CONDUCT` | `GITHUB_LIST_CODES_OF_CONDUCT` |
> | `GITHUB_GET_ALL_COMMONLY_USED_LICENSES` | `GITHUB_LIST_COMMONLY_USED_LICENSES` |
> | `GITHUB_GET_ALL_CUSTOM_PROPERTIES_FOR_AN_ORGANIZATION` | `GITHUB_LIST_CUSTOM_PROPERTIES_FOR_AN_ORGANIZATION` |
> | `GITHUB_GET_ALL_CUSTOM_PROPERTY_VALUES_FOR_A_REPOSITORY` | `GITHUB_LIST_CUSTOM_PROPERTY_VALUES_FOR_A_REPOSITORY` |
> | `GITHUB_GET_ALL_DEPLOYMENT_PROTECTION_RULES_FOR_AN_ENVIRONMENT` | `GITHUB_GET_ALL_DEPLOYMENT_PROTECTION_RULES_FOR_ENV` |
> | `GITHUB_GET_ALL_GITIGNORE_TEMPLATES` | `GITHUB_LIST_GITIGNORE_TEMPLATES` |
> | `GITHUB_GET_ALL_ORGANIZATION_ROLES_FOR_AN_ORGANIZATION` | `GITHUB_LIST_ORGANIZATION_ROLES_FOR_AN_ORGANIZATION` |
> | `GITHUB_GET_ALL_REPOSITORY_RULESETS` | `GITHUB_LIST_REPOSITORY_RULESETS` |
> | `GITHUB_GET_ALL_REPOSITORY_TOPICS` | `GITHUB_LIST_REPOSITORY_TOPICS` |
> | `GITHUB_GET_ALL_STATUS_CHECK_CONTEXTS` | `GITHUB_LIST_STATUS_CHECK_CONTEXTS` |
> | `GITHUB_GET_APPS_WITH_ACCESS_TO_THE_PROTECTED_BRANCH` | `GITHUB_LIST_APPS_WITH_ACCESS_TO_THE_PROTECTED_BRANCH` |
> | `GITHUB_GET_A_CHECK_RUN` | `GITHUB_GET_CHECK_RUN` |
> | `GITHUB_GET_A_CHECK_SUITE` | `GITHUB_GET_CHECK_SUITE` |
> | `GITHUB_GET_A_CLASSROOM` | `GITHUB_GET_CLASSROOM` |
> | `GITHUB_GET_A_CODESPACE_FOR_THE_AUTHENTICATED_USER` | `GITHUB_GET_CODESPACE` |
> | `GITHUB_GET_A_CODE_OF_CONDUCT` | `GITHUB_GET_CODE_OF_CONDUCT` |
> | `GITHUB_GET_A_CODE_QL_DATABASE_FOR_A_REPOSITORY` | `GITHUB_GET_CODEQL_DATABASE` |
> | `GITHUB_GET_A_CODE_SCANNING_ALERT` | `GITHUB_GET_CODE_SCANNING_ALERT` |
> | `GITHUB_GET_A_CODE_SCANNING_ANALYSIS_FOR_A_REPOSITORY` | `GITHUB_GET_CODE_SCANNING_ANALYSIS` |
> | `GITHUB_GET_A_CODE_SCANNING_DEFAULT_SETUP_CONFIGURATION` | `GITHUB_GET_CODE_SCANNING_DEFAULT_SETUP` |
> | `GITHUB_GET_A_COMMIT_COMMENT` | `GITHUB_GET_COMMIT_COMMENT` |
> | `GITHUB_GET_A_COMMIT_OBJECT` | `GITHUB_GET_COMMIT_OBJECT` |
> | `GITHUB_GET_A_CUSTOM_DEPLOYMENT_PROTECTION_RULE` | `GITHUB_GET_CUSTOM_DEPLOYMENT_PROTECTION_RULE` |
> | `GITHUB_GET_A_CUSTOM_PROPERTY_FOR_AN_ORGANIZATION` | `GITHUB_GET_ORGANIZATION_CUSTOM_PROPERTY` |
> | `GITHUB_GET_A_DELIVERY_FOR_A_REPOSITORY_WEBHOOK` | `GITHUB_GET_REPOSITORY_WEBHOOK_DELIVERY` |
> | `GITHUB_GET_A_DEPLOYMENT` | `GITHUB_GET_DEPLOYMENT` |
> | `GITHUB_GET_A_DEPLOYMENT_BRANCH_POLICY` | `GITHUB_GET_DEPLOYMENT_BRANCH_POLICY` |
> | `GITHUB_GET_A_DEPLOYMENT_STATUS` | `GITHUB_GET_DEPLOYMENT_STATUS` |
> | `GITHUB_GET_A_DEPLOY_KEY` | `GITHUB_GET_DEPLOY_KEY` |
> | `GITHUB_GET_A_DIFF_OF_THE_DEPENDENCIES_BETWEEN_COMMITS` | `GITHUB_GET_DEPENDENCY_DIFF` |
> | `GITHUB_GET_A_DISCUSSION` | `GITHUB_GET_DISCUSSION` |
> | `GITHUB_GET_A_DISCUSSION_COMMENT` | `GITHUB_GET_DISCUSSION_COMMENT` |
> | `GITHUB_GET_A_DNS_HEALTH_CHECK_FOR_GITHUB_PAGES` | `GITHUB_GET_PAGES_DNS_HEALTH_CHECK` |
> | `GITHUB_GET_A_GIST` | `GITHUB_GET_GIST` |
> | `GITHUB_GET_A_GIST_COMMENT` | `GITHUB_GET_GIST_COMMENT` |
> | `GITHUB_GET_A_GIST_REVISION` | `GITHUB_GET_GIST_REVISION` |
> | `GITHUB_GET_A_GITHUB_PAGES_SITE` | `GITHUB_GET_PAGES_SITE` |
> | `GITHUB_GET_A_GITIGNORE_TEMPLATE` | `GITHUB_GET_GITIGNORE_TEMPLATE` |
> | `GITHUB_GET_A_JOB_FOR_A_WORKFLOW_RUN` | `GITHUB_GET_WORKFLOW_RUN_JOB` |
> | `GITHUB_GET_A_LABEL` | `GITHUB_GET_LABEL` |
> | `GITHUB_GET_A_LICENSE` | `GITHUB_GET_LICENSE` |
> | `GITHUB_GET_USERS_PROJECTSV2` | `GITHUB_GET_USERS_PROJECTS_V2` |
> | `GITHUB_GET_VIEWER_GRAPH_QL` | `GITHUB_GET_VIEWER_GRAPHQL` |
> | `GITHUB_LIST_CODES_OF_CONDUCT_GRAPH_QL` | `GITHUB_LIST_CODES_OF_CONDUCT_GRAPHQL` |
> | `GITHUB_LIST_CODE_QL_DATABASES_FOR_A_REPOSITORY` | `GITHUB_LIST_CODEQL_DATABASES_FOR_A_REPOSITORY` |
> | `GITHUB_LIST_GPG_KEYS_FOR_USER` | `GITHUB_LIST_GPG_KEYS_FOR_A_USER` |
> | `GITHUB_LIST_ORGANIZATION_MEMBERSHIPS_FOR_AUTHENTICATED_USER` | `GITHUB_LIST_ORGANIZATION_MEMBERSHIPS_FOR_THE_AUTHENTICATED_U` |
> | `GITHUB_LIST_ORG_ISSUES_FOR_USER` | `GITHUB_LIST_ORG_ISSUES_FOR_THE_AUTHENTICATED_USER` |
> | `GITHUB_LIST_ORG_LEVEL_CODESPACES_SECRETS` | `GITHUB_LIST_ORGANIZATION_CODESPACES_SECRETS` |
> | `GITHUB_LIST_ORG_REPOS_WITHGITHUB_ACTIONS_ENABLED` | `GITHUB_LIST_ORG_REPOS_WITH_GITHUB_ACTIONS_ENABLED` |
> | `GITHUB_LIST_PACKAGES_FOR_THE_AUTHENTICATED_USER_S_NAMESPACE` | `GITHUB_LIST_PACKAGES_FOR_THE_AUTHENTICATED_USER` |
> | `GITHUB_LIST_PROJECTS_FIELDS_FOR_USER` | `GITHUB_LIST_PROJECT_FIELDS_FOR_USER` |
> | `GITHUB_LIST_REPOS_WITH_GHACTIONS_CACHE_USAGE` | `GITHUB_LIST_REPOSITORIES_WITH_GITHUB_ACTIONS_CACHE_USAGE` |
> | `GITHUB_LIST_SECURITY_ADVISORIES_GRAPH_QL` | `GITHUB_LIST_SECURITY_ADVISORIES_GRAPHQL` |
> | `GITHUB_LIST_SELECTED_REPOS_FOR_SECRET_ACCESS` | `GITHUB_LIST_SELECTED_REPOSITORIES_FOR_SECRET_ACCESS` |
> | `GITHUB_LIST_SSH_SIGNING_KEYS_FOR_USER` | `GITHUB_LIST_SSH_SIGNING_KEYS_FOR_A_USER` |
> | `GITHUB_LIST_SUBSCRIPTIONS_FOR_AUTHENTICATED_USER` | `GITHUB_LIST_SUBSCRIPTIONS_FOR_THE_AUTHENTICATED_USER` |
> | `GITHUB_RETRIEVE_REPO_PUBLIC_KEY_FOR_ENCRYPTION` | `GITHUB_GET_REPOSITORY_PUBLIC_KEY_FOR_ENCRYPTION` |
> | `GITHUB_SYNC_A_FORK_BRANCH_WITH_THE_UPSTREAM_REPOSITORY` | `GITHUB_SYNC_FORK_BRANCH_WITH_UPSTREAM` |
> | `GITHUB_TEST_THE_PUSH_REPOSITORY_WEBHOOK` | `GITHUB_TEST_REPOSITORY_WEBHOOK` |
> | `GITHUB_UNBLOCK_A_USER_FROM_AN_ORGANIZATION` | `GITHUB_UNBLOCK_USER_FROM_ORGANIZATION` |
> | `GITHUB_UNLOCK_AN_ORGANIZATION_REPOSITORY` | `GITHUB_UNLOCK_ORGANIZATION_REPOSITORY` |
> | `GITHUB_UNLOCK_A_USER_REPOSITORY` | `GITHUB_UNLOCK_USER_REPOSITORY` |
> | `GITHUB_UNSTAR_A_REPOSITORY_FOR_THE_AUTHENTICATED_USER` | `GITHUB_UNSTAR_REPOSITORY` |
> | `GITHUB_UPDATE_AN_EXISTING_PROJECT_CARD` | `GITHUB_UPDATE_PROJECT_CARD` |
> | `GITHUB_UPDATE_AN_EXISTING_PROJECT_COLUMN` | `GITHUB_UPDATE_PROJECT_COLUMN` |
> | `GITHUB_UPDATE_A_CODESPACE_FOR_THE_AUTHENTICATED_USER` | `GITHUB_UPDATE_CODESPACE` |
> | `GITHUB_UPDATE_A_CODE_SCANNING_DEFAULT_SETUP_CONFIGURATION` | `GITHUB_UPDATE_CODE_SCANNING_DEFAULT_SETUP` |
> | `GITHUB_UPDATE_A_REVIEW_COMMENT_FOR_A_PULL_REQUEST` | `GITHUB_UPDATE_PULL_REQUEST_REVIEW_COMMENT` |
> | `GITHUB_UPDATE_A_REVIEW_FOR_A_PULL_REQUEST` | `GITHUB_UPDATE_PULL_REQUEST_REVIEW` |
> | `GITHUB_UPDATE_A_WEBHOOK_CONFIGURATION_FOR_AN_ORGANIZATION` | `GITHUB_UPDATE_ORGANIZATION_WEBHOOK_CONFIGURATION` |
> | `GITHUB_UPDATE_A_WEBHOOK_CONFIGURATION_FOR_A_REPOSITORY` | `GITHUB_UPDATE_REPOSITORY_WEBHOOK_CONFIGURATION` |
> | `GITHUB_UPDATE_PROJECTS_V2_ITEM_FOR_USER` | `GITHUB_UPDATE_USER_PROJECT_ITEM` |
> | `GITHUB_UPLOAD_AN_ANALYSIS_AS_SARIF_DATA` | `GITHUB_UPLOAD_SARIF_ANALYSIS` |

> [accordion] Pipedrive (156 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `PIPEDRIVE_ADD_AN_INSTALLMENT_SUBSCRIPTION` | `PIPEDRIVE_ADD_INSTALLMENT_SUBSCRIPTION` |
> | `PIPEDRIVE_ADD_A_CALL_LOG` | `PIPEDRIVE_ADD_CALL_LOG` |
> | `PIPEDRIVE_ADD_A_CHANNEL` | `PIPEDRIVE_ADD_CHANNEL` |
> | `PIPEDRIVE_ADD_A_FOLLOWER_TO_A_DEAL` | `PIPEDRIVE_ADD_DEAL_FOLLOWER` |
> | `PIPEDRIVE_ADD_A_LEAD` | `PIPEDRIVE_ADD_LEAD` |
> | `PIPEDRIVE_ADD_A_LEAD_LABEL` | `PIPEDRIVE_ADD_LEAD_LABEL` |
> | `PIPEDRIVE_ADD_A_NEW_DEAL_FIELD` | `PIPEDRIVE_ADD_DEAL_FIELD` |
> | `PIPEDRIVE_ADD_A_NEW_FILTER` | `PIPEDRIVE_ADD_FILTER` |
> | `PIPEDRIVE_ADD_A_NEW_GOAL` | `PIPEDRIVE_ADD_GOAL` |
> | `PIPEDRIVE_ADD_A_NEW_ORGANIZATION_FIELD` | `PIPEDRIVE_ADD_ORGANIZATION_FIELD` |
> | `PIPEDRIVE_ADD_A_NEW_PERSON_FIELD` | `PIPEDRIVE_ADD_PERSON_FIELD` |
> | `PIPEDRIVE_ADD_A_NEW_PIPELINE` | `PIPEDRIVE_ADD_PIPELINE` |
> | `PIPEDRIVE_ADD_A_NEW_PRODUCT_FIELD` | `PIPEDRIVE_ADD_PRODUCT_FIELD` |
> | `PIPEDRIVE_ADD_A_NEW_STAGE` | `PIPEDRIVE_ADD_STAGE` |
> | `PIPEDRIVE_ADD_A_NEW_TEAM` | `PIPEDRIVE_ADD_TEAM` |
> | `PIPEDRIVE_ADD_A_NEW_USER` | `PIPEDRIVE_ADD_USER` |
> | `PIPEDRIVE_ADD_A_PARTICIPANT_TO_A_DEAL` | `PIPEDRIVE_ADD_DEAL_PARTICIPANT` |
> | `PIPEDRIVE_ADD_A_PRODUCT` | `PIPEDRIVE_ADD_PRODUCT` |
> | `PIPEDRIVE_ADD_A_PROJECT` | `PIPEDRIVE_ADD_PROJECT` |
> | `PIPEDRIVE_ADD_A_RECURRING_SUBSCRIPTION` | `PIPEDRIVE_ADD_RECURRING_SUBSCRIPTION` |
> | `PIPEDRIVE_ADD_A_ROLE` | `PIPEDRIVE_ADD_ROLE` |
> | `PIPEDRIVE_ADD_A_TASK` | `PIPEDRIVE_ADD_TASK` |
> | `PIPEDRIVE_ADD_NEW_ACTIVITY_TYPE` | `PIPEDRIVE_ADD_ACTIVITY_TYPE` |
> | `PIPEDRIVE_ADD_USERS_TO_A_TEAM` | `PIPEDRIVE_ADD_TEAM_USERS` |
> | `PIPEDRIVE_ARCHIVE_A_PROJECT` | `PIPEDRIVE_ARCHIVE_PROJECT` |
> | `PIPEDRIVE_CANCEL_A_RECURRING_SUBSCRIPTION` | `PIPEDRIVE_CANCEL_RECURRING_SUBSCRIPTION` |
> | `PIPEDRIVE_CREATE_AN_ORGANIZATION_RELATIONSHIP` | `PIPEDRIVE_CREATE_ORGANIZATION_RELATIONSHIP` |
> | `PIPEDRIVE_CREATE_A_NEW_WEBHOOK` | `PIPEDRIVE_CREATE_WEBHOOK` |
> | `PIPEDRIVE_CREATE_A_REMOTE_FILE_AND_LINK_IT_TO_AN_ITEM` | `PIPEDRIVE_CREATE_REMOTE_FILE_LINK` |
> | `PIPEDRIVE_DEALS_CONVERT_TO_LEAD` | `PIPEDRIVE_CONVERT_DEAL_TO_LEAD` |
> | `PIPEDRIVE_DEALS_GET_DEALS_PRODUCTS` | `PIPEDRIVE_GET_DEALS_PRODUCTS` |
> | `PIPEDRIVE_DEALS_POST_DEALS` | `PIPEDRIVE_ADD_DEAL_PRODUCTS` |
> | `PIPEDRIVE_DELETE_AN_ORGANIZATION_FIELD` | `PIPEDRIVE_DELETE_ORGANIZATION_FIELD` |
> | `PIPEDRIVE_DELETE_AN_ORGANIZATION_RELATIONSHIP` | `PIPEDRIVE_DELETE_ORGANIZATION_RELATIONSHIP` |
> | `PIPEDRIVE_DELETE_A_CALL_LOG` | `PIPEDRIVE_DELETE_CALL_LOG` |
> | `PIPEDRIVE_DELETE_A_CHANNEL` | `PIPEDRIVE_DELETE_CHANNEL` |
> | `PIPEDRIVE_DELETE_A_CONVERSATION` | `PIPEDRIVE_DELETE_CONVERSATION` |
> | `PIPEDRIVE_DELETE_A_FOLLOWER_FROM_A_PERSON` | `PIPEDRIVE_DELETE_PERSON_FOLLOWER` |
> | `PIPEDRIVE_DELETE_A_FOLLOWER_FROM_A_PRODUCT` | `PIPEDRIVE_DELETE_PRODUCT_FOLLOWER` |
> | `PIPEDRIVE_DELETE_A_LEAD` | `PIPEDRIVE_DELETE_LEAD` |
> | `PIPEDRIVE_DELETE_A_NOTE` | `PIPEDRIVE_DELETE_NOTE` |
> | `PIPEDRIVE_DELETE_A_PARTICIPANT_FROM_A_DEAL` | `PIPEDRIVE_DELETE_DEAL_PARTICIPANT` |
> | `PIPEDRIVE_DELETE_A_PIPELINE` | `PIPEDRIVE_DELETE_PIPELINE` |
> | `PIPEDRIVE_DELETE_A_PRODUCT` | `PIPEDRIVE_DELETE_PRODUCT` |
> | `PIPEDRIVE_DELETE_A_PRODUCT_FIELD` | `PIPEDRIVE_DELETE_PRODUCT_FIELD` |
> | `PIPEDRIVE_DELETE_A_PROJECT` | `PIPEDRIVE_DELETE_PROJECT` |
> | `PIPEDRIVE_DELETE_A_ROLE` | `PIPEDRIVE_DELETE_ROLE` |
> | `PIPEDRIVE_DELETE_A_ROLE_ASSIGNMENT` | `PIPEDRIVE_DELETE_ROLE_ASSIGNMENT` |
> | `PIPEDRIVE_DELETE_A_SUBSCRIPTION` | `PIPEDRIVE_DELETE_SUBSCRIPTION` |
> | `PIPEDRIVE_DELETE_A_TASK` | `PIPEDRIVE_DELETE_TASK` |
> | `PIPEDRIVE_DELETE_DEALFIELDS_OPTIONS` | `PIPEDRIVE_DELETE_DEAL_FIELD_OPTIONS` |
> | `PIPEDRIVE_DELETE_DEALS_PRODUCTS` | `PIPEDRIVE_DELETE_DEAL_PRODUCTS` |
> | `PIPEDRIVE_DELETE_EXISTING_GOAL` | `PIPEDRIVE_DELETE_GOAL` |
> | `PIPEDRIVE_DELETE_EXISTING_WEBHOOK` | `PIPEDRIVE_DELETE_WEBHOOK` |
> | `PIPEDRIVE_DELETE_MULTIPLE_ACTIVITIES_IN_BULK` | `PIPEDRIVE_DELETE_ACTIVITIES_BULK` |
> | `PIPEDRIVE_DELETE_MULTIPLE_ACTIVITY_TYPES_IN_BULK` | `PIPEDRIVE_DELETE_ACTIVITY_TYPES_BULK` |
> | `PIPEDRIVE_DELETE_MULTIPLE_DEALS_IN_BULK` | `PIPEDRIVE_DELETE_DEALS_BULK` |
> | `PIPEDRIVE_DELETE_MULTIPLE_DEAL_FIELDS_IN_BULK` | `PIPEDRIVE_DELETE_DEAL_FIELDS_BULK` |
> | `PIPEDRIVE_DELETE_MULTIPLE_FILTERS_IN_BULK` | `PIPEDRIVE_DELETE_FILTERS_BULK` |
> | `PIPEDRIVE_DELETE_MULTIPLE_ORGANIZATIONS_IN_BULK` | `PIPEDRIVE_DELETE_ORGANIZATIONS_BULK` |
> | `PIPEDRIVE_DELETE_MULTIPLE_ORGANIZATION_FIELDS_IN_BULK` | `PIPEDRIVE_DELETE_ORGANIZATION_FIELDS_BULK` |
> | `PIPEDRIVE_DELETE_MULTIPLE_PERSONS_IN_BULK` | `PIPEDRIVE_DELETE_PERSONS_BULK` |
> | `PIPEDRIVE_DELETE_MULTIPLE_PERSON_FIELDS_IN_BULK` | `PIPEDRIVE_DELETE_PERSON_FIELDS_BULK` |
> | `PIPEDRIVE_DELETE_MULTIPLE_PRODUCT_FIELDS_IN_BULK` | `PIPEDRIVE_DELETE_MULTIPLE_PRODUCT_FIELDS` |
> | `PIPEDRIVE_DELETE_MULTIPLE_STAGES_IN_BULK` | `PIPEDRIVE_DELETE_MULTIPLE_STAGES` |
> | `PIPEDRIVE_DELETE_PERSONFIELDS_OPTIONS` | `PIPEDRIVE_DELETE_PERSON_FIELD_OPTIONS` |
> | `PIPEDRIVE_DELETE_PRODUCTFIELDS_OPTIONS` | `PIPEDRIVE_DELETE_PRODUCT_FIELD_OPTIONS` |
> | `PIPEDRIVE_DELETE_USERS_FROM_A_TEAM` | `PIPEDRIVE_DELETE_TEAM_USERS` |
> | `PIPEDRIVE_DOWNLOAD_ONE_FILE` | `PIPEDRIVE_DOWNLOAD_FILE` |
> | `PIPEDRIVE_FIND_SUBSCRIPTION_BY_DEAL` | `PIPEDRIVE_GET_DEAL_SUBSCRIPTION` |
> | `PIPEDRIVE_GET_ALL_ADD_ONS_FOR_A_SINGLE_COMPANY` | `PIPEDRIVE_GET_COMPANY_ADD_ONS` |
> | `PIPEDRIVE_GET_ALL_CALL_LOGS_ASSIGNED_TO_A_PARTICULAR_USER` | `PIPEDRIVE_GET_USER_CALL_LOGS` |
> | `PIPEDRIVE_GET_ALL_COMMENTS_FOR_A_NOTE` | `PIPEDRIVE_GET_NOTE_COMMENTS` |
> | `PIPEDRIVE_GET_ALL_MAIL_MESSAGES_OF_MAIL_THREAD` | `PIPEDRIVE_GET_MAIL_THREAD_MESSAGES` |
> | `PIPEDRIVE_GET_ALL_PAYMENTS_OF_A_SUBSCRIPTION` | `PIPEDRIVE_GET_SUBSCRIPTION_PAYMENTS` |
> | `PIPEDRIVE_GET_A_SINGLE_TEAM` | `PIPEDRIVE_GET_TEAM` |
> | `PIPEDRIVE_GET_DEALS_WHERE_A_PRODUCT_IS_ATTACHED_TO` | `PIPEDRIVE_GET_DEALS_WITH_PRODUCT` |
> | `PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY` | `PIPEDRIVE_GET_ACTIVITY` |
> | `PIPEDRIVE_GET_DETAILS_OF_A_BOARD` | `PIPEDRIVE_GET_PROJECT_BOARD` |
> | `PIPEDRIVE_GET_DETAILS_OF_A_PHASE` | `PIPEDRIVE_GET_PROJECT_PHASE` |
> | `PIPEDRIVE_GET_DETAILS_OF_A_PROJECT` | `PIPEDRIVE_GET_PROJECT` |
> | `PIPEDRIVE_GET_DETAILS_OF_A_SUBSCRIPTION` | `PIPEDRIVE_GET_SUBSCRIPTION` |
> | `PIPEDRIVE_GET_DETAILS_OF_A_TASK` | `PIPEDRIVE_GET_TASK` |
> | `PIPEDRIVE_GET_DETAILS_OF_A_TEMPLATE` | `PIPEDRIVE_GET_TEMPLATE` |
> | `PIPEDRIVE_GET_ONE_COMMENT` | `PIPEDRIVE_GET_COMMENT` |
> | `PIPEDRIVE_GET_ONE_FILE` | `PIPEDRIVE_GET_FILE` |
> | `PIPEDRIVE_GET_ONE_FILTER` | `PIPEDRIVE_GET_FILTER` |
> | `PIPEDRIVE_GET_ONE_MAIL_MESSAGE` | `PIPEDRIVE_GET_MAIL_MESSAGE` |
> | `PIPEDRIVE_GET_ONE_MAIL_THREAD` | `PIPEDRIVE_GET_MAIL_THREAD` |
> | `PIPEDRIVE_GET_ONE_NOTE` | `PIPEDRIVE_GET_NOTE` |
> | `PIPEDRIVE_GET_ONE_ORGANIZATION_RELATIONSHIP` | `PIPEDRIVE_GET_ORGANIZATION_RELATIONSHIP` |
> | `PIPEDRIVE_GET_ONE_PERMISSION_SET` | `PIPEDRIVE_GET_PERMISSION_SET` |
> | `PIPEDRIVE_GET_ONE_PIPELINE` | `PIPEDRIVE_GET_PIPELINE` |
> | `PIPEDRIVE_GET_ONE_PRODUCT` | `PIPEDRIVE_GET_PRODUCT` |
> | `PIPEDRIVE_GET_ONE_PRODUCT_FIELD` | `PIPEDRIVE_GET_PRODUCT_FIELD` |
> | `PIPEDRIVE_GET_ONE_STAGE` | `PIPEDRIVE_GET_STAGE` |
> | `PIPEDRIVE_GET_ONE_USER` | `PIPEDRIVE_GET_USER` |
> | `PIPEDRIVE_GET_PERSONS_PICTURE` | `PIPEDRIVE_GET_PERSON_PICTURE` |
> | `PIPEDRIVE_GET_PRODUCTS_IMAGES` | `PIPEDRIVE_GET_PRODUCT_IMAGES` |
> | `PIPEDRIVE_GET_RESULT_OF_A_GOAL` | `PIPEDRIVE_GET_GOAL_RESULT` |
> | `PIPEDRIVE_LEADS_GET_LEAD_BY_ID` | `PIPEDRIVE_GET_LEAD_CONVERSION_STATUS` |
> | `PIPEDRIVE_LEADS_POST_LEADS` | `PIPEDRIVE_CONVERT_LEAD_TO_DEAL` |
> | `PIPEDRIVE_LINK_A_REMOTE_FILE_TO_AN_ITEM` | `PIPEDRIVE_LINK_REMOTE_FILE` |
> | `PIPEDRIVE_LIST_ACTIVITIES_ASSOCIATED_WITH_AN_ORGANIZATION` | `PIPEDRIVE_LIST_ORGANIZATION_ACTIVITIES` |
> | `PIPEDRIVE_LIST_ACTIVITIES_ASSOCIATED_WITH_A_DEAL` | `PIPEDRIVE_LIST_DEAL_ACTIVITIES` |
> | `PIPEDRIVE_LIST_ACTIVITIES_ASSOCIATED_WITH_A_PERSON` | `PIPEDRIVE_LIST_PERSON_ACTIVITIES` |
> | `PIPEDRIVE_LIST_ALL_PERSONS_ASSOCIATED_WITH_A_DEAL` | `PIPEDRIVE_LIST_DEAL_PERSONS` |
> | `PIPEDRIVE_LIST_DEALS_ASSOCIATED_WITH_AN_ORGANIZATION` | `PIPEDRIVE_LIST_ORGANIZATION_DEALS` |
> | `PIPEDRIVE_LIST_DEALS_ASSOCIATED_WITH_A_PERSON` | `PIPEDRIVE_LIST_PERSON_DEALS` |
> | `PIPEDRIVE_LIST_FILES_ATTACHED_TO_AN_ORGANIZATION` | `PIPEDRIVE_LIST_ORGANIZATION_FILES` |
> | `PIPEDRIVE_LIST_FILES_ATTACHED_TO_A_DEAL` | `PIPEDRIVE_LIST_DEAL_FILES` |
> | `PIPEDRIVE_LIST_FILES_ATTACHED_TO_A_PERSON` | `PIPEDRIVE_LIST_PERSON_FILES` |
> | `PIPEDRIVE_LIST_FILES_ATTACHED_TO_A_PRODUCT` | `PIPEDRIVE_LIST_PRODUCT_FILES` |
> | `PIPEDRIVE_LIST_FOLLOWERS_OF_AN_ORGANIZATION` | `PIPEDRIVE_LIST_ORGANIZATION_FOLLOWERS` |
> | `PIPEDRIVE_LIST_FOLLOWERS_OF_A_DEAL` | `PIPEDRIVE_LIST_DEAL_FOLLOWERS` |
> | `PIPEDRIVE_LIST_FOLLOWERS_OF_A_PERSON` | `PIPEDRIVE_LIST_PERSON_FOLLOWERS` |
> | `PIPEDRIVE_LIST_FOLLOWERS_OF_A_PRODUCT` | `PIPEDRIVE_LIST_PRODUCT_FOLLOWERS` |
> | `PIPEDRIVE_LIST_FOLLOWERS_OF_A_USER` | `PIPEDRIVE_LIST_USER_FOLLOWERS` |
> | `PIPEDRIVE_LIST_MAIL_MESSAGES_ASSOCIATED_WITH_AN_ORGANIZATION` | `PIPEDRIVE_LIST_ORGANIZATION_MAIL_MESSAGES` |
> | `PIPEDRIVE_LIST_MAIL_MESSAGES_ASSOCIATED_WITH_A_DEAL` | `PIPEDRIVE_LIST_DEAL_MAIL_MESSAGES` |
> | `PIPEDRIVE_LIST_MAIL_MESSAGES_ASSOCIATED_WITH_A_PERSON` | `PIPEDRIVE_LIST_PERSON_MAIL_MESSAGES` |
> | `PIPEDRIVE_LIST_PERMITTED_USERS` | `PIPEDRIVE_LIST_DEAL_USERS` |
> | `PIPEDRIVE_LIST_PERSONS_OF_AN_ORGANIZATION` | `PIPEDRIVE_LIST_ORGANIZATION_PERSONS` |
> | `PIPEDRIVE_LIST_PERSON_ACCESS_USERS` | `PIPEDRIVE_LIST_PERSON_USERS` |
> | `PIPEDRIVE_LIST_PIPELINE_VISIBILITY_FOR_A_ROLE` | `PIPEDRIVE_LIST_ROLE_PIPELINE_VISIBILITY` |
> | `PIPEDRIVE_LIST_PRODUCTS_ASSOCIATED_WITH_A_PERSON` | `PIPEDRIVE_LIST_PERSON_PRODUCTS` |
> | `PIPEDRIVE_LIST_PRODUCTS_ATTACHED_TO_A_DEAL` | `PIPEDRIVE_LIST_DEAL_PRODUCTS` |
> | `PIPEDRIVE_LIST_PRODUCT_PERMITTED_USERS` | `PIPEDRIVE_LIST_PRODUCT_USERS` |
> | `PIPEDRIVE_LIST_SETTINGS_OF_AN_AUTHORIZED_USER` | `PIPEDRIVE_LIST_USER_SETTINGS` |
> | `PIPEDRIVE_LIST_UPDATES_ABOUT_A_DEAL` | `PIPEDRIVE_LIST_DEAL_UPDATES` |
> | `PIPEDRIVE_PATCH_DEALFIELDS_OPTIONS` | `PIPEDRIVE_UPDATE_DEALFIELDS_OPTIONS` |
> | `PIPEDRIVE_PATCH_PERSONFIELDS_OPTIONS` | `PIPEDRIVE_UPDATE_PERSONFIELDS_OPTIONS` |
> | `PIPEDRIVE_PATCH_PRODUCTFIELDS_OPTIONS` | `PIPEDRIVE_UPDATE_PRODUCTFIELDS_OPTIONS` |
> | `PIPEDRIVE_PERFORM_A_SEARCH_FROM_MULTIPLE_ITEM_TYPES` | `PIPEDRIVE_SEARCH_MULTIPLE_ITEM_TYPES` |
> | `PIPEDRIVE_POST_DEALFIELDS_OPTIONS` | `PIPEDRIVE_ADD_DEALFIELDS_OPTIONS` |
> | `PIPEDRIVE_POST_PERSONFIELDS_OPTIONS` | `PIPEDRIVE_ADD_PERSONFIELDS_OPTIONS` |
> | `PIPEDRIVE_PRODUCTFIELDS_POST_PRODUCTFIELDS_OPTIONS` | `PIPEDRIVE_ADD_PRODUCTFIELDS_OPTIONS` |
> | `PIPEDRIVE_PRODUCTS_POST_PRODUCT_VARIATION` | `PIPEDRIVE_ADD_PRODUCT_VARIATION` |
> | `PIPEDRIVE_RECEIVES_AN_INCOMING_MESSAGE` | `PIPEDRIVE_ADD_INCOMING_MESSAGE` |
> | `PIPEDRIVE_REFRESHING_THE_TOKENS` | `PIPEDRIVE_REFRESH_TOKENS` |
> | `PIPEDRIVE_REQUESTING_AUTHORIZATION` | `PIPEDRIVE_REQUEST_AUTHORIZATION` |
> | `PIPEDRIVE_RETURNS_PROJECT_ACTIVITIES` | `PIPEDRIVE_GET_PROJECT_ACTIVITIES` |
> | `PIPEDRIVE_RETURNS_PROJECT_GROUPS` | `PIPEDRIVE_GET_PROJECT_GROUPS` |
> | `PIPEDRIVE_RETURNS_PROJECT_PLAN` | `PIPEDRIVE_GET_PROJECT_PLAN` |
> | `PIPEDRIVE_RETURNS_PROJECT_TASKS` | `PIPEDRIVE_GET_PROJECT_TASKS` |
> | `PIPEDRIVE_UPDATE_AN_INSTALLMENT_SUBSCRIPTION` | `PIPEDRIVE_UPDATE_INSTALLMENT_SUBSCRIPTION` |
> | `PIPEDRIVE_UPDATE_A_PROJECT` | `PIPEDRIVE_UPDATE_PROJECT` |
> | `PIPEDRIVE_UPDATE_A_RECURRING_SUBSCRIPTION` | `PIPEDRIVE_UPDATE_RECURRING_SUBSCRIPTION` |
> | `PIPEDRIVE_UPDATE_A_TASK` | `PIPEDRIVE_UPDATE_TASK` |
> | `PIPEDRIVE_UPDATE_A_TEAM` | `PIPEDRIVE_UPDATE_TEAM` |
> | `PIPEDRIVE_UPDATE_DEALS_DISCOUNTS` | `PIPEDRIVE_UPDATE_DEAL_DISCOUNT` |
> | `PIPEDRIVE_UPDATE_EXISTING_GOAL` | `PIPEDRIVE_UPDATE_GOAL` |
> | `PIPEDRIVE_UPDATE_MAIL_THREAD_DETAILS` | `PIPEDRIVE_UPDATE_MAIL_THREAD` |
> | `PIPEDRIVE_UPDATE_PIPELINE_VISIBILITY_FOR_A_ROLE` | `PIPEDRIVE_UPDATE_PIPELINE_VISIBILITY_FOR_ROLE` |
> | `PIPEDRIVE_UPDATE_ROLE_DETAILS` | `PIPEDRIVE_UPDATE_ROLE` |
> | `PIPEDRIVE_UPDATE_THE_PRODUCT_ATTACHED_TO_A_DEAL` | `PIPEDRIVE_UPDATE_DEAL_PRODUCT_ATTACHMENT` |

> [accordion] Shopify (132 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `SHOPIFY_ADDS_A_PRODUCT_TO_A_CUSTOM_COLLECTION` | `SHOPIFY_ADD_PRODUCT_TO_CUSTOM_COLLECTION` |
> | `SHOPIFY_APPROVES_A_COMMENT` | `SHOPIFY_APPROVE_COMMENT` |
> | `SHOPIFY_CANCEL_AN_ORDER` | `SHOPIFY_CANCEL_ORDER` |
> | `SHOPIFY_CANCEL_A_FULFILLMENT_ORDER` | `SHOPIFY_CANCEL_FULFILLMENT_ORDER` |
> | `SHOPIFY_CLOSE_AN_ORDER` | `SHOPIFY_CLOSE_ORDER` |
> | `SHOPIFY_COMPLETE_A_DRAFT_ORDER` | `SHOPIFY_COMPLETE_DRAFT_ORDER` |
> | `SHOPIFY_COUNT_ALL_THE_EVENTS` | `SHOPIFY_COUNT_EVENTS` |
> | `SHOPIFY_COUNT_ARTICLE` | `SHOPIFY_COUNT_ARTICLES` |
> | `SHOPIFY_COUNT_FULFILLMENT` | `SHOPIFY_COUNT_FULFILLMENTS` |
> | `SHOPIFY_COUNT_METAFIELD` | `SHOPIFY_COUNT_METAFIELDS` |
> | `SHOPIFY_COUNT_PRICERULE` | `SHOPIFY_COUNT_PRICE_RULES` |
> | `SHOPIFY_COUNT_SCRIPTTAG` | `SHOPIFY_COUNT_SCRIPT_TAGS` |
> | `SHOPIFY_CREATES_A_DISCOUNT_CODE` | `SHOPIFY_CREATE_DISCOUNT_CODE` |
> | `SHOPIFY_CREATES_A_MARKETING_EVENT` | `SHOPIFY_CREATE_MARKETING_EVENT` |
> | `SHOPIFY_CREATES_MARKETING_ENGAGEMENTS_ON_A_MARKETING_EVENT` | `SHOPIFY_CREATE_MARKETING_ENGAGEMENTS` |
> | `SHOPIFY_CREATE_A_NEW_BLOG` | `SHOPIFY_CREATE_BLOG` |
> | `SHOPIFY_CREATE_A_NEW_DRAFTORDER` | `SHOPIFY_CREATE_DRAFT_ORDER` |
> | `SHOPIFY_CREATE_A_NEW_PAGE` | `SHOPIFY_CREATE_PAGE` |
> | `SHOPIFY_CREATE_A_NEW_PRODUCT_VARIANT` | `SHOPIFY_CREATE_PRODUCT_VARIANT` |
> | `SHOPIFY_CREATE_COMMENT_FOR_ARTICLE` | `SHOPIFY_CREATE_ARTICLE_COMMENT` |
> | `SHOPIFY_CREATE_COUNTRIES` | `SHOPIFY_CREATE_COUNTRY` |
> | `SHOPIFY_CREATE_GIFT_CARDS` | `SHOPIFY_CREATE_GIFT_CARD` |
> | `SHOPIFY_CREATE_INVENTORY_LEVELS_ADJUST` | `SHOPIFY_ADJUST_INVENTORY_LEVEL` |
> | `SHOPIFY_CREATE_INVENTORY_LEVELS_CONNECT` | `SHOPIFY_CONNECT_INVENTORY_LEVEL` |
> | `SHOPIFY_CREATE_INVENTORY_LEVELS_SET` | `SHOPIFY_SET_INVENTORY_LEVEL` |
> | `SHOPIFY_CREATE_ORDERS_PARAM_ORDER_ID_REFUNDS` | `SHOPIFY_CREATE_REFUND` |
> | `SHOPIFY_CREATE_PRICE_RULES_PARAM_PRICE_RULE_ID_BATCH` | `SHOPIFY_CREATE_DISCOUNT_CODE_BATCH` |
> | `SHOPIFY_CREATE_REDIRECTS` | `SHOPIFY_CREATE_REDIRECT` |
> | `SHOPIFY_CREATE_SCRIPTTAG` | `SHOPIFY_CREATE_SCRIPT_TAG` |
> | `SHOPIFY_CREATE_STOREFRONT_ACCESS_TOKENS` | `SHOPIFY_CREATE_STOREFRONT_ACCESS_TOKEN` |
> | `SHOPIFY_CREATE_THEMES` | `SHOPIFY_CREATE_THEME` |
> | `SHOPIFY_CREATE_TRANSACTION_FOR_ORDER` | `SHOPIFY_CREATE_ORDER_TRANSACTION` |
> | `SHOPIFY_DELETES_AN_ASSET_FROM_A_THEME` | `SHOPIFY_DELETE_THEME_ASSET` |
> | `SHOPIFY_DELETES_A_CUSTOMER` | `SHOPIFY_DELETE_CUSTOMER` |
> | `SHOPIFY_DELETES_A_MARKETING_EVENT` | `SHOPIFY_DELETE_MARKETING_EVENT` |
> | `SHOPIFY_DELETE_A_METAFIELD_BY_ITS_ID` | `SHOPIFY_DELETE_METAFIELD` |
> | `SHOPIFY_DELETE_COUNTRIES_PARAM_COUNTRY_ID` | `SHOPIFY_DELETE_COUNTRY` |
> | `SHOPIFY_DELETE_INVENTORY_LEVELS` | `SHOPIFY_DELETE_INVENTORY_LEVEL` |
> | `SHOPIFY_DELETE_METAFIELDS_BULK` | `SHOPIFY_BULK_DELETE_METAFIELDS` |
> | `SHOPIFY_DELETE_METAOBJECTS` | `SHOPIFY_BULK_DELETE_METAOBJECTS` |
> | `SHOPIFY_DELETE_REDIRECTS_PARAM_REDIRECT_ID` | `SHOPIFY_DELETE_REDIRECT` |
> | `SHOPIFY_DELETE_THEMES_PARAM_THEME_ID` | `SHOPIFY_DELETE_THEME` |
> | `SHOPIFY_DELETE_WEBHOOKS_PARAM_WEBHOOK_ID` | `SHOPIFY_DELETE_WEBHOOK` |
> | `SHOPIFY_DEL_ORDER_RISK` | `SHOPIFY_DELETE_ORDER_RISK` |
> | `SHOPIFY_DISABLES_A_GIFT_CARD` | `SHOPIFY_DISABLE_GIFT_CARD` |
> | `SHOPIFY_GET_A_LIST_OF_ACCESS_SCOPES` | `SHOPIFY_GET_ACCESS_SCOPES` |
> | `SHOPIFY_GET_COUNTRIES_PARAM_COUNTRY_ID_PROVINCES` | `SHOPIFY_GET_COUNTRY_PROVINCES` |
> | `SHOPIFY_GET_COUNT_OF_COMMENTS` | `SHOPIFY_GET_COMMENTS_COUNT` |
> | `SHOPIFY_GET_CUSTOMERS_PARAM_CUSTOMER_ID_ADDRESSES` | `SHOPIFY_GET_CUSTOMER_ADDRESSES` |
> | `SHOPIFY_GET_EVENTS_PARAM_EVENT_ID` | `SHOPIFY_GET_EVENT` |
> | `SHOPIFY_GET_FULFILLMENT_ORDERS_PARAM_FULFILLMENT_ORDER_ID` | `SHOPIFY_GET_FULFILLMENT_ORDER_MOVE_LOCATIONS` |
> | `SHOPIFY_GET_GIFT_CARDS_SEARCH` | `SHOPIFY_SEARCHES_FOR_GIFT_CARDS` |
> | `SHOPIFY_GET_METAFIELDS_PARAM_METAFIELD_ID` | `SHOPIFY_GET_METAFIELD_BY_ID` |
> | `SHOPIFY_GET_ORDERS_PARAM_ORDER_ID_REFUNDS` | `SHOPIFY_GET_ORDER_REFUNDS` |
> | `SHOPIFY_GET_ORDERS_PARAM_ORDER_ID_REFUNDS_PARAM_REFUND_ID` | `SHOPIFY_GET_ORDER_REFUND_BY_ID` |
> | `SHOPIFY_GET_PRICE_RULES_PARAM_PRICE_RULE_ID_BATCH_PARAM` | `SHOPIFY_GET_PRICE_RULE_BATCH_INFO` |
> | `SHOPIFY_GET_PRICE_RULES_PARAM_PRICE_RULE_ID_DISCOUNT_CODES` | `SHOPIFY_GET_PRICE_RULE_DISCOUNT_CODES` |
> | `SHOPIFY_GET_PROVINCES_COUNT_FOR_COUNTRY` | `SHOPIFY_GET_COUNTRIES_PARAM_COUNTRY_ID_PROVINCES_COUNT` |
> | `SHOPIFY_GET_REDIRECTS_PARAM_REDIRECT_ID` | `SHOPIFY_GET_REDIRECT_BY_ID` |
> | `SHOPIFY_LIST_LOCATION` | `SHOPIFY_LIST_LOCATIONS` |
> | `SHOPIFY_MODIFY_AN_EXISTING_BLOG` | `SHOPIFY_UPDATE_BLOG` |
> | `SHOPIFY_MODIFY_AN_EXISTING_DRAFTORDER` | `SHOPIFY_UPDATE_DRAFT_ORDER` |
> | `SHOPIFY_MODIFY_AN_EXISTING_THEME` | `SHOPIFY_UPDATE_THEME` |
> | `SHOPIFY_PERFORMS_BULK_OPERATIONS_MULTIPLE_CUSTOMER_ADDRESSES` | `SHOPIFY_BULK_DELETE_CUSTOMER_ADDRESSES` |
> | `SHOPIFY_RECEIVE_A_COUNT_OF_ALL_BLOGS` | `SHOPIFY_COUNT_BLOGS` |
> | `SHOPIFY_RECEIVE_A_COUNT_OF_ALL_DRAFTORDERS` | `SHOPIFY_COUNT_DRAFT_ORDERS` |
> | `SHOPIFY_RECEIVE_A_COUNT_OF_ALL_WEBHOOKS` | `SHOPIFY_COUNT_WEBHOOKS` |
> | `SHOPIFY_RECEIVE_A_LIST_OF_ALL_COUNTRIES` | `SHOPIFY_LIST_COUNTRIES` |
> | `SHOPIFY_RECEIVE_A_LIST_OF_ALL_PRODUCT_IMAGES` | `SHOPIFY_LIST_PRODUCT_IMAGES` |
> | `SHOPIFY_RECEIVE_A_LIST_OF_ALL_RESOURCEFEEDBACKS` | `SHOPIFY_LIST_RESOURCE_FEEDBACKS` |
> | `SHOPIFY_RECEIVE_A_SINGLE_BLOG` | `SHOPIFY_GET_BLOG` |
> | `SHOPIFY_RECEIVE_A_SINGLE_DRAFTORDER` | `SHOPIFY_GET_DRAFT_ORDER` |
> | `SHOPIFY_RECEIVE_A_SINGLE_PRODUCT_VARIANT` | `SHOPIFY_GET_PRODUCT_VARIANT` |
> | `SHOPIFY_REMOVES_A_COMMENT` | `SHOPIFY_DELETE_COMMENT` |
> | `SHOPIFY_REMOVE_AN_EXISTING_BLOG` | `SHOPIFY_DELETE_BLOG` |
> | `SHOPIFY_REMOVE_AN_EXISTING_DRAFTORDER` | `SHOPIFY_DELETE_DRAFT_ORDER` |
> | `SHOPIFY_REMOVE_AN_EXISTING_FULFILLMENTSERVICE` | `SHOPIFY_DELETE_FULFILLMENT_SERVICE` |
> | `SHOPIFY_REMOVE_PRODUCT_FROM_COLLECTION` | `SHOPIFY_DELETE_COLLECT` |
> | `SHOPIFY_REMOVE_PRODUCT_VARIANT` | `SHOPIFY_DELETE_PRODUCT_VARIANT` |
> | `SHOPIFY_RETRIEVES_ALL_APPLICATION_CREDITS` | `SHOPIFY_LIST_APPLICATION_CREDITS` |
> | `SHOPIFY_RETRIEVES_ALL_ORDERS_BELONGING_TO_A_CUSTOMER` | `SHOPIFY_LIST_CUSTOMER_ORDERS` |
> | `SHOPIFY_RETRIEVES_A_COUNT_OF_CUSTOM_COLLECTIONS` | `SHOPIFY_COUNT_CUSTOM_COLLECTIONS` |
> | `SHOPIFY_RETRIEVES_A_COUNT_OF_GIFT_CARDS` | `SHOPIFY_GET_GIFT_CARDS_COUNT` |
> | `SHOPIFY_RETRIEVES_A_COUNT_OF_LOCATIONS` | `SHOPIFY_COUNT_LOCATION` |
> | `SHOPIFY_RETRIEVES_A_COUNT_OF_PRODUCTS` | `SHOPIFY_COUNT_PRODUCTS` |
> | `SHOPIFY_RETRIEVES_A_DISCOUNT_CODE_CREATION_JOB` | `SHOPIFY_GET_DISCOUNT_CODE_BATCH_JOB` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_ALL_ARTICLES_FROM_A_BLOG` | `SHOPIFY_LIST_BLOG_ARTICLES` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_ALL_MARKETING_EVENTS` | `SHOPIFY_LIST_MARKETING_EVENTS` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_ALL_SCRIPT_TAGS` | `SHOPIFY_LIST_SCRIPT_TAGS` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_ASSETS_FOR_A_THEME` | `SHOPIFY_LIST_THEME_ASSETS` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_COLLECTS` | `SHOPIFY_LIST_COLLECTS` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_COMMENTS` | `SHOPIFY_LIST_COMMENTS` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_CURRENCIES_ENABLED_ON_A_SHOP` | `SHOPIFY_LIST_CURRENCIES` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_CUSTOMERS` | `SHOPIFY_LIST_CUSTOMERS` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_CUSTOM_COLLECTIONS` | `SHOPIFY_LIST_CUSTOM_COLLECTIONS` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_DRAFT_ORDERS` | `SHOPIFY_LIST_DRAFT_ORDERS` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_GIFT_CARDS` | `SHOPIFY_GET_GIFT_CARDS` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_INVENTORY_LEVELS` | `SHOPIFY_LIST_INVENTORY_LEVELS` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_ORDERS` | `SHOPIFY_LIST_ORDERS` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_PAGES` | `SHOPIFY_LIST_PAGES` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_PRODUCT_VARIANTS` | `SHOPIFY_LIST_PRODUCT_VARIANTS` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_REFUNDS_FOR_AN_ORDER` | `SHOPIFY_LIST_ORDER_REFUNDS` |
> | `SHOPIFY_RETRIEVES_A_LIST_OF_TRANSACTIONS` | `SHOPIFY_LIST_TRANSACTIONS` |
> | `SHOPIFY_RETRIEVES_A_PAGE_COUNT` | `SHOPIFY_COUNT_PAGES` |
> | `SHOPIFY_RETRIEVES_A_SINGLE_CUSTOMER` | `SHOPIFY_GET_CUSTOMER` |
> | `SHOPIFY_RETRIEVES_A_SINGLE_PROVINCE_FOR_A_COUNTRY` | `SHOPIFY_GET_COUNTRIES_PARAM_COUNTRY_ID_PROVINCES_PARAM_PROVI` |
> | `SHOPIFY_RETRIEVES_A_SINGLE_REDIRECT` | `SHOPIFY_GET_REDIRECT` |
> | `SHOPIFY_RETRIEVES_A_SINGLE_SMART_COLLECTION` | `SHOPIFY_GET_SMART_COLLECTION` |
> | `SHOPIFY_RETRIEVES_A_SINGLE_THEME` | `SHOPIFY_GET_THEME` |
> | `SHOPIFY_RETRIEVES_A_SPECIFIC_REFUND` | `SHOPIFY_GET_REFUND` |
> | `SHOPIFY_RETRIEVES_A_SPECIFIC_TRANSACTION` | `SHOPIFY_GET_TRANSACTION` |
> | `SHOPIFY_RETRIEVES_FULFILLMENTS_ASSOCIATED_FULFILLMENT_ORDER` | `SHOPIFY_GET_FULFILLMENT_ORDER_FULFILLMENTS` |
> | `SHOPIFY_RETRIEVES_FULFILLMENTS_ASSOCIATED_WITH_AN_ORDER` | `SHOPIFY_GET_ORDER_FULFILLMENTS` |
> | `SHOPIFY_RETRIEVE_A_LIST_OF_ALL_BLOGS` | `SHOPIFY_LIST_BLOGS` |
> | `SHOPIFY_RETRIEVE_LIST_PRODUCTS_BELONGING_COLLECTION` | `SHOPIFY_LIST_COLLECTION_PRODUCTS` |
> | `SHOPIFY_SENDS_AN_ACCOUNT_INVITE_TO_A_CUSTOMER` | `SHOPIFY_SEND_CUSTOMER_ACCOUNT_INVITE` |
> | `SHOPIFY_SEND_AN_INVOICE` | `SHOPIFY_SEND_INVOICE` |
> | `SHOPIFY_SHOP_RETRIEVE_A_SPECIFIC_METAFIELD` | `SHOPIFY_GET_SHOP_METAFIELD` |
> | `SHOPIFY_SHOP_RETRIEVE_LIST_METAFIELDS_RESOURCE_S_ENDPOINT` | `SHOPIFY_GET_SHOP_METAFIELDS` |
> | `SHOPIFY_SHOP_UPDATES_A_METAFIELD` | `SHOPIFY_UPDATE_SHOP_METAFIELD` |
> | `SHOPIFY_UPDATES_AN_EXISTING_PROVINCE_FOR_A_COUNTRY` | `SHOPIFY_UPDATE_PROVINCE` |
> | `SHOPIFY_UPDATES_AN_EXISTING_REDIRECT` | `SHOPIFY_UPDATE_REDIRECT_ALT` |
> | `SHOPIFY_UPDATES_A_CUSTOMER` | `SHOPIFY_UPDATE_CUSTOMER` |
> | `SHOPIFY_UPDATES_A_MARKETING_EVENT` | `SHOPIFY_UPDATE_MARKETING_EVENT` |
> | `SHOPIFY_UPDATES_A_METAFIELD` | `SHOPIFY_UPDATE_METAFIELD_GENERIC` |
> | `SHOPIFY_UPDATES_A_METAFIELD2` | `SHOPIFY_UPDATE_METAFIELD_RESOURCE` |
> | `SHOPIFY_UPDATE_AN_EXISTING_GIFT_CARD` | `SHOPIFY_UPDATE_GIFT_CARD` |
> | `SHOPIFY_UPDATE_COUNTRIES_PARAM_COUNTRY_ID_PROVINCES_PARAM` | `SHOPIFY_UPDATE_COUNTRIES_PARAM_COUNTRY_ID_PROVINCES_PARAM_PR` |
> | `SHOPIFY_UPDATE_METAFIELDS_PARAM_METAFIELD_ID` | `SHOPIFY_UPDATE_METAFIELD_BY_ID` |
> | `SHOPIFY_UPDATE_REDIRECTS_PARAM_REDIRECT_ID` | `SHOPIFY_UPDATE_REDIRECT` |
> | `SHOPIFY_UPDATE_SCRIPTTAG` | `SHOPIFY_UPDATE_SCRIPT_TAG` |
> | `SHOPIFY_UPDATE_SMART_COLLECTIONS_PARAM_SMART_COLLECTION_ID` | `SHOPIFY_UPDATE_SMART_COLLECTION_ALT` |

> [accordion] Outlook (70 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `OUTLOOK_CANCEL_USER_CALENDAR_EVENT` | `OUTLOOK_CANCEL_CALENDAR_EVENT` |
> | `OUTLOOK_CANCEL_USER_CALENDAR_GROUP_EVENT` | `OUTLOOK_CANCEL_CALENDAR_GROUP_CALENDAR_EVENT` |
> | `OUTLOOK_CANCEL_USER_EVENT` | `OUTLOOK_CANCEL_EVENT` |
> | `OUTLOOK_COPY_USER_MAIL_FOLDER` | `OUTLOOK_COPY_MAIL_FOLDER` |
> | `OUTLOOK_COPY_USER_MESSAGE_FROM_MAIL_FOLDER` | `OUTLOOK_COPY_MESSAGE_FROM_MAIL_FOLDER` |
> | `OUTLOOK_CREATE_CONTACT_IN_CHILD_FOLDER` | `OUTLOOK_CREATE_ME_CONTACT_IN_CHILD_FOLDER` |
> | `OUTLOOK_CREATE_REPLY_DRAFT` | `OUTLOOK_CREATE_ME_REPLY_DRAFT` |
> | `OUTLOOK_CREATE_USER_CALENDAR_CALENDAR_EVENT` | `OUTLOOK_CREATE_CALENDAR_EVENT_IN_CALENDAR` |
> | `OUTLOOK_CREATE_USER_CALENDAR_EVENT` | `OUTLOOK_CREATE_ME_EVENT` |
> | `OUTLOOK_CREATE_USER_CALENDAR_EVENT_EXTENSION` | `OUTLOOK_CREATE_ME_CALENDAR_EVENT_EXTENSION` |
> | `OUTLOOK_CREATE_USER_CALENDAR_GROUP_EVENT_ATTACHMENT` | `OUTLOOK_CREATE_CALENDAR_GROUP_CALENDAR_EVENT_ATTACHMENT` |
> | `OUTLOOK_CREATE_USER_CALENDAR_PERMISSION2` | `OUTLOOK_CREATE_ME_CALENDAR_PERMISSION` |
> | `OUTLOOK_CREATE_USER_CHILD_FOLDER_MESSAGE` | `OUTLOOK_CREATE_ME_CHILD_FOLDER_MESSAGE` |
> | `OUTLOOK_CREATE_USER_CHILD_FOLDER_MESSAGE_REPLY_ALL_DRAFT` | `OUTLOOK_CREATE_ME_REPLY_ALL_DRAFT` |
> | `OUTLOOK_CREATE_USER_CONTACT_FOLDERS_CONTACTS_EXTENSIONS` | `OUTLOOK_CREATE_ME_CONTACT_FOLDERS_CONTACTS_EXTENSIONS` |
> | `OUTLOOK_CREATE_USER_CONTACT_FOLDER_CHILD_FOLDER` | `OUTLOOK_CREATE_CONTACT_FOLDER_CHILD_FOLDER` |
> | `OUTLOOK_CREATE_USER_CONTACT_FOLDER_CONTACT` | `OUTLOOK_CREATE_ME_CONTACT_FOLDERS_CONTACTS` |
> | `OUTLOOK_CREATE_USER_EVENT_ATTACHMENT` | `OUTLOOK_CREATE_EVENT_ATTACHMENT` |
> | `OUTLOOK_CREATE_USER_FORWARD_DRAFT` | `OUTLOOK_CREATE_ME_FORWARD_DRAFT` |
> | `OUTLOOK_CREATE_USER_INFERENCE_CLASSIFICATION_OVERRIDE` | `OUTLOOK_CREATE_ME_INFERENCE_CLASSIFICATION_OVERRIDE` |
> | `OUTLOOK_CREATE_USER_MAIL_FOLDER_MESSAGE_FORWARD_DRAFT` | `OUTLOOK_CREATE_FORWARD_DRAFT` |
> | `OUTLOOK_CREATE_USER_MAIL_FOLDER_MESSAGE_RULE` | `OUTLOOK_CREATE_MAIL_FOLDER_MESSAGE_RULE` |
> | `OUTLOOK_CREATE_USER_MESSAGE_REPLY_ALL_DRAFT` | `OUTLOOK_CREATE_ME_MESSAGE_REPLY_ALL_DRAFT` |
> | `OUTLOOK_DELETE_CONTACT_EXTENSION` | `OUTLOOK_DELETE_ME_CONTACT_EXTENSION` |
> | `OUTLOOK_DELETE_INFERENCE_CLASSIFICATION_OVERRIDE` | `OUTLOOK_DELETE_ME_INFERENCE_CLASSIFICATION_OVERRIDE` |
> | `OUTLOOK_DELETE_MAIL_FOLDER_CHILD_FOLDER` | `OUTLOOK_DELETE_ME_MAIL_FOLDER_CHILD_FOLDER` |
> | `OUTLOOK_DELETE_MAIL_FOLDER_MESSAGE_RULE` | `OUTLOOK_DELETE_ME_MAIL_FOLDER_MESSAGE_RULE` |
> | `OUTLOOK_DELETE_USER_CALENDARS_CALENDAR_PERMISSION` | `OUTLOOK_DELETE_ME_CALENDAR_PERMISSION` |
> | `OUTLOOK_DELETE_USER_CALENDAR_EVENT_ATTACHMENT` | `OUTLOOK_DELETE_CALENDAR_EVENT_ATTACHMENT` |
> | `OUTLOOK_DELETE_USER_CALENDAR_GROUP_CALENDAR` | `OUTLOOK_DELETE_CALENDAR_FROM_GROUP` |
> | `OUTLOOK_DELETE_USER_CALENDAR_GROUP_CALENDAR_EVENT` | `OUTLOOK_DELETE_CALENDAR_GROUP_CALENDAR_EVENT` |
> | `OUTLOOK_DELETE_USER_CALENDAR_GROUP_CALENDAR_PERMISSION` | `OUTLOOK_DELETE_CALENDAR_PERMISSION` |
> | `OUTLOOK_DELETE_USER_CALENDAR_PERMISSION` | `OUTLOOK_DELETE_PRIMARY_CALENDAR_PERMISSION` |
> | `OUTLOOK_DELETE_USER_CONTACT_FOLDER_CHILD_FOLDER` | `OUTLOOK_DELETE_CONTACT_FOLDER_CHILD_FOLDER` |
> | `OUTLOOK_DELETE_USER_CONTACT_FOLDER_CONTACT_EXTENSION` | `OUTLOOK_DELETE_ME_CONTACT_FOLDER_CONTACT_EXTENSION` |
> | `OUTLOOK_DELETE_USER_CONTACT_FROM_CHILD_FOLDER_PERMANENTLY` | `OUTLOOK_DELETE_CONTACT_FROM_CHILD_FOLDER_PERMANENTLY` |
> | `OUTLOOK_DELETE_USER_EVENT_ATTACHMENT` | `OUTLOOK_DELETE_ME_EVENTS_ATTACHMENTS` |
> | `OUTLOOK_DELETE_USER_EVENT_EXTENSION` | `OUTLOOK_DELETE_ME_EVENT_EXTENSION` |
> | `OUTLOOK_DELETE_USER_MAIL_FOLDERS_CHILD_FOLDERS_MESSAGES_EXTENSIONS` | `OUTLOOK_DELETE_ME_MAIL_FOLDERS_CHILD_FOLDERS_MESSAGES_EXTENS` |
> | `OUTLOOK_DISMISS_USER_CALENDAR_EVENT_REMINDER` | `OUTLOOK_DISMISS_CALENDAR_EVENT_REMINDER` |
> | `OUTLOOK_DISMISS_USER_CALENDAR_GROUP_EVENT_REMINDER` | `OUTLOOK_DISMISS_EVENT_REMINDER_FROM_GROUP` |
> | `OUTLOOK_GET_CONTACT` | `OUTLOOK_GET_ME_CONTACTS` |
> | `OUTLOOK_GET_EVENT_CALENDAR` | `OUTLOOK_GET_ME_EVENT_CALENDAR` |
> | `OUTLOOK_GET_OUTLOOK_SUPPORTED_TIME_ZONES` | `OUTLOOK_GET_SUPPORTED_TIME_ZONES` |
> | `OUTLOOK_GET_USER_CALENDAR_GROUP_SCHEDULE` | `OUTLOOK_GET_CALENDAR_GROUP_SCHEDULE` |
> | `OUTLOOK_GET_USER_CALENDAR_PERMISSION` | `OUTLOOK_GET_CALENDAR_PERMISSION` |
> | `OUTLOOK_GET_USER_CALENDAR_PERMISSION2` | `OUTLOOK_GET_CALENDAR_PERMISSION_FROM_CALENDAR` |
> | `OUTLOOK_GET_USER_CONTACT_EXTENSION` | `OUTLOOK_GET_ME_CONTACTS_EXTENSIONS` |
> | `OUTLOOK_GET_USER_CONTACT_FOLDER_CHILD_FOLDER` | `OUTLOOK_GET_ME_CONTACT_FOLDERS_CHILD_FOLDER` |
> | `OUTLOOK_GET_USER_EVENT_ATTACHMENT` | `OUTLOOK_GET_ME_EVENT_ATTACHMENT` |
> | `OUTLOOK_GET_USER_MAIL_FOLDER_MESSAGE_RULE` | `OUTLOOK_GET_MAIL_FOLDER_MESSAGE_RULE` |
> | `OUTLOOK_GET_USER_MESSAGES_EXTENSIONS` | `OUTLOOK_GET_ME_MAIL_FOLDERS_MESSAGES_EXTENSIONS` |
> | `OUTLOOK_GET_USER_MESSAGE_EXTENSION` | `OUTLOOK_GET_MESSAGE_EXTENSION` |
> | `OUTLOOK_GET_USER_OUTLOOK` | `OUTLOOK_GET_ME_OUTLOOK` |
> | `OUTLOOK_LIST_USER_CALENDARS_CALENDAR_PERMISSIONS2` | `OUTLOOK_LIST_USER_CALENDARS_CALENDAR_PERMISSIONS` |
> | `OUTLOOK_LIST_USER_CALENDAR_EVENT_ATTACHMENTS` | `OUTLOOK_LIST_CALENDAR_EVENT_ATTACHMENTS` |
> | `OUTLOOK_LIST_USER_CALENDAR_GROUP_CALENDAR_EVENTS` | `OUTLOOK_LIST_CALENDAR_GROUP_CALENDAR_EVENTS` |
> | `OUTLOOK_LIST_USER_CALENDAR_GROUP_EVENT_ATTACHMENTS` | `OUTLOOK_LIST_CALENDAR_GROUP_EVENT_ATTACHMENTS` |
> | `OUTLOOK_LIST_USER_CALENDAR_PERMISSIONS` | `OUTLOOK_LIST_ME_CALENDAR_PERMISSIONS` |
> | `OUTLOOK_LIST_USER_CHILD_FOLDER_CONTACTS` | `OUTLOOK_LIST_CHILD_FOLDER_CONTACTS` |
> | `OUTLOOK_LIST_USER_CONTACT_FOLDERS` | `OUTLOOK_GET_CONTACT_FOLDERS` |
> | `OUTLOOK_MOVE_CHILD_MAIL_FOLDER` | `OUTLOOK_MOVE_ME_MAIL_FOLDER` |
> | `OUTLOOK_SNOOZE_USER_CALENDAR_EVENT_REMINDER3` | `OUTLOOK_SNOOZE_USER_CALENDAR_EVENT_REMINDER` |
> | `OUTLOOK_SNOOZE_USER_CALENDAR_GROUP_EVENT_REMINDER` | `OUTLOOK_SNOOZE_CALENDAR_GROUP_EVENT_REMINDER` |
> | `OUTLOOK_UPDATE_USER_CALENDAR_EVENT2` | `OUTLOOK_UPDATE_USER_CALENDAR_CALENDAR_EVENT` |
> | `OUTLOOK_UPDATE_USER_CALENDAR_GROUPS_CALENDARS` | `OUTLOOK_UPDATE_CALENDAR_GROUPS_CALENDARS` |
> | `OUTLOOK_UPDATE_USER_CALENDAR_GROUP_EVENT` | `OUTLOOK_UPDATE_CALENDAR_GROUPS_CALENDARS_EVENTS` |
> | `OUTLOOK_UPDATE_USER_CONTACTS_EXTENSIONS3` | `OUTLOOK_UPDATE_USER_CONTACTS_EXTENSIONS_DIRECT` |
> | `OUTLOOK_UPDATE_USER_CONTACT_FOLDER` | `OUTLOOK_UPDATE_CONTACT_FOLDER` |
> | `OUTLOOK_UPDATE_USER_CONTACT_FOLDER_CHILD_FOLDER` | `OUTLOOK_UPDATE_CONTACT_FOLDER_CHILD_FOLDER` |

> [accordion] Supabase (65 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `SUPABASE_ALPHA_CREATES_A_NEW_API_KEY_FOR_THE_PROJECT` | `SUPABASE_ALPHA_CREATE_API_KEY` |
> | `SUPABASE_ALPHA_DELETES_AN_API_KEY_FOR_THE_PROJECT` | `SUPABASE_ALPHA_DELETE_API_KEY` |
> | `SUPABASE_ALPHA_GET_A_THIRD_PARTY_INTEGRATION` | `SUPABASE_ALPHA_GET_THIRD_PARTY_INTEGRATION` |
> | `SUPABASE_ALPHA_LISTS_ALL_THIRD_PARTY_AUTH_INTEGRATIONS` | `SUPABASE_ALPHA_LIST_THIRD_PARTY_AUTH_INTEGRATIONS` |
> | `SUPABASE_ALPHA_REMOVES_A_THIRD_PARTY_AUTH_INTEGRATION` | `SUPABASE_ALPHA_DELETE_THIRD_PARTY_AUTH_INTEGRATION` |
> | `SUPABASE_ALPHA_UPDATES_AN_API_KEY_FOR_THE_PROJECT` | `SUPABASE_ALPHA_UPDATE_API_KEY` |
> | `SUPABASE_BETA_ACTIVATES_A_CUSTOM_HOSTNAME_FOR_A_PROJECT` | `SUPABASE_BETA_ACTIVATE_CUSTOM_HOSTNAME` |
> | `SUPABASE_BETA_ACTIVATES_A_VANITY_SUBDOMAIN_FOR_A_PROJECT` | `SUPABASE_BETA_ACTIVATE_VANITY_SUBDOMAIN` |
> | `SUPABASE_BETA_CHECKS_VANITY_SUBDOMAIN_AVAILABILITY` | `SUPABASE_BETA_CHECK_VANITY_SUBDOMAIN_AVAILABILITY` |
> | `SUPABASE_BETA_ENABLES_DATABASE_WEBHOOKS_ON_THE_PROJECT` | `SUPABASE_BETA_ENABLE_DATABASE_WEBHOOKS` |
> | `SUPABASE_BETA_GETS_CURRENT_VANITY_SUBDOMAIN_CONFIG` | `SUPABASE_BETA_GET_VANITY_SUBDOMAIN_CONFIG` |
> | `SUPABASE_BETA_GETS_PROJECT_S_CUSTOM_HOSTNAME_CONFIG` | `SUPABASE_BETA_GET_PROJECT_CUSTOM_HOSTNAME_CONFIG` |
> | `SUPABASE_BETA_GETS_PROJECT_S_NETWORK_BANS` | `SUPABASE_BETA_GET_PROJECT_NETWORK_BANS` |
> | `SUPABASE_BETA_GETS_PROJECT_S_NETWORK_RESTRICTIONS` | `SUPABASE_BETA_GET_PROJECT_NETWORK_RESTRICTIONS` |
> | `SUPABASE_BETA_GETS_PROJECT_S_PGSODIUM_CONFIG` | `SUPABASE_BETA_GET_PROJECT_PGSODIUM_CONFIG` |
> | `SUPABASE_BETA_GET_PROJECT_S_SSL_ENFORCEMENT_CONFIGURATION` | `SUPABASE_BETA_GET_PROJECT_SSL_ENFORCEMENT_CONFIG` |
> | `SUPABASE_BETA_REMOVE_A_READ_REPLICA` | `SUPABASE_BETA_REMOVE_READ_REPLICA` |
> | `SUPABASE_BETA_SET_UP_A_READ_REPLICA` | `SUPABASE_BETA_CREATE_READ_REPLICA` |
> | `SUPABASE_BETA_UPDATES_PROJECT_S_NETWORK_RESTRICTIONS` | `SUPABASE_BETA_UPDATE_PROJECT_NETWORK_RESTRICTIONS` |
> | `SUPABASE_BETA_UPGRADES_THE_PROJECT_S_POSTGRES_VERSION` | `SUPABASE_BETA_UPGRADE_PROJECT_POSTGRES_VERSION` |
> | `SUPABASE_CONFIG_PGSODIUM_UPDATE_WITH_ROOT_KEY_WARNING` | `SUPABASE_UPDATE_PGSODIUM_CONFIG` |
> | `SUPABASE_CREATES_A_NEW_SSO_PROVIDER` | `SUPABASE_CREATE_SSO_PROVIDER` |
> | `SUPABASE_CREATES_A_NEW_THIRD_PARTY_AUTH_INTEGRATION` | `SUPABASE_CREATE_THIRD_PARTY_AUTH_INTEGRATION` |
> | `SUPABASE_CREATE_AN_ORGANIZATION` | `SUPABASE_CREATE_ORGANIZATION` |
> | `SUPABASE_CREATE_A_DATABASE_BRANCH` | `SUPABASE_CREATE_DATABASE_BRANCH` |
> | `SUPABASE_CREATE_A_FUNCTION` | `SUPABASE_CREATE_FUNCTION` |
> | `SUPABASE_CUSTOM_HOSTNAME_DNS_VERIFICATION` | `SUPABASE_VERIFY_CUSTOM_HOSTNAME_DNS` |
> | `SUPABASE_DELETES_THE_GIVEN_PROJECT` | `SUPABASE_DELETE_PROJECT` |
> | `SUPABASE_DELETE_A_DATABASE_BRANCH` | `SUPABASE_DELETE_DATABASE_BRANCH` |
> | `SUPABASE_DELETE_A_FUNCTION` | `SUPABASE_DELETE_FUNCTION` |
> | `SUPABASE_DISABLES_PREVIEW_BRANCHING` | `SUPABASE_DISABLE_PREVIEW_BRANCHING` |
> | `SUPABASE_EXCHANGE_O_AUTH_TOKEN` | `SUPABASE_EXCHANGE_OAUTH_TOKEN` |
> | `SUPABASE_GENERATE_TYPE_SCRIPT_TYPES` | `SUPABASE_GENERATE_TYPESCRIPT_TYPES` |
> | `SUPABASE_GETS_A_SPECIFIC_SQL_SNIPPET` | `SUPABASE_GET_SQL_SNIPPET` |
> | `SUPABASE_GETS_A_SSO_PROVIDER_BY_ITS_UUID` | `SUPABASE_GET_SSO_PROVIDER` |
> | `SUPABASE_GETS_INFORMATION_ABOUT_THE_ORGANIZATION` | `SUPABASE_GET_ORGANIZATION` |
> | `SUPABASE_GETS_PROJECT_S_POSTGREST_CONFIG` | `SUPABASE_GET_PROJECT_POSTGREST_CONFIG` |
> | `SUPABASE_GETS_PROJECT_S_POSTGRES_CONFIG` | `SUPABASE_GET_PROJECT_POSTGRES_CONFIG` |
> | `SUPABASE_GETS_PROJECT_S_SUPAVISOR_CONFIG` | `SUPABASE_GET_PROJECT_SUPAVISOR_CONFIG` |
> | `SUPABASE_GET_A_BRANCH` | `SUPABASE_GET_BRANCH` |
> | `SUPABASE_GET_A_MIGRATION` | `SUPABASE_GET_MIGRATION` |
> | `SUPABASE_GET_PROJECT_S_PGBOUNCER_CONFIG` | `SUPABASE_GET_PROJECT_PGBOUNCER_CONFIG` |
> | `SUPABASE_LISTS_ALL_BACKUPS` | `SUPABASE_LIST_BACKUPS` |
> | `SUPABASE_LISTS_ALL_BUCKETS` | `SUPABASE_LIST_BUCKETS` |
> | `SUPABASE_LISTS_ALL_SSO_PROVIDERS` | `SUPABASE_LIST_SSO_PROVIDERS` |
> | `SUPABASE_LISTS_SQL_SNIPPETS_FOR_THE_LOGGED_IN_USER` | `SUPABASE_LIST_SQL_SNIPPETS` |
> | `SUPABASE_LIST_ALL_DATABASE_BRANCHES` | `SUPABASE_LIST_DATABASE_BRANCHES` |
> | `SUPABASE_LIST_ALL_FUNCTIONS` | `SUPABASE_LIST_FUNCTIONS` |
> | `SUPABASE_LIST_ALL_SECRETS` | `SUPABASE_LIST_SECRETS` |
> | `SUPABASE_LIST_MEMBERS_OF_AN_ORGANIZATION` | `SUPABASE_LIST_ORGANIZATION_MEMBERS` |
> | `SUPABASE_PATCH_A_MIGRATION` | `SUPABASE_PATCH_MIGRATION` |
> | `SUPABASE_PUSH_A_BRANCH` | `SUPABASE_PUSH_BRANCH` |
> | `SUPABASE_REMOVES_A_SSO_PROVIDER_BY_ITS_UUID` | `SUPABASE_DELETE_SSO_PROVIDER` |
> | `SUPABASE_RESETS_A_DATABASE_BRANCH` | `SUPABASE_RESET_DATABASE_BRANCH` |
> | `SUPABASE_RESTORES_A_PITR_BACKUP_FOR_A_DATABASE` | `SUPABASE_RESTORE_PITR_BACKUP` |
> | `SUPABASE_RESUMABLE_UPLOAD_SIGN_OPTIONS_WITH_ID` | `SUPABASE_HANDLE_RESUMABLE_UPLOAD_SIGN_OPTIONS_WITH_ID` |
> | `SUPABASE_RETRIEVE_A_FUNCTION` | `SUPABASE_GET_FUNCTION` |
> | `SUPABASE_RETRIEVE_A_FUNCTION_BODY` | `SUPABASE_GET_FUNCTION_BODY` |
> | `SUPABASE_RETURNS_PROJECT_S_READONLY_MODE_STATUS` | `SUPABASE_GET_PROJECT_READONLY_MODE_STATUS` |
> | `SUPABASE_UPDATES_A_SSO_PROVIDER_BY_ITS_UUID` | `SUPABASE_UPDATE_SSO_PROVIDER` |
> | `SUPABASE_UPDATES_PROJECT_S_POSTGREST_CONFIG` | `SUPABASE_UPDATE_PROJECT_POSTGREST_CONFIG` |
> | `SUPABASE_UPDATES_PROJECT_S_POSTGRES_CONFIG` | `SUPABASE_UPDATE_PROJECT_POSTGRES_CONFIG` |
> | `SUPABASE_UPDATES_PROJECT_S_SUPAVISOR_CONFIG` | `SUPABASE_UPDATE_PROJECT_SUPAVISOR_CONFIG` |
> | `SUPABASE_UPDATE_A_PROJECT` | `SUPABASE_UPDATE_PROJECT` |
> | `SUPABASE_UPDATE_PROJECT_CUSTOM_HOSTNAME_ACTION` | `SUPABASE_UPDATE_PROJECT_CUSTOM_HOSTNAME` |

> [accordion] Trello (63 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `TRELLO_ADD_BOARDS_CALENDAR_KEY_GENERATE_BY_ID_BOARD` | `TRELLO_GENERATE_BOARD_CALENDAR_KEY` |
> | `TRELLO_ADD_BOARDS_EMAIL_KEY_GENERATE_BY_ID_BOARD` | `TRELLO_GENERATE_BOARD_EMAIL_KEY` |
> | `TRELLO_ADD_BOARDS_LABELS_BY_ID_BOARD` | `TRELLO_CREATE_BOARD_LABEL` |
> | `TRELLO_ADD_BOARDS_MARK_AS_VIEWED_BY_ID_BOARD` | `TRELLO_MARK_BOARD_AS_VIEWED` |
> | `TRELLO_ADD_BOARDS_POWER_UPS_BY_ID_BOARD` | `TRELLO_ENABLE_BOARD_POWER_UP` |
> | `TRELLO_ADD_CARDS_ID_MEMBERS_BY_ID_CARD` | `TRELLO_ADD_MEMBER_TO_CARD` |
> | `TRELLO_ADD_CARDS_LABELS_BY_ID_CARD` | `TRELLO_CREATE_CARD_LABEL` |
> | `TRELLO_ADD_CARDS_MEMBERS_VOTED_BY_ID_CARD` | `TRELLO_ADD_CARD_VOTE` |
> | `TRELLO_ADD_CARDS_STICKERS_BY_ID_CARD` | `TRELLO_CREATE_CARD_STICKER` |
> | `TRELLO_ADD_LISTS_ARCHIVE_ALL_CARDS_BY_ID_LIST` | `TRELLO_ARCHIVE_ALL_LIST_CARDS` |
> | `TRELLO_ADD_LISTS_MOVE_ALL_CARDS_BY_ID_LIST` | `TRELLO_MOVE_ALL_LIST_CARDS` |
> | `TRELLO_ADD_MEMBERS_AVATAR_BY_ID_MEMBER` | `TRELLO_UPDATE_MEMBER_AVATAR` |
> | `TRELLO_ADD_MEMBERS_BOARD_BACKGROUNDS_BY_ID_MEMBER` | `TRELLO_CREATE_MEMBER_BOARD_BACKGROUND` |
> | `TRELLO_ADD_MEMBERS_BOARD_STARS_BY_ID_MEMBER` | `TRELLO_CREATE_MEMBER_BOARD_STAR` |
> | `TRELLO_ADD_MEMBERS_CUSTOM_BOARD_BACKGROUNDS_BY_ID_MEMBER` | `TRELLO_CREATE_MEMBER_CUSTOM_BOARD_BACKGROUND` |
> | `TRELLO_ADD_MEMBERS_CUSTOM_EMOJI_BY_ID_MEMBER` | `TRELLO_CREATE_MEMBER_CUSTOM_EMOJI` |
> | `TRELLO_ADD_MEMBERS_CUSTOM_STICKERS_BY_ID_MEMBER` | `TRELLO_CREATE_MEMBER_CUSTOM_STICKER` |
> | `TRELLO_ADD_MEMBERS_SAVED_SEARCHES_BY_ID_MEMBER` | `TRELLO_CREATE_MEMBER_SAVED_SEARCH` |
> | `TRELLO_ADD_NOTIFICATIONS_ALL_READ` | `TRELLO_MARK_ALL_NOTIFICATIONS_READ` |
> | `TRELLO_ADD_ORGANIZATIONS` | `TRELLO_CREATE_ORGANIZATION` |
> | `TRELLO_ADD_ORGANIZATIONS_LOGO_BY_ID_ORG` | `TRELLO_UPDATE_ORGANIZATION_LOGO` |
> | `TRELLO_ADD_SESSIONS` | `TRELLO_CREATE_SESSION` |
> | `TRELLO_CREATE_WEBHOOKS` | `TRELLO_CREATE_WEBHOOK` |
> | `TRELLO_DELETE_ACTIONS_BY_ID_ACTION` | `TRELLO_DELETE_ACTION` |
> | `TRELLO_DELETE_ACTIONS_REACTIONS` | `TRELLO_DELETE_ACTION_REACTION` |
> | `TRELLO_DELETE_BOARDS_BY_ID` | `TRELLO_DELETE_BOARD` |
> | `TRELLO_DELETE_BOARDS_MEMBERS_BY_ID_BOARD_BY_ID_MEMBER` | `TRELLO_REMOVE_BOARD_MEMBER` |
> | `TRELLO_DELETE_BOARDS_POWER_UPS_BY_ID_BOARD_BY_POWER_UP` | `TRELLO_DISABLE_BOARD_POWER_UP` |
> | `TRELLO_DELETE_CARDS_ACTIONS_COMMENTS_BY_ID_CARD_BY_ID_ACTION` | `TRELLO_DELETE_CARD_COMMENT` |
> | `TRELLO_DELETE_CARDS_ATTACHMENTS_BY_ID_CARD_BY_ID_ATTACHMENT` | `TRELLO_DELETE_CARD_ATTACHMENT` |
> | `TRELLO_DELETE_CARDS_CHECKLISTS_BY_ID_CARD_BY_ID_CHECKLIST` | `TRELLO_DELETE_CARD_CHECKLIST` |
> | `TRELLO_DELETE_CARDS_ID_LABELS_BY_ID_CARD_BY_ID_LABEL` | `TRELLO_REMOVE_LABEL_FROM_CARD` |
> | `TRELLO_DELETE_CARDS_ID_MEMBERS_BY_ID_CARD_BY_ID_MEMBER` | `TRELLO_REMOVE_MEMBER_FROM_CARD` |
> | `TRELLO_DELETE_CARDS_LABELS_BY_ID_CARD_BY_COLOR` | `TRELLO_REMOVE_CARD_LABEL_BY_COLOR` |
> | `TRELLO_GET_MEMBER_CUSTOM_STICKER` | `TRELLO_GET_MEMBERS_CUSTOM_STICKERS_BY_ID_MEMBER_BY_ID_STICKE` |
> | `TRELLO_GET_MEMBER_SAVED_SEARCH` | `TRELLO_GET_MEMBERS_SAVED_SEARCHES_BY_ID_MEMBER_BY_ID_SAVED_S` |
> | `TRELLO_GET_NOTIFICATION_ORG_FIELD` | `TRELLO_GET_NOTIFICATIONS_ORGANIZATION_BY_ID_NOTIFICATION_BY_` |
> | `TRELLO_GET_NOTIF_CREATOR_FIELD` | `TRELLO_GET_NOTIFICATIONS_MEMBER_CREATOR_BY_ID_NOTIFICATION_B` |
> | `TRELLO_UPDATE_BOARD_STAR_POSITION` | `TRELLO_UPDATE_BOARD_STARS_POSITION_BY_ID_MEMBER_BY_ID_BOARD_` |
> | `TRELLO_UPDATE_CARDS_CHECK_ITEM` | `TRELLO_UPDATE_CARDS_CHECKLIST_ITEMS_BY_ID_CARD_BY_ID_CHECKLI` |
> | `TRELLO_UPDATE_CARD_CHECKLIST_ITEM_POSITION` | `TRELLO_UPDATE_CARDS_CHECKLIST_ITEMS_POSITION_BY_ID_CARD_BY_I` |
> | `TRELLO_UPDATE_CARD_CHECKLIST_ITEM_STATE_BY_IDS` | `TRELLO_UPDATE_CARDS_CHECKLIST_ITEMS_STATE_BY_ID_CARD_BY_ID_C` |
> | `TRELLO_UPDATE_CARD_COMMENT` | `TRELLO_UPDATE_CARDS_ACTIONS_COMMENTS_BY_ID_CARD_BY_ID_ACTION` |
> | `TRELLO_UPDATE_CHECKLIST_FIELD` | `TRELLO_UPDATE_CHECKLISTS_BY_ID_CHECKLIST_BY_FIELD` |
> | `TRELLO_UPDATE_CHECKLIST_ITEM_NAME_IN_CARD` | `TRELLO_UPDATE_CARDS_CHECKLISTS_CHECK_ITEMS_NAME_BY_ID_CARD_B` |
> | `TRELLO_UPDATE_LABEL_FIELD` | `TRELLO_UPDATE_LABELS_BY_ID_LABEL_BY_FIELD` |
> | `TRELLO_UPDATE_MEMBER_BOARD_BACKGROUND` | `TRELLO_UPDATE_MEMBERS_BOARD_BACKGROUNDS_BY_ID_MEMBER_BY_ID_B` |
> | `TRELLO_UPDATE_MEMBER_BOARD_STAR` | `TRELLO_UPDATE_MEMBERS_BOARD_STARS_BY_ID_MEMBER_BY_ID_BOARD_S` |
> | `TRELLO_UPDATE_MEMBER_SAVED_SEARCH` | `TRELLO_UPDATE_MEMBERS_SAVED_SEARCHES_BY_ID_MEMBER_BY_ID_SAVE` |
> | `TRELLO_UPDATE_MEMBER_SAVED_SEARCH_NAME` | `TRELLO_UPDATE_MEMBERS_SAVED_SEARCHES_NAME_BY_ID_MEMBER_BY_ID` |
> | `TRELLO_UPDATE_MEMBER_SAVED_SEARCH_POS` | `TRELLO_UPDATE_MEMBERS_SAVED_SEARCHES_POS_BY_ID_MEMBER_BY_ID_` |
> | `TRELLO_UPDATE_MEMBER_SAVED_SEARCH_QUERY` | `TRELLO_UPDATE_MEMBERS_SAVED_SEARCHES_QUERY_BY_ID_MEMBER_BY_I` |
> | `TRELLO_UPDATE_MEMBER_SUMMARY_INTERVAL` | `TRELLO_UPDATE_MEMBERS_PREFS_SUMMARY_INTERVAL_BY_ID_MEMBER` |
> | `TRELLO_UPDATE_MEMBER_S_CUSTOM_BOARD_BACKGROUNDS` | `TRELLO_UPDATE_MEMBERS_CUSTOM_BOARD_BACKGROUNDS_BY_ID_MEMBER_` |
> | `TRELLO_UPDATE_ORG_ASSOCIATED_DOMAIN_PREFS` | `TRELLO_UPDATE_ORGANIZATIONS_PREFS_ASSOCIATED_DOMAIN_BY_ID_OR` |
> | `TRELLO_UPDATE_ORG_BOARD_VISIBILITY` | `TRELLO_UPDATE_ORGANIZATIONS_PREFS_BOARD_VISIBILITY_BY_ID_ORG` |
> | `TRELLO_UPDATE_ORG_EXTERNAL_MEMBERS_ACCESS` | `TRELLO_UPDATE_ORGANIZATIONS_PREFS_EXTERNAL_MEMBERS_ACCESS_BY` |
> | `TRELLO_UPDATE_ORG_MEMBERSHIP` | `TRELLO_UPDATE_ORGANIZATIONS_MEMBERSHIPS_BY_ID_ORG_BY_ID_MEMB` |
> | `TRELLO_UPDATE_ORG_MEMBER_DEACTIVATION` | `TRELLO_UPDATE_ORGANIZATIONS_MEMBERS_DEACTIVATION_BY_ID_ORG_B` |
> | `TRELLO_UPDATE_ORG_PRIVATE_BOARD_VISIBILITY` | `TRELLO_UPDATE_ORGANIZATIONS_PREFS_PRIVATE_BOARD_VISIBILITY_B` |
> | `TRELLO_UPDATE_ORG_PUBLIC_BOARD_VISIBILITY` | `TRELLO_UPDATE_ORGANIZATIONS_PREFS_PUBLIC_BOARD_VISIBILITY_BY` |
> | `TRELLO_UPDATE_WEBHOOKS` | `TRELLO_UPDATE_WEBHOOKS_BY_ID_WEBHOOK` |
> | `TRELLO_UPDATE_WEBHOOKS_CALLBACK_URLBY_ID_WEBHOOK` | `TRELLO_UPDATE_WEBHOOKS_CALLBACK_URL_BY_ID_WEBHOOK` |

> [accordion] HubSpot (61 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `HUBSPOT_ARCHIVE` | `HUBSPOT_ARCHIVE_EMAIL` |
> | `HUBSPOT_ARCHIVE_A_BATCH_OF_QUOTES_BY_ID` | `HUBSPOT_ARCHIVE_BATCH_OF_QUOTES` |
> | `HUBSPOT_ARCHIVE_BATCH_OF_FEEDBACK_SUBMISSIONS_BY_ID` | `HUBSPOT_ARCHIVE_BATCH_OF_FEEDBACK_SUBMISSIONS` |
> | `HUBSPOT_ARCHIVE_BATCH_OF_LINE_ITEMS_BY_ID` | `HUBSPOT_ARCHIVE_BATCH_OF_LINE_ITEMS` |
> | `HUBSPOT_ARCHIVE_BATCH_OF_OBJECTS_BY_ID` | `HUBSPOT_ARCHIVE_BATCH_OF_OBJECTS` |
> | `HUBSPOT_ARCHIVE_LINE_ITEM_BY_ID` | `HUBSPOT_ARCHIVE_LINE_ITEM` |
> | `HUBSPOT_ARCHIVE_QUOTE_OBJECT_BY_ID` | `HUBSPOT_ARCHIVE_QUOTE` |
> | `HUBSPOT_AUDIT_PIPELINE_CHANGES_BY_ID` | `HUBSPOT_AUDIT_PIPELINE_CHANGES` |
> | `HUBSPOT_CANCEL_ACTIVE_IMPORT` | `HUBSPOT_CANCEL_IMPORT` |
> | `HUBSPOT_CREATE_ASSOCIATION_FOR_OBJECT_TYPE` | `HUBSPOT_CREATE_ASSOCIATION` |
> | `HUBSPOT_CREATE_MULTIPLE_TIMELINE_EVENTS_BATCH` | `HUBSPOT_CREATE_TIMELINE_EVENTS_BATCH` |
> | `HUBSPOT_CREATE_NEW_OBJECT_SCHEMA_WITH_CUSTOM_PROPERTIES` | `HUBSPOT_CREATE_OBJECT_SCHEMA` |
> | `HUBSPOT_CREATE_PIPELINE_FOR_OBJECT_TYPE` | `HUBSPOT_CREATE_PIPELINE` |
> | `HUBSPOT_CREATE_TIMELINE_EVENT_BASED_ON_TEMPLATE` | `HUBSPOT_CREATE_TIMELINE_EVENT` |
> | `HUBSPOT_DELETE_A_BATCH_OF_CAMPAIGNS` | `HUBSPOT_DELETE_CAMPAIGNS_BATCH` |
> | `HUBSPOT_DELETE_A_MARKETING_EMAIL` | `HUBSPOT_DELETE_MARKETING_EMAIL` |
> | `HUBSPOT_DELETE_PIPELINE_BY_ID` | `HUBSPOT_DELETE_PIPELINE` |
> | `HUBSPOT_DELETE_PIPELINE_STAGE_BY_ID` | `HUBSPOT_DELETE_PIPELINE_STAGE` |
> | `HUBSPOT_DELETE_SCHEMA_BY_OBJECT_TYPE` | `HUBSPOT_DELETE_SCHEMA` |
> | `HUBSPOT_FETCH_RECORDING_SETTINGS_BY_APP_ID` | `HUBSPOT_FETCH_RECORDING_SETTINGS` |
> | `HUBSPOT_GET_ALL_WORKFLOWS` | `HUBSPOT_GET_WORKFLOWS` |
> | `HUBSPOT_GET_A_REVISION_OF_A_MARKETING_EMAIL` | `HUBSPOT_GET_MARKETING_EMAIL_REVISION` |
> | `HUBSPOT_GET_DRAFT_VERSION_OF_A_MARKETING_EMAIL` | `HUBSPOT_GET_MARKETING_EMAIL_DRAFT` |
> | `HUBSPOT_GET_QUOTE_BY_ID` | `HUBSPOT_GET_QUOTE` |
> | `HUBSPOT_GET_REVISIONS_OF_A_MARKETING_EMAIL` | `HUBSPOT_GET_MARKETING_EMAIL_REVISIONS` |
> | `HUBSPOT_GET_SPECIFIC_EVENT_TEMPLATE_FOR_APP` | `HUBSPOT_GET_EVENT_TEMPLATE` |
> | `HUBSPOT_GET_THE_VARIATION_OF_A_AN_AB_MARKETING_EMAIL` | `HUBSPOT_GET_AB_EMAIL_VARIATION` |
> | `HUBSPOT_INITIATE_DATA_IMPORT_PROCESS` | `HUBSPOT_START_IMPORT` |
> | `HUBSPOT_LIST` | `HUBSPOT_LIST_EMAILS` |
> | `HUBSPOT_LIST_ALL_EVENT_TEMPLATES_FOR_APP` | `HUBSPOT_LIST_EVENT_TEMPLATES` |
> | `HUBSPOT_LIST_FEEDBACK_SUBMISSIONS_PAGE` | `HUBSPOT_LIST_FEEDBACK_SUBMISSIONS` |
> | `HUBSPOT_LIST_QUOTES_PAGE` | `HUBSPOT_LIST_QUOTES` |
> | `HUBSPOT_MERGE_TWO_COMPANIES_OF_SAME_TYPE` | `HUBSPOT_MERGE_COMPANIES` |
> | `HUBSPOT_MERGE_TWO_FEEDBACK_SUBMISSIONS` | `HUBSPOT_MERGE_FEEDBACK_SUBMISSIONS` |
> | `HUBSPOT_MERGE_TWO_LINE_ITEMS_OF_SAME_TYPE` | `HUBSPOT_MERGE_LINE_ITEMS` |
> | `HUBSPOT_MERGE_TWO_OBJECTS_OF_SAME_TYPE` | `HUBSPOT_MERGE_OBJECTS` |
> | `HUBSPOT_MERGE_TWO_QUOTES_OF_SAME_TYPE` | `HUBSPOT_MERGE_QUOTES` |
> | `HUBSPOT_MODIFY_CALLING_EXTENSION_SETTINGS` | `HUBSPOT_UPDATE_CALLING_EXTENSION_SETTINGS` |
> | `HUBSPOT_PARTIALLY_UPDATE_PIPELINE_BY_ID` | `HUBSPOT_UPDATE_PIPELINE` |
> | `HUBSPOT_PARTIALLY_UPDATE_PROPERTY_GROUP` | `HUBSPOT_UPDATE_PROPERTY_GROUP` |
> | `HUBSPOT_PARTIAL_UPDATE_QUOTE_BY_QUOTE_ID` | `HUBSPOT_UPDATE_QUOTE` |
> | `HUBSPOT_PERMANENTLY_DELETE_COMPANY_FOR_GDPR_COMPLIANCE` | `HUBSPOT_DELETE_COMPANY_GDPR` |
> | `HUBSPOT_PERMANENTLY_DELETE_CONTACT_FOR_GDPR_COMPLIANCE` | `HUBSPOT_DELETE_CONTACT_GDPR` |
> | `HUBSPOT_PERMANENTLY_DELETE_DEAL_FOR_GDPR_COMPLIANCE` | `HUBSPOT_DELETE_DEAL_GDPR` |
> | `HUBSPOT_PERMANENTLY_DELETE_LINE_ITEMS_FOR_GDPR` | `HUBSPOT_DELETE_LINE_ITEMS_GDPR` |
> | `HUBSPOT_PURGE_SCHEMA_BY_OBJECT_TYPE` | `HUBSPOT_PURGE_SCHEMA` |
> | `HUBSPOT_READ` | `HUBSPOT_READ_EMAIL` |
> | `HUBSPOT_READ_A_BATCH_OF_CRM_OBJECT_PROPERTIES` | `HUBSPOT_READ_BATCH_CRM_OBJECT_PROPERTIES` |
> | `HUBSPOT_READ_A_PROPERTY_GROUP` | `HUBSPOT_READ_PROPERTY_GROUP` |
> | `HUBSPOT_RESTORE_A_REVISION_OF_A_MARKETING_EMAIL` | `HUBSPOT_RESTORE_MARKETING_EMAIL_REVISION` |
> | `HUBSPOT_RESTORE_A_REVISION_OF_A_MARKETING_EMAIL_TO_DRAFT_STATE` | `HUBSPOT_RESTORE_EMAIL_REVISION` |
> | `HUBSPOT_RETRIEVE_LINE_ITEMS_LIST` | `HUBSPOT_RETRIEVE_LINE_ITEMS` |
> | `HUBSPOT_RETURN_PIPELINE_BY_ID` | `HUBSPOT_GET_PIPELINE_BY_ID` |
> | `HUBSPOT_UPDATE` | `HUBSPOT_UPDATE_EMAIL` |
> | `HUBSPOT_UPDATE_A_BATCH_OF_CAMPAIGNS` | `HUBSPOT_UPDATE_CAMPAIGNS` |
> | `HUBSPOT_UPDATE_A_BATCH_OF_LINE_ITEMS` | `HUBSPOT_UPDATE_LINE_ITEMS` |
> | `HUBSPOT_UPDATE_EXISTING_EVENT_TEMPLATE` | `HUBSPOT_UPDATE_EVENT_TEMPLATE` |
> | `HUBSPOT_UPDATE_FEEDBACK_SUBMISSION_BY_ID` | `HUBSPOT_UPDATE_FEEDBACK_SUBMISSION` |
> | `HUBSPOT_UPDATE_LINE_ITEM_OBJECT_PARTIALLY` | `HUBSPOT_UPDATE_LINE_ITEM` |
> | `HUBSPOT_UPDATE_PIPELINE_STAGE_BY_IDS` | `HUBSPOT_UPDATE_PIPELINE_STAGE` |
> | `HUBSPOT_UPDATE_SPECIFIC_CRM_PROPERTY` | `HUBSPOT_UPDATE_CRM_PROPERTY` |

> [accordion] Box (58 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `BOX_ADD_DOMAIN_TO_LIST_OF_ALLOWED_COLLABORATION_DOMAINS` | `BOX_ADD_ALLOWED_COLLABORATION_DOMAIN` |
> | `BOX_CHANGE_SHIELD_INFORMATION_BARRIER_STATUS` | `BOX_UPDATE_SHIELD_INFORMATION_BARRIER_STATUS` |
> | `BOX_CREATE_JOBS_TO_TERMINATE_USERS_SESSION` | `BOX_TERMINATE_USER_SESSIONS` |
> | `BOX_CREATE_JOBS_TO_TERMINATE_USER_GROUP_SESSION` | `BOX_TERMINATE_USER_GROUP_SESSIONS` |
> | `BOX_GET_AI_AGENT_BY_AGENT_ID` | `BOX_GET_AI_AGENT` |
> | `BOX_GET_BOX_SIGN_REQUEST_BY_ID` | `BOX_GET_BOX_SIGN_REQUEST` |
> | `BOX_GET_BOX_SIGN_TEMPLATE_BY_ID` | `BOX_GET_BOX_SIGN_TEMPLATE` |
> | `BOX_GET_COLLECTION_BY_ID` | `BOX_GET_COLLECTION` |
> | `BOX_GET_FOLDER_INFORMATION` | `BOX_GET_FOLDER` |
> | `BOX_GET_SHARED_ITEMS_WEB_LINKS` | `BOX_GET_SHARED_WEB_LINK` |
> | `BOX_GET_SHIELD_INFORMATION_BARRIER_SEGMENT_WITH_SPECIFIED_ID` | `BOX_GET_SHIELD_INFORMATION_BARRIER_SEGMENT_BY_ID` |
> | `BOX_GET_SHIELD_INFORMATION_BARRIER_WITH_SPECIFIED_ID` | `BOX_GET_SHIELD_INFORMATION_BARRIER_BY_ID` |
> | `BOX_GET_WATERMARK_FOR_FOLDER` | `BOX_GET_WATERMARK_ON_FOLDER` |
> | `BOX_LIST_ALL_LEGAL_HOLD_POLICIES` | `BOX_LIST_LEGAL_HOLD_POLICIES` |
> | `BOX_LIST_ALL_METADATA_TEMPLATES_FOR_ENTERPRISE` | `BOX_LIST_ENTERPRISE_METADATA_TEMPLATES` |
> | `BOX_LIST_ALL_WEBHOOKS` | `BOX_LIST_WEBHOOKS` |
> | `BOX_LIST_GROUPS_FOR_ENTERPRISE` | `BOX_LIST_ENTERPRISE_GROUPS` |
> | `BOX_LIST_MEMBERS_OF_GROUP` | `BOX_LIST_GROUP_MEMBERS` |
> | `BOX_LIST_PARTS` | `BOX_LIST_UPLOAD_SESSION_PARTS` |
> | `BOX_LIST_PREVIOUS_FILE_VERSIONS_FOR_LEGAL_HOLD_POLICY_ASSIGNMENT` | `BOX_LIST_HOLD_FILE_VERSIONS` |
> | `BOX_LIST_USER_AND_ENTERPRISE_EVENTS` | `BOX_LIST_EVENTS` |
> | `BOX_LIST_USER_S_EMAIL_ALIASES` | `BOX_LIST_USER_EMAIL_ALIASES` |
> | `BOX_LIST_USER_S_GROUPS` | `BOX_LIST_USER_GROUPS` |
> | `BOX_PERMANENTLY_REMOVE_FILE` | `BOX_DELETE_FILE_PERMANENTLY` |
> | `BOX_PERMANENTLY_REMOVE_FOLDER` | `BOX_DELETE_FOLDER_PERMANENTLY` |
> | `BOX_PERMANENTLY_REMOVE_WEB_LINK` | `BOX_DELETE_WEB_LINK_PERMANENTLY` |
> | `BOX_REMOVE_BOX_SKILL_CARDS_FROM_FILE` | `BOX_DELETE_BOX_SKILL_CARDS_FROM_FILE` |
> | `BOX_REMOVE_COLLABORATION` | `BOX_DELETE_COLLABORATION` |
> | `BOX_REMOVE_COMMENT` | `BOX_DELETE_COMMENT` |
> | `BOX_REMOVE_DEVICE_PIN` | `BOX_DELETE_DEVICE_PIN` |
> | `BOX_REMOVE_DOMAIN_FROM_LIST_OF_ALLOWED_COLLABORATION_DOMAINS` | `BOX_DELETE_ALLOWED_COLLABORATION_DOMAIN` |
> | `BOX_REMOVE_EMAIL_ALIAS` | `BOX_DELETE_EMAIL_ALIAS` |
> | `BOX_REMOVE_FILE_VERSION` | `BOX_DELETE_FILE_VERSION` |
> | `BOX_REMOVE_GROUP` | `BOX_DELETE_GROUP` |
> | `BOX_REMOVE_LEGAL_HOLD_POLICY` | `BOX_DELETE_LEGAL_HOLD_POLICY` |
> | `BOX_REMOVE_METADATA_CASCADE_POLICY` | `BOX_DELETE_METADATA_CASCADE_POLICY` |
> | `BOX_REMOVE_METADATA_INSTANCE_FROM_FILE` | `BOX_DELETE_METADATA_INSTANCE_FROM_FILE` |
> | `BOX_REMOVE_METADATA_INSTANCE_FROM_FOLDER` | `BOX_DELETE_METADATA_INSTANCE_FROM_FOLDER` |
> | `BOX_REMOVE_METADATA_TAXONOMY` | `BOX_DELETE_METADATA_TAXONOMY` |
> | `BOX_REMOVE_METADATA_TAXONOMY_NODE` | `BOX_DELETE_METADATA_TAXONOMY_NODE` |
> | `BOX_REMOVE_METADATA_TEMPLATE` | `BOX_DELETE_METADATA_TEMPLATE` |
> | `BOX_REMOVE_RETENTION_POLICY_ASSIGNMENT` | `BOX_DELETE_RETENTION_POLICY_ASSIGNMENT` |
> | `BOX_REMOVE_SHARED_LINK_FROM_FILE` | `BOX_DELETE_SHARED_LINK_FROM_FILE` |
> | `BOX_REMOVE_SHARED_LINK_FROM_FOLDER` | `BOX_DELETE_SHARED_LINK_FROM_FOLDER` |
> | `BOX_REMOVE_SHARED_LINK_FROM_WEB_LINK` | `BOX_DELETE_SHARED_LINK_FROM_WEB_LINK` |
> | `BOX_REMOVE_TASK` | `BOX_DELETE_TASK` |
> | `BOX_REMOVE_UPLOAD_SESSION` | `BOX_DELETE_UPLOAD_SESSION` |
> | `BOX_REMOVE_USER_DOMAIN_EXEMPTION` | `BOX_DELETE_USER_DOMAIN_EXEMPTION` |
> | `BOX_REMOVE_USER_FROM_GROUP` | `BOX_DELETE_USER_FROM_GROUP` |
> | `BOX_REMOVE_WATERMARK_FROM_FILE` | `BOX_DELETE_WATERMARK_FROM_FILE` |
> | `BOX_REMOVE_WATERMARK_FROM_FOLDER` | `BOX_DELETE_WATERMARK_FROM_FOLDER` |
> | `BOX_REMOVE_WEBHOOK` | `BOX_DELETE_WEBHOOK` |
> | `BOX_REMOVE_WEB_LINK` | `BOX_DELETE_WEB_LINK` |
> | `BOX_REVIEW_FILES_ON_LEGAL_HOLD_POLICY_ASSIGNMENT` | `BOX_LIST_FILES_ON_LEGAL_HOLD_POLICY_ASSIGNMENT` |
> | `BOX_STARTS_WORKFLOW_BASED_ON_REQUEST_BODY` | `BOX_START_WORKFLOW` |
> | `BOX_UNASSIGN_STORAGE_POLICY` | `BOX_DELETE_STORAGE_POLICY_ASSIGNMENT` |
> | `BOX_UNASSIGN_TASK` | `BOX_DELETE_TASK_ASSIGNMENT` |
> | `BOX_UPDATE_SHIELD_INFORMATION_BARRIER_SEGMENT_WITH_SPECIFIED_ID` | `BOX_UPDATE_BARRIER_SEGMENT` |

> [accordion] Slack (48 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `SLACK_ADD_AN_EMOJI_ALIAS_IN_SLACK` | `SLACK_ADD_EMOJI_ALIAS` |
> | `SLACK_ADD_A_REMOTE_FILE_FROM_A_SERVICE` | `SLACK_ADD_REMOTE_FILE` |
> | `SLACK_ADD_A_STAR_TO_AN_ITEM` | `SLACK_ADD_STAR` |
> | `SLACK_ADMIN_APPS_APPROVED_LIST` | `SLACK_LIST_ADMIN_APPS_APPROVED` |
> | `SLACK_ADMIN_APPS_REQUESTS_LIST` | `SLACK_LIST_ADMIN_APPS_REQUESTS` |
> | `SLACK_ARCHIVE_A_SLACK_CONVERSATION` | `SLACK_ARCHIVE_CONVERSATION` |
> | `SLACK_CLOSE_DM_OR_MULTI_PERSON_DM` | `SLACK_CLOSE_DM` |
> | `SLACK_CONVERT_PUBLIC_CHANNEL_TO_PRIVATE` | `SLACK_CONVERT_CHANNEL_TO_PRIVATE` |
> | `SLACK_CREATE_A_SLACK_USER_GROUP` | `SLACK_CREATE_USER_GROUP` |
> | `SLACK_DELETE_A_COMMENT_ON_A_FILE` | `SLACK_DELETE_FILE_COMMENT` |
> | `SLACK_DELETE_A_FILE_BY_ID` | `SLACK_DELETE_FILE` |
> | `SLACK_DELETE_A_PUBLIC_OR_PRIVATE_CHANNEL` | `SLACK_DELETE_CHANNEL` |
> | `SLACK_DELETE_A_SCHEDULED_MESSAGE_IN_A_CHAT` | `SLACK_DELETE_SCHEDULED_MESSAGE` |
> | `SLACK_DELETE_A_SLACK_REMINDER` | `SLACK_DELETE_REMINDER` |
> | `SLACK_DISABLE_AN_EXISTING_SLACK_USER_GROUP` | `SLACK_DISABLE_USER_GROUP` |
> | `SLACK_ENABLE_A_SPECIFIED_USER_GROUP` | `SLACK_ENABLE_USER_GROUP` |
> | `SLACK_END_A_CALL_WITH_DURATION_AND_ID` | `SLACK_END_CALL` |
> | `SLACK_END_USER_DO_NOT_DISTURB_SESSION` | `SLACK_END_DND` |
> | `SLACK_FETCH_BOT_USER_INFORMATION` | `SLACK_GET_BOT_USER` |
> | `SLACK_FETCH_WORKSPACE_SETTINGS_INFORMATION` | `SLACK_GET_WORKSPACE_SETTINGS` |
> | `SLACK_GET_REMINDER_INFORMATION` | `SLACK_GET_REMINDER` |
> | `SLACK_GET_TEAM_DND_STATUS` | `SLACK_GET_USER_DND_STATUS` |
> | `SLACK_GET_USER_PRESENCE_INFO` | `SLACK_GET_USER_PRESENCE` |
> | `SLACK_LEAVE_A_CONVERSATION` | `SLACK_LEAVE_CONVERSATION` |
> | `SLACK_LISTS_PINNED_ITEMS_IN_A_CHANNEL` | `SLACK_LIST_PINNED_ITEMS` |
> | `SLACK_LIST_ALL_USERS_IN_A_USER_GROUP` | `SLACK_LIST_USER_GROUP_MEMBERS` |
> | `SLACK_LIST_RESTRICTED_APPS_FOR_ORG_OR_WORKSPACE` | `SLACK_LIST_RESTRICTED_APPS` |
> | `SLACK_LIST_TEAM_CUSTOM_EMOJIS` | `SLACK_LIST_CUSTOM_EMOJIS` |
> | `SLACK_LIST_USER_GROUPS_FOR_TEAM_WITH_OPTIONS` | `SLACK_LIST_USER_GROUPS` |
> | `SLACK_MANUALLY_SET_USER_PRESENCE` | `SLACK_SET_USER_PRESENCE` |
> | `SLACK_PINS_AN_ITEM_TO_A_CHANNEL` | `SLACK_PIN_ITEM` |
> | `SLACK_REMOVE_A_REMOTE_FILE` | `SLACK_REMOVE_REMOTE_FILE` |
> | `SLACK_REMOVE_A_STAR_FROM_AN_ITEM` | `SLACK_REMOVE_STAR` |
> | `SLACK_REMOVE_A_USER_FROM_A_CONVERSATION` | `SLACK_REMOVE_USER_FROM_CONVERSATION` |
> | `SLACK_RENAME_AN_EMOJI` | `SLACK_RENAME_EMOJI` |
> | `SLACK_RENAME_A_CONVERSATION` | `SLACK_RENAME_CONVERSATION` |
> | `SLACK_RETRIEVE_CALL_INFORMATION` | `SLACK_GET_CALL_INFO` |
> | `SLACK_RETRIEVE_TEAM_PROFILE_DETAILS` | `SLACK_GET_TEAM_PROFILE` |
> | `SLACK_REVOKE_PUBLIC_SHARING_ACCESS_FOR_A_FILE` | `SLACK_REVOKE_FILE_PUBLIC_SHARING` |
> | `SLACK_SET_A_CONVERSATION_S_PURPOSE` | `SLACK_SET_CONVERSATION_PURPOSE` |
> | `SLACK_SET_SLACK_USER_PROFILE_INFORMATION` | `SLACK_SET_USER_PROFILE` |
> | `SLACK_SHARE_A_ME_MESSAGE_IN_A_CHANNEL` | `SLACK_SEND_ME_MESSAGE` |
> | `SLACK_SHARE_REMOTE_FILE_IN_CHANNELS` | `SLACK_SHARE_REMOTE_FILE` |
> | `SLACK_UNPIN_ITEM_FROM_CHANNEL` | `SLACK_UNPIN_ITEM` |
> | `SLACK_UPDATES_AN_EXISTING_REMOTE_FILE` | `SLACK_UPDATE_REMOTE_FILE` |
> | `SLACK_UPDATE_AN_EXISTING_SLACK_USER_GROUP` | `SLACK_UPDATE_USER_GROUP` |
> | `SLACK_UPDATE_SLACK_CALL_INFORMATION` | `SLACK_UPDATE_CALL_INFO` |
> | `SLACK_USERS_SET_ACTIVE` | `SLACK_SET_USER_ACTIVE` |

> [accordion] Salesforce (41 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `SALESFORCE_CLOSE_OR_ABORT_A_JOB` | `SALESFORCE_CLOSE_OR_ABORT_JOB` |
> | `SALESFORCE_CUSTOM_INVOCABLE_ACTIONS` | `SALESFORCE_LIST_CUSTOM_INVOCABLE_ACTIONS` |
> | `SALESFORCE_FILE_INFORMATION` | `SALESFORCE_GET_FILE_INFORMATION` |
> | `SALESFORCE_FILE_SHARES` | `SALESFORCE_GET_FILE_SHARES` |
> | `SALESFORCE_GET_AN_APP` | `SALESFORCE_GET_APP` |
> | `SALESFORCE_GET_A_DIRECTORY_OF_SUPPORTED_OBJECTS` | `SALESFORCE_GET_SUPPORTED_OBJECTS_DIRECTORY` |
> | `SALESFORCE_GET_CONSENT` | `SALESFORCE_GET_CONSENT_ACTION` |
> | `SALESFORCE_GET_DATA_UIAPI_ACTIONS_LIST_VIEW` | `SALESFORCE_GET_LIST_VIEW_ACTIONS` |
> | `SALESFORCE_GET_JOB_INFO_QUERY` | `SALESFORCE_GET_QUERY_JOB_INFO` |
> | `SALESFORCE_GET_JOB_QUERY_RESULT` | `SALESFORCE_GET_QUERY_JOB_RESULTS` |
> | `SALESFORCE_GET_LIMITS` | `SALESFORCE_GET_ORG_LIMITS` |
> | `SALESFORCE_GET_LIMITS_RECORDCOUNT` | `SALESFORCE_GET_RECORD_COUNTS` |
> | `SALESFORCE_GET_LIST_VIEW_FOR_AN_OBJECT` | `SALESFORCE_GET_OBJECT_LIST_VIEWS` |
> | `SALESFORCE_GET_LIST_VIEW_METADATA_PER_API_NAME` | `SALESFORCE_GET_LIST_VIEW_METADATA_BY_NAME` |
> | `SALESFORCE_GET_LIST_VIEW_RECORDS_PER_API_NAME` | `SALESFORCE_GET_LIST_VIEW_RECORDS_BY_NAME` |
> | `SALESFORCE_GET_LIST_VIEW_RECORDS_PER_ID` | `SALESFORCE_GET_LIST_VIEW_RECORDS_BY_ID` |
> | `SALESFORCE_GET_MOST_RECENTLY_USED_LIST_VIEW_RECORDS` | `SALESFORCE_GET_MRU_LIST_VIEW_RECORDS` |
> | `SALESFORCE_GET_RELATED_LIST_PREFS_BATCH` | `SALESFORCE_GET_RELATED_LIST_PREFERENCES_BATCH` |
> | `SALESFORCE_GET_SEARCH_RESULT_LAYOUTS` | `SALESFORCE_GET_SEARCH_LAYOUT` |
> | `SALESFORCE_GET_SOBJECT_APPROVAL_LAYOUTS` | `SALESFORCE_GET_SOBJECTS_SOBJECT_DESCRIBE_APPROVALLAYOUTS` |
> | `SALESFORCE_GET_SOBJECT_LISTVIEWS` | `SALESFORCE_GET_SOBJECT_LIST_VIEWS` |
> | `SALESFORCE_GET_S_OBJECT_BY_EXTERNAL_ID` | `SALESFORCE_GET_SOBJECT_BY_EXTERNAL_ID` |
> | `SALESFORCE_GET_S_OBJECT_COLLECTIONS` | `SALESFORCE_GET_SOBJECT_COLLECTIONS` |
> | `SALESFORCE_GET_S_OBJECT_LIST_VIEW` | `SALESFORCE_GET_SOBJECT_LIST_VIEW` |
> | `SALESFORCE_GET_UI_API_RECORDS_BATCH` | `SALESFORCE_GET_A_BATCH_OF_RECORDS` |
> | `SALESFORCE_GET_USER_PASSWORD_EXPIRATION_STATUS` | `SALESFORCE_SOBJECT_USER_PASSWORD` |
> | `SALESFORCE_POST_COMPOSITE_SOBJECTS_SOBJECT` | `SALESFORCE_GET_COMPOSITE_SOBJECTS` |
> | `SALESFORCE_POST_SOBJECT_QUICK_ACTIONS` | `SALESFORCE_EXECUTE_SOBJECT_QUICK_ACTION` |
> | `SALESFORCE_POST_UIAPI_LOOKUPS_CASE_CONTACT_ID` | `SALESFORCE_GET_LOOKUP_SUGGESTIONS_CASE_CONTACT` |
> | `SALESFORCE_POST_UI_API_RELATED_LIST_RECORDS_CONTACTS` | `SALESFORCE_GET_RELATED_LIST_RECORDS_CONTACTS` |
> | `SALESFORCE_QUICK_ACTIONS` | `SALESFORCE_GET_QUICK_ACTIONS` |
> | `SALESFORCE_RETRIEVE_SPECIFIC_CONTACT_BY_ID` | `SALESFORCE_GET_CONTACT_BY_ID` |
> | `SALESFORCE_SEARCH_SUGGESTED_QUERIES` | `SALESFORCE_GET_SEARCH_SUGGESTIONS` |
> | `SALESFORCE_SEARCH_SUGGEST_TITLE_MATCHES` | `SALESFORCE_SEARCH_KNOWLEDGE_ARTICLES` |
> | `SALESFORCE_SOBJECT_COLLECTIONS_DELETE` | `SALESFORCE_DELETE_SOBJECT_COLLECTIONS` |
> | `SALESFORCE_SOBJECT_PLATFORMACTION` | `SALESFORCE_GET_SOBJECT_PLATFORMACTION` |
> | `SALESFORCE_SOBJECT_TREE` | `SALESFORCE_CREATE_SOBJECT_TREE` |
> | `SALESFORCE_STANDARD_INVOCABLE_ACTIONS` | `SALESFORCE_LIST_STANDARD_INVOCABLE_ACTIONS` |
> | `SALESFORCE_UPDATE_A_FAVORITE` | `SALESFORCE_UPDATE_FAVORITE` |
> | `SALESFORCE_UPDATE_A_RECORD` | `SALESFORCE_UPDATE_RECORD` |
> | `SALESFORCE_UPSERT_S_OBJECT_BY_EXTERNAL_ID` | `SALESFORCE_UPSERT_SOBJECT_BY_EXTERNAL_ID` |

> [accordion] Vercel (39 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `VERCEL_ARTIFACT_EXISTS` | `VERCEL_CHECK_CACHE_ARTIFACT_EXISTS` |
> | `VERCEL_CREATE_AUTH_TOKEN2` | `VERCEL_CREATE_AUTH_TOKEN` |
> | `VERCEL_CREATE_EDGE_CONFIG_TOKEN2` | `VERCEL_CREATE_EDGE_CONFIG_TOKEN` |
> | `VERCEL_DELETE_DEPLOYMENT2` | `VERCEL_DELETE_DEPLOYMENT` |
> | `VERCEL_DELETE_EDGE_CONFIG_TOKENS2` | `VERCEL_DELETE_EDGE_CONFIG_TOKENS` |
> | `VERCEL_DELETE_PROJECT2` | `VERCEL_DELETE_PROJECT` |
> | `VERCEL_GET_DNS_RECORDS` | `VERCEL_LIST_DNS_RECORDS` |
> | `VERCEL_GET_DOMAINS` | `VERCEL_LIST_DOMAINS` |
> | `VERCEL_GET_EDGE_CONFIG2` | `VERCEL_GET_EDGE_CONFIG` |
> | `VERCEL_GET_EDGE_CONFIGS` | `VERCEL_LIST_EDGE_CONFIGS` |
> | `VERCEL_GET_EDGE_CONFIG_BACKUPS` | `VERCEL_LIST_EDGE_CONFIG_BACKUPS` |
> | `VERCEL_GET_EDGE_CONFIG_ITEMS` | `VERCEL_LIST_EDGE_CONFIG_ITEMS` |
> | `VERCEL_GET_EDGE_CONFIG_TOKENS` | `VERCEL_LIST_EDGE_CONFIG_TOKENS` |
> | `VERCEL_GET_INTEGRATION_LOG_DRAINS` | `VERCEL_LIST_INTEGRATION_LOG_DRAINS` |
> | `VERCEL_GET_PROJECT_CUSTOM_ENVIRONMENTS` | `VERCEL_LIST_PROJECT_CUSTOM_ENVIRONMENTS` |
> | `VERCEL_GET_PROJECT_MEMBERS` | `VERCEL_LIST_PROJECT_MEMBERS` |
> | `VERCEL_GET_SUPPORTED_TLDS` | `VERCEL_LIST_SUPPORTED_TLDS` |
> | `VERCEL_GET_TEAM_MEMBERS` | `VERCEL_LIST_TEAM_MEMBERS` |
> | `VERCEL_GET_V1_SECURITY_FIREWALL_EVENTS` | `VERCEL_LIST_FIREWALL_EVENTS` |
> | `VERCEL_GET_WEBHOOKS` | `VERCEL_LIST_WEBHOOKS` |
> | `VERCEL_INVALIDATE_BY_SRC_IMAGES` | `VERCEL_INVALIDATE_CACHE_BY_SRC_IMAGES` |
> | `VERCEL_INVALIDATE_BY_TAGS` | `VERCEL_INVALIDATE_CACHE_BY_TAGS` |
> | `VERCEL_LIST_ALIASES2` | `VERCEL_LIST_ALIASES` |
> | `VERCEL_LIST_GIT_NAMESPACES` | `VERCEL_GET_GIT_NAMESPACES` |
> | `VERCEL_LIST_PROJECT_DOMAINS` | `VERCEL_GET_PROJECT_DOMAINS` |
> | `VERCEL_LIST_PROMOTE_ALIASES` | `VERCEL_GET_PROMOTE_ALIASES` |
> | `VERCEL_LIST_SHARED_ENV_VARIABLES` | `VERCEL_GET_SHARED_ENV_VARIABLES` |
> | `VERCEL_LIST_USER_EVENTS` | `VERCEL_GET_USER_EVENTS` |
> | `VERCEL_PATCH_DOMAIN` | `VERCEL_UPDATE_DOMAIN` |
> | `VERCEL_PATCH_TEAM` | `VERCEL_UPDATE_TEAM` |
> | `VERCEL_PATCH_URL_PROTECTION_BYPASS` | `VERCEL_UPDATE_URL_PROTECTION_BYPASS` |
> | `VERCEL_PUT_FIREWALL_CONFIG` | `VERCEL_REPLACE_FIREWALL_CONFIG` |
> | `VERCEL_QUERY_ARTIFACT` | `VERCEL_GET_ARTIFACT_INFO` |
> | `VERCEL_REMOVE_PROJECT_DOMAIN2` | `VERCEL_REMOVE_PROJECT_DOMAIN` |
> | `VERCEL_REMOVE_PROJECT_ENV` | `VERCEL_DELETE_PROJECT_ENV` |
> | `VERCEL_REMOVE_RECORD` | `VERCEL_DELETE_DNS_RECORD` |
> | `VERCEL_STATUS` | `VERCEL_GET_CACHE_STATUS` |
> | `VERCEL_UPDATE_EDGE_CONFIG2` | `VERCEL_UPDATE_EDGE_CONFIG` |
> | `VERCEL_VERIFY_PROJECT_DOMAIN2` | `VERCEL_VERIFY_PROJECT_DOMAIN` |

> [accordion] Twitter (36 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `TWITTER_ADD_A_LIST_MEMBER` | `TWITTER_ADD_LIST_MEMBER` |
> | `TWITTER_CREATE_A_NEW_DM_CONVERSATION` | `TWITTER_CREATE_DM_CONVERSATION` |
> | `TWITTER_CREATE_COMPLIANCE_JOB_REQUEST` | `TWITTER_CREATE_COMPLIANCE_JOB` |
> | `TWITTER_FETCH_LIST_MEMBERS_BY_ID` | `TWITTER_GET_LIST_MEMBERS` |
> | `TWITTER_FETCH_SPACE_TICKET_BUYERS_LIST` | `TWITTER_GET_SPACE_TICKET_BUYERS` |
> | `TWITTER_FOLLOW_A_LIST` | `TWITTER_FOLLOW_LIST` |
> | `TWITTER_FULL_ARCHIVE_SEARCH_COUNTS` | `TWITTER_SEARCH_FULL_ARCHIVE_COUNTS` |
> | `TWITTER_GET_A_USER_S_LIST_MEMBERSHIPS` | `TWITTER_GET_USER_LIST_MEMBERSHIPS` |
> | `TWITTER_GET_A_USER_S_OWNED_LISTS` | `TWITTER_GET_USER_OWNED_LISTS` |
> | `TWITTER_GET_A_USER_S_PINNED_LISTS` | `TWITTER_GET_USER_PINNED_LISTS` |
> | `TWITTER_GET_DM_EVENTS_BY_ID` | `TWITTER_GET_DM_EVENT` |
> | `TWITTER_GET_DM_EVENTS_FOR_A_DM_CONVERSATION` | `TWITTER_GET_DM_CONVERSATION_EVENTS` |
> | `TWITTER_GET_USER_S_FOLLOWED_LISTS` | `TWITTER_GET_USER_FOLLOWED_LISTS` |
> | `TWITTER_LIST_LOOKUP_BY_LIST_ID` | `TWITTER_GET_LIST` |
> | `TWITTER_MUTE_USER_BY_USER_ID` | `TWITTER_MUTE_USER` |
> | `TWITTER_PIN_A_LIST` | `TWITTER_PIN_LIST` |
> | `TWITTER_POSTS_LABEL_STREAM` | `TWITTER_STREAM_POST_LABELS` |
> | `TWITTER_POST_USAGE` | `TWITTER_GET_POST_USAGE` |
> | `TWITTER_RECENT_SEARCH_COUNTS` | `TWITTER_SEARCH_RECENT_COUNTS` |
> | `TWITTER_REMOVE_A_BOOKMARKED_POST` | `TWITTER_REMOVE_POST_FROM_BOOKMARKS` |
> | `TWITTER_REMOVE_A_LIST_MEMBER` | `TWITTER_REMOVE_LIST_MEMBER` |
> | `TWITTER_RETRIEVE_COMPLIANCE_JOBS` | `TWITTER_GET_COMPLIANCE_JOBS` |
> | `TWITTER_RETRIEVE_COMPLIANCE_JOB_BY_ID` | `TWITTER_GET_COMPLIANCE_JOB` |
> | `TWITTER_RETRIEVE_POSTS_FROM_A_SPACE` | `TWITTER_GET_SPACE_POSTS` |
> | `TWITTER_RETRIEVE_POSTS_THAT_REPOST_A_POST` | `TWITTER_GET_POST_RETWEETS` |
> | `TWITTER_RETURNS_THE_OPEN_API_SPECIFICATION_DOCUMENT` | `TWITTER_GET_OPENAPI_SPEC` |
> | `TWITTER_SEARCH_FOR_SPACES` | `TWITTER_SEARCH_SPACES` |
> | `TWITTER_SEND_A_NEW_MESSAGE_TO_A_DM_CONVERSATION` | `TWITTER_SEND_DM_TO_CONVERSATION` |
> | `TWITTER_SPACE_LOOKUP_BY_SPACE_ID` | `TWITTER_GET_SPACE_BY_ID` |
> | `TWITTER_SPACE_LOOKUP_BY_THEIR_CREATORS` | `TWITTER_GET_SPACES_BY_CREATORS` |
> | `TWITTER_SPACE_LOOKUP_UP_SPACE_IDS` | `TWITTER_GET_SPACES_BY_IDS` |
> | `TWITTER_UNFOLLOW_A_LIST` | `TWITTER_UNFOLLOW_LIST` |
> | `TWITTER_UNMUTE_USER_BY_USER_ID` | `TWITTER_UNMUTE_USER` |
> | `TWITTER_UNPIN_A_LIST` | `TWITTER_UNPIN_LIST` |
> | `TWITTER_USER_LOOKUP_BY_ID` | `TWITTER_GET_USER_BY_ID` |
> | `TWITTER_USER_LOOKUP_BY_IDS` | `TWITTER_GET_USERS_BY_IDS` |

> [accordion] Google Analytics (25 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `GOOGLE_ANALYTICS_ADMIN_PROPS_DV360_AD_LINKS_LIST` | `GOOGLE_ANALYTICS_LIST_DV360_AD_LINKS` |
> | `GOOGLE_ANALYTICS_ADMIN_PROPS_DV360_LINK_PROPOSALS_LIST` | `GOOGLE_ANALYTICS_LIST_DV360_LINK_PROPOSALS` |
> | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_AUDIENCES_LIST` | `GOOGLE_ANALYTICS_LIST_AUDIENCES` |
> | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_CHANNELGROUPS` | `GOOGLE_ANALYTICS_LIST_CHANNEL_GROUPS` |
> | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_CONVERSIONEVENTS` | `GOOGLE_ANALYTICS_LIST_CONVERSION_EVENTS` |
> | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_CUSTOMDIMENSIONS` | `GOOGLE_ANALYTICS_LIST_CUSTOM_DIMENSIONS` |
> | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_DATASTREAMS` | `GOOGLE_ANALYTICS_LIST_MEASUREMENT_PROTOCOL_SECRETS` |
> | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_DATASTREAMS_LIST` | `GOOGLE_ANALYTICS_LIST_DATA_STREAMS` |
> | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_EXPANDEDDATASETS` | `GOOGLE_ANALYTICS_LIST_EXPANDED_DATA_SETS` |
> | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_FIREBASELINKS` | `GOOGLE_ANALYTICS_LIST_FIREBASE_LINKS` |
> | `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_BIG_QUERY_LINKS` | `GOOGLE_ANALYTICS_LIST_BIGQUERY_LINKS` |
> | `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_GOOGLE_ADS` | `GOOGLE_ANALYTICS_LIST_GOOGLE_ADS_LINKS` |
> | `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_SEARCH_ADS360` | `GOOGLE_ANALYTICS_LIST_SEARCH_ADS360_LINKS` |
> | `GOOGLE_ANALYTICS_GET_PROPERTIES_AUDIENCE_EXPORT` | `GOOGLE_ANALYTICS_GET_AUDIENCE_EXPORT` |
> | `GOOGLE_ANALYTICS_LIST_PROPERTY` | `GOOGLE_ANALYTICS_LIST_PROPERTIES_FILTERED` |
> | `GOOGLE_ANALYTICS_PROPERTIES_AD_SENSE_LINKS_LIST` | `GOOGLE_ANALYTICS_LIST_ADSENSE_LINKS` |
> | `GOOGLE_ANALYTICS_PROPERTIES_AUDIENCEEXPORTS_CREATE` | `GOOGLE_ANALYTICS_CREATE_AUDIENCE_EXPORT` |
> | `GOOGLE_ANALYTICS_PROPERTIES_AUDIENCEEXPORTS_LIST` | `GOOGLE_ANALYTICS_LIST_AUDIENCE_EXPORTS` |
> | `GOOGLE_ANALYTICS_PROPERTIES_CALCULATEDMETRICS_LIST` | `GOOGLE_ANALYTICS_LIST_CALCULATED_METRICS` |
> | `GOOGLE_ANALYTICS_PROPERTIES_DATASTREAMS_EVENTCREATERULES` | `GOOGLE_ANALYTICS_LIST_EVENT_CREATE_RULES` |
> | `GOOGLE_ANALYTICS_PROPERTIES_REPORTINGDATAANNOTATIONS_LIST` | `GOOGLE_ANALYTICS_LIST_REPORTING_DATA_ANNOTATIONS` |
> | `GOOGLE_ANALYTICS_PROPERTIES_REPORT_TASKS_CREATE` | `GOOGLE_ANALYTICS_CREATE_REPORT_TASK` |
> | `GOOGLE_ANALYTICS_PROPERTIES_REPORT_TASKS_LIST` | `GOOGLE_ANALYTICS_LIST_REPORT_TASKS` |
> | `GOOGLE_ANALYTICS_PROPERTIES_SUBPROPERTYEVENTFILTERS_LIST` | `GOOGLE_ANALYTICS_LIST_SUBPROPERTY_EVENT_FILTERS` |
> | `GOOGLE_ANALYTICS_PROPERTIES_SUBPROPERTYSYNCONFIGS_LIST` | `GOOGLE_ANALYTICS_LIST_SUBPROPERTY_SYNC_CONFIGS` |

> [accordion] ClickUp (23 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `CLICKUP_ADD_TAGS_FROM_TIME_ENTRIES` | `CLICKUP_ADD_TAGS_TO_TIME_ENTRIES` |
> | `CLICKUP_CHANGE_TAG_NAMES_FROM_TIME_ENTRIES` | `CLICKUP_UPDATE_TIME_ENTRY_TAG` |
> | `CLICKUP_CLICK_UP_CREATE_DOC` | `CLICKUP_CREATE_DOC` |
> | `CLICKUP_CLICK_UP_GET_DOC_CONTENT` | `CLICKUP_GET_DOC_CONTENT` |
> | `CLICKUP_CLICK_UP_GET_DOC_PAGE_CONTENT` | `CLICKUP_GET_DOC_PAGE_CONTENT` |
> | `CLICKUP_CLICK_UP_SEARCH_DOCS` | `CLICKUP_SEARCH_DOCS` |
> | `CLICKUP_CREATE_FOLDER_LIST_FROM_TEMPLATE` | `CLICKUP_CREATE_LIST_FROM_TEMPLATE` |
> | `CLICKUP_DELETE_A_TIME_ENTRY` | `CLICKUP_DELETE_TIME_ENTRY` |
> | `CLICKUP_EDIT_CHECKLIST` | `CLICKUP_UPDATE_CHECKLIST` |
> | `CLICKUP_EDIT_CHECKLIST_ITEM` | `CLICKUP_UPDATE_CHECKLIST_ITEM` |
> | `CLICKUP_EDIT_GUEST_ON_WORKSPACE` | `CLICKUP_UPDATE_GUEST_ON_WORKSPACE` |
> | `CLICKUP_EDIT_KEY_RESULT` | `CLICKUP_UPDATE_KEY_RESULT` |
> | `CLICKUP_EDIT_SPACE_TAG` | `CLICKUP_UPDATE_SPACE_TAG` |
> | `CLICKUP_EDIT_TIME_TRACKED` | `CLICKUP_UPDATE_TIME_TRACKED` |
> | `CLICKUP_EDIT_USER_ON_WORKSPACE` | `CLICKUP_UPDATE_USER_ON_WORKSPACE` |
> | `CLICKUP_GET_SINGULAR_TIME_ENTRY` | `CLICKUP_GET_TIME_ENTRY` |
> | `CLICKUP_GET_TASK_S_TIME_IN_STATUS` | `CLICKUP_GET_TASK_TIME_IN_STATUS` |
> | `CLICKUP_GET_TIME_ENTRIES_WITHIN_A_DATE_RANGE` | `CLICKUP_GET_TIME_ENTRIES_IN_DATE_RANGE` |
> | `CLICKUP_MOVE_TASK_HOME_LIST` | `CLICKUP_MOVE_TASK_TO_HOME_LIST` |
> | `CLICKUP_SHARED_HIERARCHY` | `CLICKUP_GET_SHARED_HIERARCHY` |
> | `CLICKUP_START_A_TIME_ENTRY` | `CLICKUP_START_TIME_ENTRY` |
> | `CLICKUP_STOP_A_TIME_ENTRY` | `CLICKUP_STOP_TIME_ENTRY` |
> | `CLICKUP_UPDATE_A_TIME_ENTRY` | `CLICKUP_UPDATE_TIME_ENTRY` |

> [accordion] Microsoft Teams (22 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `MICROSOFT_TEAMS_ADD_MEMBER_TO_TEAM` | `MICROSOFT_TEAMS_ADD_TEAM_MEMBER` |
> | `MICROSOFT_TEAMS_CREATE_OPEN_SHIFTS` | `MICROSOFT_TEAMS_CREATE_OPEN_SHIFT` |
> | `MICROSOFT_TEAMS_CREATE_SCHEDULING_GROUPS` | `MICROSOFT_TEAMS_CREATE_SCHEDULING_GROUP` |
> | `MICROSOFT_TEAMS_CREATE_TEAM_SCHEDULE_SHIFT` | `MICROSOFT_TEAMS_CREATE_SHIFT` |
> | `MICROSOFT_TEAMS_DELETE_TEAM_SCHEDULE_SHIFT` | `MICROSOFT_TEAMS_DELETE_SHIFT` |
> | `MICROSOFT_TEAMS_DELETE_TEAM_SCHEDULING_GROUP` | `MICROSOFT_TEAMS_DELETE_SCHEDULING_GROUP` |
> | `MICROSOFT_TEAMS_GET_INSTALLED_APP` | `MICROSOFT_TEAMS_GET_TEAMS_APP_DEFINITION` |
> | `MICROSOFT_TEAMS_GET_TEAM` | `MICROSOFT_TEAMS_GET_TEAM_FROM_GROUP` |
> | `MICROSOFT_TEAMS_GET_USER_CHAT_MEMBER` | `MICROSOFT_TEAMS_GET_CHAT_MEMBER` |
> | `MICROSOFT_TEAMS_GET_USER_PRESENCE` | `MICROSOFT_TEAMS_GET_PRESENCE` |
> | `MICROSOFT_TEAMS_LIST_CHANNEL_MESSAGE_REPLIES` | `MICROSOFT_TEAMS_LIST_MESSAGE_REPLIES` |
> | `MICROSOFT_TEAMS_LIST_TEAMS_PERMISSION_GRANTS` | `MICROSOFT_TEAMS_LIST_TEAM_PERMISSION_GRANTS` |
> | `MICROSOFT_TEAMS_LIST_TEAMS_SCHEDULE_DAY_NOTES` | `MICROSOFT_TEAMS_LIST_SCHEDULE_DAY_NOTES` |
> | `MICROSOFT_TEAMS_LIST_TEAMS_TEMPLATES` | `MICROSOFT_TEAMS_LIST_TEAM_TEMPLATES` |
> | `MICROSOFT_TEAMS_LIST_TIMES_OFF` | `MICROSOFT_TEAMS_LIST_TIME_OFF` |
> | `MICROSOFT_TEAMS_LIST_USER_CHATS_MEMBERS` | `MICROSOFT_TEAMS_LIST_USER_CHAT_MEMBERS` |
> | `MICROSOFT_TEAMS_SEND_ACTIVITY_NOTIFICATION_TO_RECIPIENTS` | `MICROSOFT_TEAMS_SEND_ACTIVITY_NOTIFICATION` |
> | `MICROSOFT_TEAMS_SET_ME_PRESENCE_USER_PREFERRED` | `MICROSOFT_TEAMS_SET_ME_PREFERRED_PRESENCE` |
> | `MICROSOFT_TEAMS_TEAMS_GET_MESSAGE` | `MICROSOFT_TEAMS_GET_CHANNEL_MESSAGE` |
> | `MICROSOFT_TEAMS_TEAMS_LIST_PEOPLE` | `MICROSOFT_TEAMS_LIST_PEOPLE` |
> | `MICROSOFT_TEAMS_TEAMS_POST_MESSAGE_REPLY` | `MICROSOFT_TEAMS_POST_MESSAGE_REPLY` |
> | `MICROSOFT_TEAMS_UPDATE_CALLS_OPERATIONS` | `MICROSOFT_TEAMS_UPDATE_CALL_OPERATION` |

> [accordion] One Drive (21 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `ONE_DRIVE_CHECKOUT_DRIVE_ITEM` | `ONE_DRIVE_CHECKOUT_ITEM` |
> | `ONE_DRIVE_CHECK_IN_DRIVE_ITEM` | `ONE_DRIVE_CHECKIN_ITEM` |
> | `ONE_DRIVE_CREATE_DRIVES_ITEMS_PERMISSIONS` | `ONE_DRIVE_CREATE_ITEM_PERMISSION` |
> | `ONE_DRIVE_DELETE_DRIVE_FOLLOWING` | `ONE_DRIVE_UNFOLLOW_ITEM` |
> | `ONE_DRIVE_DELETE_DRIVE_ITEMS_PERMISSIONS` | `ONE_DRIVE_DELETE_ITEM_PERMISSION` |
> | `ONE_DRIVE_DELETE_DRIVE_ITEM_PERMANENTLY` | `ONE_DRIVE_DELETE_ITEM_PERMANENTLY` |
> | `ONE_DRIVE_DELETE_SHARES_PERMISSION` | `ONE_DRIVE_DELETE_SHARE_PERMISSION` |
> | `ONE_DRIVE_DOWNLOAD_DRIVE_ITEM_VERSION_CONTENT` | `ONE_DRIVE_DOWNLOAD_ITEM_VERSION` |
> | `ONE_DRIVE_FOLLOW_DRIVE_ITEM` | `ONE_DRIVE_FOLLOW_ITEM` |
> | `ONE_DRIVE_GET_DRIVES_FOLLOWING` | `ONE_DRIVE_GET_FOLLOWED_ITEM` |
> | `ONE_DRIVE_GET_DRIVE_ROOT` | `ONE_DRIVE_GET_ROOT` |
> | `ONE_DRIVE_GET_DRIVE_SPECIAL_FOLDER` | `ONE_DRIVE_GET_SPECIAL_FOLDER` |
> | `ONE_DRIVE_GET_SHARES` | `ONE_DRIVE_GET_SHARE` |
> | `ONE_DRIVE_GET_SITE_DETAILS` | `ONE_DRIVE_GET_SITE` |
> | `ONE_DRIVE_GRANT_SHARES_PERMISSION` | `ONE_DRIVE_GRANT_SHARE_PERMISSION` |
> | `ONE_DRIVE_INVITE_USER_TO_DRIVE_ITEM` | `ONE_DRIVE_INVITE_USER_TO_ITEM` |
> | `ONE_DRIVE_LIST_DRIVES_BUNDLES` | `ONE_DRIVE_LIST_BUNDLES` |
> | `ONE_DRIVE_LIST_DRIVE_ACTIVITIES` | `ONE_DRIVE_LIST_ACTIVITIES` |
> | `ONE_DRIVE_LIST_DRIVE_ITEM_ACTIVITIES` | `ONE_DRIVE_LIST_ITEM_ACTIVITIES` |
> | `ONE_DRIVE_LIST_SHARES_PERMISSION` | `ONE_DRIVE_LIST_SHARE_PERMISSIONS` |
> | `ONE_DRIVE_LIST_SITE_DRIVE_ITEMS_DELTA` | `ONE_DRIVE_LIST_SITE_ITEMS_DELTA` |

> [accordion] Dropbox (18 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `DROPBOX_ADD_MEMBERS_TO_TEAM_GROUP` | `DROPBOX_ADD_TEAM_GROUP_MEMBERS` |
> | `DROPBOX_ADD_PROPERTY_TEMPLATE_FOR_TEAM` | `DROPBOX_ADD_TEAM_PROPERTIES_TEMPLATE` |
> | `DROPBOX_ADD_SECONDARY_EMAILS_TO_TEAM_MEMBERS` | `DROPBOX_ADD_TEAM_MEMBERS_SECONDARY_EMAILS` |
> | `DROPBOX_COPY_REFERENCE_SAVE` | `DROPBOX_SAVE_COPY_REFERENCE` |
> | `DROPBOX_CREATE_PAPER` | `DROPBOX_CREATE_PAPER_DOCUMENT` |
> | `DROPBOX_GET_PROPERTY_TEMPLATE_FOR_TEAM` | `DROPBOX_GET_TEAM_PROPERTIES_TEMPLATE` |
> | `DROPBOX_GET_TEAM_MEMBERS_ADD_JOB_STATUS_V2` | `DROPBOX_GET_TEAM_MEMBERS_ADD_JOB_STATUS` |
> | `DROPBOX_LIST_MEMBERS_LINKED_APPS` | `DROPBOX_LIST_TEAM_LINKED_APPS` |
> | `DROPBOX_LIST_MEMBER_SPACE_LIMITS_EXCLUDED_USERS_CONTINUE` | `DROPBOX_LIST_EXCLUDED_USERS_CONTINUE` |
> | `DROPBOX_LIST_TEAM_GROUP_MEMBERS_CONTINUE` | `DROPBOX_LIST_TEAM_GROUPS_MEMBERS_CONTINUE` |
> | `DROPBOX_LIST_TEAM_MEMBERS_CONTINUE_V2` | `DROPBOX_LIST_TEAM_MEMBERS_CONTINUE` |
> | `DROPBOX_REMOVE_MEMBER_SPACE_LIMITS_EXCLUDED_USERS` | `DROPBOX_REMOVE_TEAM_MEMBER_SPACE_LIMITS_EXCLUDED_USERS` |
> | `DROPBOX_SET_GROUP_MEMBER_ACCESS_TYPE` | `DROPBOX_UPDATE_GROUP_MEMBER_ACCESS_TYPE` |
> | `DROPBOX_SET_TEAM_MEMBER_ADMIN_PERMISSIONS` | `DROPBOX_UPDATE_TEAM_MEMBER_ADMIN_PERMISSIONS` |
> | `DROPBOX_SET_TEAM_MEMBER_PROFILE` | `DROPBOX_UPDATE_TEAM_MEMBER_PROFILE` |
> | `DROPBOX_SET_TEAM_MEMBER_PROFILE_PHOTO` | `DROPBOX_UPDATE_TEAM_MEMBER_PROFILE_PHOTO` |
> | `DROPBOX_UPDATE_FOLDER_MEMBER_ACTION` | `DROPBOX_UPDATE_FOLDER_MEMBER` |
> | `DROPBOX_UPLOAD_SESSION_APPEND_BATCH` | `DROPBOX_APPEND_UPLOAD_SESSION_BATCH` |

> [accordion] Google Drive (15 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `GOOGLEDRIVE_DELETE_CHILD_V2` | `GOOGLEDRIVE_DELETE_CHILD` |
> | `GOOGLEDRIVE_DELETE_PARENT_V2` | `GOOGLEDRIVE_DELETE_PARENT` |
> | `GOOGLEDRIVE_DELETE_PROPERTY_V2` | `GOOGLEDRIVE_DELETE_PROPERTY` |
> | `GOOGLEDRIVE_FILES_MODIFY_LABELS` | `GOOGLEDRIVE_MODIFY_FILE_LABELS` |
> | `GOOGLEDRIVE_GET_CHANGE_V2` | `GOOGLEDRIVE_GET_CHANGE` |
> | `GOOGLEDRIVE_GET_CHILD_V2` | `GOOGLEDRIVE_GET_CHILD` |
> | `GOOGLEDRIVE_GET_PARENT_V2` | `GOOGLEDRIVE_GET_PARENT` |
> | `GOOGLEDRIVE_GET_PROPERTY_V2` | `GOOGLEDRIVE_GET_FILE_PROPERTY` |
> | `GOOGLEDRIVE_INSERT_CHILD_V2` | `GOOGLEDRIVE_INSERT_CHILD` |
> | `GOOGLEDRIVE_INSERT_PARENT_V2` | `GOOGLEDRIVE_ADD_PARENT` |
> | `GOOGLEDRIVE_INSERT_PROPERTY_V2` | `GOOGLEDRIVE_ADD_PROPERTY` |
> | `GOOGLEDRIVE_LIST_PROPERTIES_V2` | `GOOGLEDRIVE_LIST_FILE_PROPERTIES` |
> | `GOOGLEDRIVE_LIST_REPLIES_TO_COMMENT` | `GOOGLEDRIVE_LIST_REPLIES` |
> | `GOOGLEDRIVE_PATCH_PROPERTY_V2` | `GOOGLEDRIVE_PATCH_PROPERTY` |
> | `GOOGLEDRIVE_UPDATE_PROPERTY_V2` | `GOOGLEDRIVE_UPDATE_FILE_PROPERTY` |

> [accordion] Firecrawl (11 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `FIRECRAWL_BATCH_SCRAPE_DELETE` | `FIRECRAWL_BATCH_SCRAPE_CANCEL` |
> | `FIRECRAWL_CANCEL_AGENT` | `FIRECRAWL_AGENT_CANCEL` |
> | `FIRECRAWL_CANCEL_A_CRAWL_JOB` | `FIRECRAWL_CRAWL_CANCEL` |
> | `FIRECRAWL_CRAWL_ACTIVE` | `FIRECRAWL_CRAWL_LIST_ACTIVE` |
> | `FIRECRAWL_CREDIT_USAGE` | `FIRECRAWL_CREDIT_USAGE_GET` |
> | `FIRECRAWL_CREDIT_USAGE_HISTORICAL` | `FIRECRAWL_CREDIT_USAGE_GET_HISTORICAL` |
> | `FIRECRAWL_GENERATE_LLMS_TXT` | `FIRECRAWL_LLMS_TXT_GENERATE` |
> | `FIRECRAWL_GET_LLMS_TXT_STATUS` | `FIRECRAWL_LLMS_TXT_GET` |
> | `FIRECRAWL_QUEUE_STATUS` | `FIRECRAWL_QUEUE_GET` |
> | `FIRECRAWL_TOKEN_USAGE` | `FIRECRAWL_TOKEN_USAGE_GET` |
> | `FIRECRAWL_TOKEN_USAGE_HISTORICAL` | `FIRECRAWL_TOKEN_USAGE_GET_HISTORICAL` |

> [accordion] Jira (11 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `JIRA_CREATE_PERMISSIONS_CHECK` | `JIRA_CHECK_PERMISSIONS` |
> | `JIRA_EVALUATE_JSIS_JIRA_EXPRESSION` | `JIRA_EVALUATE_JIRA_EXPRESSION` |
> | `JIRA_GET_AVATAR_SYSTEM` | `JIRA_GET_SYSTEM_AVATARS` |
> | `JIRA_GET_COMPONENT` | `JIRA_GET_COMPONENTS` |
> | `JIRA_GET_CREATE_METADATA_ISSUE_CREATEMETA` | `JIRA_GET_ISSUE_CREATE_METADATA` |
> | `JIRA_GET_CUSTOM_FIELDS_PAGINATED` | `JIRA_GET_FIELDS_PAGINATED` |
> | `JIRA_GET_DASHBOARD` | `JIRA_GET_DASHBOARDS` |
> | `JIRA_GET_FILTER_FAVOURITE` | `JIRA_GET_FAVORITE_FILTERS` |
> | `JIRA_GET_ISSUE_EDIT_META` | `JIRA_GET_ISSUE_EDIT_METADATA` |
> | `JIRA_GET_ISSUE_PICKER` | `JIRA_GET_ISSUE_PICKER_SUGGESTIONS` |
> | `JIRA_LIST_COMMENT_LIST` | `JIRA_LIST_COMMENTS` |

> [accordion] Asana (5 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `ASANA_ADD_MEMBERS_FOR_PROJECT` | `ASANA_ADD_MEMBERS_TO_PROJECT` |
> | `ASANA_ADD_USER_FOR_TEAM` | `ASANA_ADD_USER_TO_TEAM` |
> | `ASANA_ADD_USER_FOR_WORKSPACE` | `ASANA_ADD_USER_TO_WORKSPACE` |
> | `ASANA_GET_PROJECT_MEMBERSHIPS_FOR_PROJECT` | `ASANA_GET_PROJECT_MEMBERSHIPS` |
> | `ASANA_GET_TASKS_FROM_A_SECTION` | `ASANA_GET_TASKS_FROM_SECTION` |

> [accordion] Icypeas (5 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `ICYPEAS_FIND_LINKED_IN_PROFILE_BY_EMAIL` | `ICYPEAS_FIND_LINKEDIN_PROFILE_BY_EMAIL` |
> | `ICYPEAS_FIND_PROFILE_URLS_BULK` | `ICYPEAS_BULK_FIND_PROFILE_URLS` |
> | `ICYPEAS_PERFORM_BULK_REVERSE_EMAIL_LOOKUP` | `ICYPEAS_BULK_REVERSE_EMAIL_LOOKUP` |
> | `ICYPEAS_SCRAPE_BULK` | `ICYPEAS_BULK_SCRAPE` |
> | `ICYPEAS_STATISTICS_BULK_SEARCH` | `ICYPEAS_PARSE_BULK_SEARCH_STATISTICS` |

> [accordion] Attio (4 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `ATTIO_DELETE_LIST_ENTRY` | `ATTIO_DELETE_ENTRY` |
> | `ATTIO_GET_V2_OBJECTS_OBJECT_RECORDS_RECORD_ID_ENTRIES` | `ATTIO_GET_RECORD_ENTRIES` |
> | `ATTIO_GET_V2_SELF` | `ATTIO_GET_SELF` |
> | `ATTIO_PATCH_V2_TARGET_IDENTIFIER_ATTRIBUTES_ATTRIBUTE` | `ATTIO_UPDATE_ATTRIBUTE` |

> [accordion] Linear (3 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `LINEAR_CREATE_LINEAR_ATTACHMENT` | `LINEAR_CREATE_ATTACHMENT` |
> | `LINEAR_CREATE_LINEAR_ISSUE_DETAILS` | `LINEAR_GET_ISSUE_DEFAULTS` |
> | `LINEAR_GET_ATTACHMENTS` | `LINEAR_GET_ATTACHMENT` |

> [accordion] PeopleDataLabs (3 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `PEOPLEDATALABS_AUTOCOMPLETE_FIELD_SUGGESTIONS` | `PEOPLEDATALABS_GET_AUTOCOMPLETE_SUGGESTIONS` |
> | `PEOPLEDATALABS_COMPANY_SEARCH_ELASTIC` | `PEOPLEDATALABS_SEARCH_COMPANY_ELASTIC` |
> | `PEOPLEDATALABS_GENERATE_SEARCH_QUERY_ACTION` | `PEOPLEDATALABS_GENERATE_SEARCH_QUERY` |

> [accordion] Gmail (2 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `GMAIL_TRASH_THREAD` | `GMAIL_MOVE_THREAD_TO_TRASH` |
> | `GMAIL_UPDATE_POP` | `GMAIL_UPDATE_POP_SETTINGS` |

> [accordion] Google Calendar (2 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `GOOGLECALENDAR_LIST_ACL_RULES` | `GOOGLECALENDAR_ACL_LIST` |
> | `GOOGLECALENDAR_UPDATE_ACL_RULE` | `GOOGLECALENDAR_ACL_UPDATE` |

> [accordion] Reddit (2 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `REDDIT_GET_CONTROVERSIAL` | `REDDIT_GET_CONTROVERSIAL_POSTS` |
> | `REDDIT_SEND_REDDIT_REPLIES` | `REDDIT_TOGGLE_INBOX_REPLIES` |

> [accordion] YouTube (2 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `YOUTUBE_INSERT_CHANNEL_SECTION` | `YOUTUBE_CREATE_CHANNEL_SECTION` |
> | `YOUTUBE_INSERT_COMMENT` | `YOUTUBE_CREATE_COMMENT_REPLY` |

> [accordion] Apollo (1 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `APOLLO_CREATE_APOLLO_TASK2` | `APOLLO_CREATE_TASK` |

> [accordion] Facebook (1 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `FACEBOOK_ADD_REACTION` | `FACEBOOK_LIKE_POST_OR_COMMENT` |

> [accordion] Google Docs (1 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `GOOGLEDOCS_GET_CHARTS_FROM_SPREADSHEET` | `GOOGLEDOCS_LIST_SPREADSHEET_CHARTS` |

> [accordion] Google Sheets (1 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `GOOGLESHEETS_SPREADSHEETS_VALUES_BATCH_CLEAR_BY_DATA_FILTER` | `GOOGLESHEETS_BATCH_CLEAR_VALUES_BY_DATA_FILTER` |

> [accordion] Hyperbrowser (1 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `HYPERBROWSER_GET_PROFILE_BY_ID` | `HYPERBROWSER_GET_PROFILE` |

> [accordion] Telegram (1 renamed)
>
> | Old Enum | New Enum |
> | - | - |
> | `TELEGRAM_EXPORT_CHAT_INVITE_LINK` | `TELEGRAM_CREATE_CHAT_INVITE_LINK` |

## Migration

If you are using `latest` toolkit versions or fetching tools dynamically, no action is required.

If you reference tool enums by name in your code:

1. **Deprecated tools** — update to the replacement listed above at your convenience. The old enum still works but will show a deprecation notice.
2. **Removed tools** — switch to the canonical tool for that operation. The removed tool's functionality is fully covered.
3. **Renamed enums** — update any hardcoded enum strings to the new names.

**Mar 25, 2026**

Deprecated mcp.composio.dev endpoint permanently removed; traffic redirects to composio.dev/toolkits

## mcp.composio.dev Deprecated Endpoint Removed

We've permanently removed the deprecated `mcp.composio.dev` endpoint that was deprecated in November 2025.

This endpoint was part of our early MCP integration experiments and the latest MCP offering from Composio is [Composio For You](https://dashboard.composio.dev/~/org/connect?utm_source=docs\&utm_medium=content\&utm_campaign=changelog-03-25-26-mcp-endpoint-removed) (access 1000+ apps through one MCP).

### What Changed

* All traffic to `mcp.composio.dev` web page now redirects to [composio.dev/toolkits](https://composio.dev/toolkits)
* The underlying service has been fully decommissioned
* No action needed if you're using our current MCP

### Migrating?

If you were still using the old endpoint, head to [https://dashboard.composio.dev/\~/org/connect](https://dashboard.composio.dev/~/org/connect?utm_source=docs\&utm_medium=content\&utm_campaign=changelog-03-25-26-mcp-endpoint-removed) to get started with the new MCP.

Questions? Reach out to [support@composio.dev](mailto:support@composio.dev)

**Mar 23, 2026**

Define local tools that run in-process alongside remote Composio tools in sessions

## Custom Tools and Toolkits (Experimental)

You can now create custom tools and toolkits that run locally alongside remote Composio tools within a session.

### SDK Version

| Package | Version |
| - | - |
| @composio/core | v0.6.6 |
| composio | v0.11.4 |

***

## What's New

Custom tools support three patterns — standalone tools for internal logic, extension tools that wrap Composio toolkit APIs with business logic, and custom toolkits that group related tools. TypeScript uses builder functions with Zod schemas; Python uses decorators with Pydantic annotations.

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio, experimental_createTool, experimental_createToolkit } from "@composio/core";
> import { z } from "zod/v3";
>
> // Standalone tool — internal data, no Composio auth needed
> const getUserProfile = experimental_createTool("GET_USER_PROFILE", {
>   name: "Get user profile",
>   description: "Retrieve the current user's profile from the internal directory",
>   inputParams: z.object({}),
>   execute: async (_input, ctx) => {
>     // ctx.userId identifies which user's session is running
>     const profiles: Record<string, { name: string; tier: string }> = {
>       "user_1": { name: "Alice Johnson", tier: "enterprise" },
>     };
>     return profiles[ctx.userId] ?? {};
>   },
> });
>
> // Extension tool — wraps Gmail with preset business logic
> // Inherits auth from the session via extendsToolkit
> const sendPromoEmail = experimental_createTool("SEND_PROMO_EMAIL", {
>   name: "Send promo email",
>   description: "Send the standard promotional email to a recipient",
>   extendsToolkit: "gmail",
>   inputParams: z.object({ to: z.string().describe("Recipient email") }),
>   execute: async (input, ctx) => {
>     const raw = btoa(`To: ${input.to}\r\nSubject: Try MyApp Pro\r\n\r\nFree for 14 days.`);
>     const res = await ctx.proxyExecute({
>       toolkit: "gmail",
>       endpoint: "https://gmail.googleapis.com/gmail/v1/users/me/messages/send",
>       method: "POST",
>       body: { raw },
>     });
>     return { status: res.status, to: input.to };
>   },
> });
>
> // Custom toolkit — groups related tools under a namespace
> const userManagement = experimental_createToolkit("USER_MANAGEMENT", {
>   name: "User scoping",
>   description: "Manage user roles and permissions",
>   tools: [
>     experimental_createTool("ASSIGN_ROLE", {
>       name: "Assign role",
>       description: "Assign a role to a user in the internal system",
>       inputParams: z.object({
>         user_id: z.string().describe("Target user ID"),
>         role: z.enum(["admin", "editor", "viewer"]).describe("Role to assign"),
>       }),
>       execute: async ({ user_id, role }) => ({ user_id, role, assigned: true }),
>     }),
>   ],
> });
>
> // Bind everything to a session
> const composio = new Composio({ apiKey: "your_api_key" });
> const session = await composio.create("user_1", {
>   toolkits: ["gmail"],
>   experimental: {
>     customTools: [getUserProfile, sendPromoEmail],
>     customToolkits: [userManagement],
>   },
> });
>
> const tools = await session.tools(); // Includes both remote and custom tools
> ```

> [tab] Python
>
> ```python theme={null}
> import base64
>
> from pydantic import BaseModel, Field
>
> from composio import Composio
>
> composio = Composio(api_key="your_api_key")
>
> class UserLookupInput(BaseModel):
>     user_id: str = Field(description="User ID")
>
> @composio.experimental.tool()
> def get_user_profile(input: UserLookupInput, ctx):
>     """Retrieve the current user's profile from the internal directory."""
>     profiles = {
>         "user_1": {"name": "Alice Johnson", "tier": "enterprise"},
>     }
>     return profiles.get(input.user_id, {})
>
> class PromoEmailInput(BaseModel):
>     to: str = Field(description="Recipient email")
>
> @composio.experimental.tool(extends_toolkit="gmail")
> def send_promo_email(input: PromoEmailInput, ctx):
>     """Send the standard promotional email to a recipient."""
>     raw = base64.urlsafe_b64encode(
>         (
>             f"To: {input.to}\r\n"
>             "Subject: Try MyApp Pro\r\n"
>             "Content-Type: text/plain; charset=UTF-8\r\n\r\n"
>             "Free for 14 days."
>         ).encode()
>     ).decode().rstrip("=")
>     res = ctx.proxy_execute(
>         toolkit="gmail",
>         endpoint="https://gmail.googleapis.com/gmail/v1/users/me/messages/send",
>         method="POST",
>         body={"raw": raw},
>     )
>     return {"status": res.status, "to": input.to}
>
> user_management = composio.experimental.Toolkit(
>     slug="USER_MANAGEMENT",
>     name="User scoping",
>     description="Manage user roles and permissions",
> )
>
> class AssignRoleInput(BaseModel):
>     user_id: str = Field(description="Target user ID")
>     role: str = Field(description="Role to assign")
>
> @user_management.tool()
> def assign_role(input: AssignRoleInput, ctx):
>     """Assign a role to a user in the internal system."""
>     return {"user_id": input.user_id, "role": input.role, "assigned": True}
>
> session = composio.create(
>     user_id="user_1",
>     toolkits=["gmail"],
>     experimental={
>         "custom_tools": [get_user_profile, send_promo_email],
>         "custom_toolkits": [user_management],
>     },
> )
>
> tools = session.tools()  # Includes both remote and custom tools
> ```

### SessionContext

Every custom tool's `execute` receives `(input, ctx)`:

* **TypeScript** — `ctx.userId`, `ctx.proxyExecute(params)`, `ctx.execute(toolSlug, args)`
* **Python** — `ctx.user_id`, `ctx.proxy_execute(...)`, `ctx.execute(tool_slug, arguments)`

***

## Limitations

* **Native tools only** — custom tools work with `session.tools()`. MCP support is coming soon.
* **Experimental API** — the custom tool APIs and session `experimental` option may change.
* **SDK-specific DX is intentional** — TypeScript uses builder helpers and Zod. Python uses decorators, docstrings, and Pydantic annotations.

**Mar 13, 2026**

Interactive org/project picker, --no-wait for link, and whoami no longer exposes API keys Existing customers keep 1-minute polling until May 1. New triggers default to 15 minutes.

## CLI Improvements: Login, Link, and Whoami

This release improves the Composio CLI with a better login flow, a non-blocking link option, and improved security for the whoami command.

### CLI Version

| Package | Version |
| - | - |
| @composio/cli | v0.2.2 |

***

## What's New

### Interactive Org/Project Picker After Login

`composio login` now prompts you to select your default organization and project after the browser OAuth flow completes.

* **Default behavior**: After login, you see an interactive picker to choose your org and project. If you have only one org and one project, they are auto-selected.
* **With `-y`**: Skip the picker and use the session defaults (e.g. for CI or scripts).

```bash theme={null}
composio login           # Login, then pick org/project
composio login -y        # Login, use session defaults (no picker)
composio login --no-browser  # Print URL, don't open browser
```

### Non-Interactive Link with `--no-wait`

`composio link` now supports a `--no-wait` flag for non-blocking authorization flows.

* **Default**: Opens the browser and waits until the connected account is ACTIVE.
* **With `--no-wait`**: Prints link info and JSON to stdout (JQ-parseable) and exits immediately. Useful for scripts and CI.

```bash theme={null}
composio link github              # Opens browser, waits for completion
composio link github --no-wait    # Prints redirect URL and JSON, exits
```

### Whoami No Longer Exposes API Keys

The `composio whoami` command no longer displays API keys in the output. This improves security and reduces the risk of accidental exposure in logs or screenshots.

* API key is removed from both display and JSON output.
* Hints for `composio manage orgs switch` and `composio init` are shown instead.

***

## Breaking Changes

### Removed Flags from Login and Init

The following flags have been removed from `composio login` and `composio init`:

* `--api-key`
* `--org-id`
* `--project-id`

> [!WARNING]
>
> **Breaking Change**
>
> If you previously used `composio login --api-key uak_xxx --org-id X --project-id Y` for non-interactive login (e.g. in CI), you must use the browser-based flow instead. Use `composio login -y` to skip the org/project picker and accept session defaults.
>
> For `composio init`, the `--org-id` and `--project-id` flags are removed. Use `composio init` interactively, or run `composio login` first and then `composio init`.

**Before:**

```bash theme={null}
composio login --api-key uak_xxx --org-id org_123 --project-id proj_456
composio init --org-id org_123 --project-id proj_456
```

**After:**

```bash theme={null}
composio login -y        # Login with session defaults (no picker)
composio init            # Interactive project selection
```

***

## Improvements

* **Login JSON output**: When using the org/project picker, the JSON output now reflects the final selection (not the initial session state).
* **Picker error handling**: If the org/project picker fails (e.g. API error), the CLI shows a warning, emits JSON with session data, and displays hints so you are not left without guidance.
* **Modularized org/project selection**: The selection logic is shared between `composio login` and `composio manage orgs switch`.

## Polling Intervals: Transition Period for Existing Customers

We're allowing a **transition period** before enforcing the new polling interval limits.

## Timeline

* **Until May 1, 2026** — Existing customers continue to get 1-minute polling on all their triggers, including newly created ones.
* **From May 1, 2026** — All triggers move to a **15-minute default** polling interval. App-specific overrides will be available for apps with favorable rate limits.

If any of your triggers were affected by the recent changes, we've restored them to their original intervals.

## Why 15 Minutes?

Composio-managed OAuth apps share rate limits across all users. At scale, 1-minute polling causes rate limiting and service degradation. The 15-minute minimum ensures reliability for everyone.

## How to Keep 1-Minute Polling

Set up **your own OAuth app**. With custom auth:

* Intervals as low as 1 minute
* Your own rate limits
* No platform limits, ever

> [!WARNING]
>
> OAuth approval from Google, Microsoft, etc. takes **days to weeks**. Start now.

→ [Set up your own OAuth app](https://composio-preview.mintlify.site/docs/authentication/custom-app-vs-managed-app.md)

**Mar 11, 2026**

Default polling interval increasing from 1 minute to 15 minutes, with silent clamping during transition

## Polling Trigger Interval Changes

> [!WARNING]
>
> **Update (March 13, 2026):** Existing customers have a transition period until May 1, 2026. See [updated changelog](https://composio-preview.mintlify.site/docs/changelog/2026/03/13).

We're updating **polling trigger intervals** to improve platform reliability and avoid rate limiting. This change affects how frequently polling triggers execute.

## What's Changing?

### Default Polling Interval

The default polling interval for triggers is increasing from **1 minute** to **15 minutes**.

If you don't specify an `interval` in your trigger configuration, your triggers will now poll every 15 minutes instead of every 1 minute.

### Minimum Polling Interval

A new **minimum polling interval of 15 minutes** is being introduced. Triggers configured with intervals shorter than 15 minutes will be automatically clamped to 15 minutes.

```python theme={null}
# Before: this would poll every 5 minutes
composio.triggers.enable(
    trigger_name="GMAIL_NEW_GMAIL_MESSAGE",
    connected_account_id="ca_xxx",
    config={"interval": 5}
)

# Now: interval is silently clamped to 15 minutes
composio.triggers.enable(
    trigger_name="GMAIL_NEW_GMAIL_MESSAGE",
    connected_account_id="ca_xxx",
    config={"interval": 5}  # Effective interval: 15 minutes
)
```

### Current Behavior (Transition Period)

During the transition period, intervals below the minimum are **silently clamped** — your triggers will continue to work without errors, but they will run at the minimum interval instead of your requested interval.

### Enforcement (April 15, 2026)

Starting **April 15, 2026**, requesting an interval below the minimum will return an **API error** instead of silently clamping. Update your trigger configurations to use an interval of 15 minutes or higher before this date.

```python theme={null}
# This will return an error after April 15, 2026
composio.triggers.enable(
    trigger_name="GMAIL_NEW_GMAIL_MESSAGE",
    connected_account_id="ca_xxx",
    config={"interval": 5}  # Error: interval must be >= 15 minutes
)
```

### App-Level Interval Overrides

We will also be introducing **app-specific default polling intervals**. Each app will have its own default interval based on the rate limits that app allows and whether the rate limit is per-user or per-app. These app-level defaults may be lower or higher than 15 minutes depending on the app. When you don't specify an `interval`, the app-level default will be used instead of the global 15-minute default.

### Need Intervals Below 15 Minutes?

If you require polling intervals shorter than 15 minutes, you should **use your own OAuth app** (custom auth). With custom auth, the 15-minute minimum does not apply — you can set polling intervals as low as **1 minute**.

## What You Need to Do

1. **Review your trigger configurations** — check if any triggers use intervals shorter than 15 minutes
2. **Update intervals** to 15 minutes or higher before **April 15, 2026**
3. **If you need near-real-time events**, consider using **webhook triggers** instead of polling triggers, or use **custom auth** for intervals as low as 1 minute

## Rollout Timeline

* **March 11, 2026**: Silent clamping enabled — intervals below 15 minutes are automatically raised to 15 minutes
* **April 15, 2026**: API enforcement — intervals below 15 minutes will return an error
* **April 15, 2026**: Dashboard enforcement — the UI will prevent setting intervals below 15 minutes

> [!NOTE]
>
> Existing triggers with intervals below 15 minutes will continue to function during the transition period, but at the clamped 15-minute interval. Update your configurations before April 15 to avoid errors.

**Mar 4, 2026**

Organizations created on or after March 5, 2026 will have require\_mcp\_api\_key enabled by default

## MCP API Key Authentication Enabled by Default for New Orgs

As announced in our [Optional API Key Enforcement for MCP Servers](https://composio-preview.mintlify.site/docs/changelog/2026/01/08) entry, **MCP API key enforcement is now enabled by default for all newly created organizations**.

### What's Changed

From **March 5, 2026**, all projects in newly created organizations will have `require_mcp_api_key` set to `true` by default. Any MCP server request without a valid `x-api-key` header will be rejected with `401 Unauthorized`.

| Setting | Previous Default | New Default (orgs created March 5+) |
| - | - | - |
| `require_mcp_api_key` | `false` | `true` |

### For New Organizations

* You can opt out by setting `require_mcp_api_key: false` in your project configuration

### For Existing Organizations

Nothing changes for existing organizations. If your organization was created before March 5, 2026:

* Your current `require_mcp_api_key` setting remains unchanged
* You can opt in at any time through your [project settings](https://dashboard.composio.dev?utm_source=docs\&utm_medium=content\&utm_campaign=changelog-03-04-26-mcp-api-key-default-new-orgs) or via the API

### Opting Out (New Organizations)

If you need to disable API key enforcement, set `require_mcp_api_key: false` during project creation or update it afterward:

```bash theme={null}
curl -X PATCH https://backend.composio.dev/api/v3/org/project/config \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{"require_mcp_api_key": false}'
```

> [!NOTE]
>
> We strongly recommend keeping MCP API key enforcement enabled to prevent unauthorized access to your MCP servers. See the [original announcement](https://composio-preview.mintlify.site/docs/changelog/2026/01/08) for setup details and usage examples.

**Feb 23, 2026**

Tools backed by deprecated upstream API endpoints are now marked as deprecated Dead services and duplicate toolkit variants have been deprecated

## 230+ Deprecated Tools Now Flagged Across 70+ Apps

**Toolkit version:** `20260225_00` for all affected toolkits

Tools with deprecated upstream API endpoints are now properly flagged with `deprecated = True`. This covers \~230 tools across 70+ apps — identified by cross-referencing official API documentation.

### All Deprecated Tools

<details>
  <summary>Click to expand full list by app (230+ tools)</summary>

  **Accredible Certificates**
  `ACCREDIBLE_CERTIFICATES_LIST_CREDENTIALS`, `ACCREDIBLE_CERTIFICATES_LIST_GROUPS`, `ACCREDIBLE_CERTIFICATES_SEARCH_CREDENTIALS`

  **Affinda**
  `AFFINDA_CREATE_DATA_POINT`, `AFFINDA_CREATE_DATA_POINT_CHOICE`, `AFFINDA_CREATE_MAPPING`, `AFFINDA_DELETE_DATA_POINT`, `AFFINDA_DELETE_EXTRACTOR`, `AFFINDA_DELETE_MAPPING`, `AFFINDA_GET_COLLECTION_FIELDS`, `AFFINDA_GET_COLLECTION_USAGE`, `AFFINDA_GET_DATA_POINT`, `AFFINDA_GET_DATA_POINT_CHOICE`, `AFFINDA_LIST_DATA_POINT_CHOICES`, `AFFINDA_REPLACE_DATA_POINT_CHOICES`, `AFFINDA_UPDATE_DATA_POINT`, `AFFINDA_UPDATE_DATA_POINT_CHOICE`

  **Algolia**
  `ALGOLIA_COMPUTE_REALTIME_USER`, `ALGOLIA_DISABLE_TASK_V1`, `ALGOLIA_ENABLE_TASK_V1`, `ALGOLIA_GET_TASK_V1`, `ALGOLIA_RUN_TASK_V1`, `ALGOLIA_SEARCH_TASKS_V1`

  **API Ninjas**
  `API_NINJAS_GET_CARS`

  **Apify**
  `APIFY_ACT_BUILD_ABORT_POST`, `APIFY_ACT_RUN_ABORT_POST`, `APIFY_ACT_RUN_GET`, `APIFY_ACT_RUN_RESURRECT_POST`, `APIFY_RESURRECT_RUN`

  **Ashby**
  `ASHBY_ARCHIVE_INTERVIEWER_POOL`

  **BART**
  `BART_GET_AVAILABLE_SCHEDULES`, `BART_GET_SPECIAL_SCHEDULES`

  **Bitbucket**
  `BITBUCKET_SEARCH_TEAM_CODE`

  **Blackboard**
  `BLACKBOARD_CREATE_COLUMN_GROUP_ATTEMPT`, `BLACKBOARD_UPDATE_COLUMN_ATTEMPT`

  **Bolna**
  `BOLNA_GET_AGENT_V1`, `BOLNA_PATCH_AGENT_V1`

  **Box**
  `BOX_GET_RETENTION_ON_FILE`, `BOX_LIST_FILE_VERSION_LEGAL_HOLDS`, `BOX_LIST_FILE_VERSION_RETENTIONS`

  **BunnyCDN**
  `BUNNYCDN_CREATE_COINIFY_PAYMENT`, `BUNNYCDN_GET_COINIFY_BTC_EXCHANGE_RATE`, `BUNNYCDN_GET_PREPARE_PAYMENT_AUTHORIZATION`

  **Cal**
  `CAL_CREATE_OAUTH_CLIENT_USER`, `CAL_CREATE_OAUTH_CLIENT_WEBHOOK_CONFIGURATION`, `CAL_DELETE_OAUTH_CLIENT_USER`, `CAL_DELETE_OAUTH_CLIENT_WEBHOOK`, `CAL_DELETE_ORGANIZATION_ATTRIBUTE_OPTION`, `CAL_FORCE_REFRESH_USER_OAUTH_CLIENT`, `CAL_REFRESH_OAUTH_TOKEN_FOR_CLIENT_ID`, `CAL_RETRIEVE_OAUTH_CLIENT_WEBHOOK_BY_ID`

  **Canvas**
  `CANVAS_LIST_STUDENTS`

  **Clockify**
  `CLOCKIFY_GET_TEMPLATE_BY_ID_ON_WORKSPACE`, `CLOCKIFY_UPDATE_TEMPLATE`

  **Cloudinary**
  `CLOUDINARY_GENERATE_SPRITE`

  **Composio**
  `COMPOSIO_CHECK_ACTIVE_CONNECTION`

  **Confluence**
  `CONFLUENCE_SEARCH_CONTENT`

  **Conveyor**
  `CONVEYOR_GET_AUTHORIZATION_REQUESTS_QUEUE`

  **Crowdin**
  `CROWDIN_CREATE_USERS_AI_SETTINGS_CUSTOM_PLACEHOLDERS`, `CROWDIN_DELETE_USERS_AI_SETTINGS_CUSTOM_PLACEHOLDERS`, `CROWDIN_GET_USERS_AI_SETTINGS_CUSTOM_PLACEHOLDERS`, `CROWDIN_LIST_USERS_AI_SETTINGS_CUSTOM_PLACEHOLDERS`, `CROWDIN_UPDATE_TMS_SEGMENTS_RECORDS`, `CROWDIN_UPDATE_USERS_AI_SETTINGS_CUSTOM_PLACEHOLDERS`

  **Customer.io**
  `CUSTOMERIO_REPORT_PUSH_EVENTS`

  **Databricks**
  `DATABRICKS_CATALOG_ONLINE_TABLES_DELETE`, `DATABRICKS_DASHBOARDS_GENIE_EXECUTE_MESSAGE_QUERY`, `DATABRICKS_DASHBOARDS_GENIE_GET_MESSAGE_QUERY_RESULT_BY_ATTACHMENT`, `DATABRICKS_ML_FEATURE_STORE_DELETE_ONLINE_TABLE`, `DATABRICKS_ML_MATERIALIZED_FEATURES_DELETE_FEATURE_TAG`, `DATABRICKS_SERVING_SERVING_ENDPOINTS_PUT`, `DATABRICKS_SQL_ALERTS_LEGACY_CREATE`, `DATABRICKS_SQL_ALERTS_LEGACY_GET`, `DATABRICKS_SQL_ALERTS_LEGACY_LIST`, `DATABRICKS_SQL_ALERTS_LEGACY_UPDATE`, `DATABRICKS_SQL_DASHBOARDS_GET`, `DATABRICKS_SQL_DBSQL_PERMISSIONS_GET`, `DATABRICKS_SQL_DBSQL_PERMISSIONS_SET`, `DATABRICKS_SQL_QUERIES_LEGACY_DELETE`, `DATABRICKS_SQL_QUERIES_LEGACY_RESTORE`, `DATABRICKS_SQL_QUERIES_LEGACY_UPDATE`, `DATABRICKS_SQL_QUERY_VISUALIZATIONS_LEGACY_CREATE`, `DATABRICKS_SQL_QUERY_VISUALIZATIONS_LEGACY_DELETE`, `DATABRICKS_SQL_QUERY_VISUALIZATIONS_LEGACY_UPDATE`

  **DataRobot**
  `DATAROBOT_CREATE_PROJECTS_MODELS_SHAP_IMPACT`, `DATAROBOT_GET_TRACING`, `DATAROBOT_GET_TRACING_BY_ID`, `DATAROBOT_LIST_EVENT_LOGS_EVENTS`, `DATAROBOT_LIST_PROJECTS_MODELS_DATASET_ROC_CURVES`, `DATAROBOT_LIST_PROJECTS_SHAP_MATRICES`

  **Dialpad**
  `DIALPAD_DELETE_DEPARTMENT_RESOURCE`

  **Discord Bot**
  `DISCORDBOT_LIST_VOICE_REGIONS`

  **DocuSign**
  `DOCUSIGN_DEPRECATED_ENDPOINT_FOR_TAB_BLOB`, `DOCUSIGN_GET_TABS_BLOB_FOR_ENVELOPE`, `DOCUSIGN_SHARE_TEMPLATE_WITH_GROUP`

  **Dropbox**
  `DROPBOX_GET_SHARED_LINKS`

  **Eagle Doc**
  `EAGLE_DOC_RECEIPT_QUOTA_V1`, `EAGLE_DOC_RECEIPT_QUOTA_V2`, `EAGLE_DOC_RECEIPT_OCR_V1`

  **ElevenReader**
  `ELEVENREADER_GET_SIGNED_URL_DEPRECATED`

  **eSputnik**
  `ESPUTNIK_GENERATE_EVENT_V1`, `ESPUTNIK_GENERATE_PAST_EVENTS_V1`

  **Facebook**
  `FACEBOOK_ADD_PHOTOS_TO_ALBUM`, `FACEBOOK_SEARCH_PAGES`

  **Gladia**
  `GLADIA_DELETE_TRANSCRIPTION_DEPRECATED`, `GLADIA_GET_TRANSCRIPTION_AUDIO_FILE_DEPRECATED`, `GLADIA_INITIATE_TRANSCRIPTION_DEPRECATED`

  **Gleap**
  `GLEAP_CREATE_HELPCENTER_REDIRECT`

  **Google Analytics**
  `GOOGLE_ANALYTICS_GET_CONVERSION_EVENT`

  **Google Drive**
  `GOOGLEDRIVE_CREATE_TEAM_DRIVE`, `GOOGLEDRIVE_DELETE_TEAM_DRIVE`, `GOOGLEDRIVE_DELETE_TEAM_DRIVE_V2`, `GOOGLEDRIVE_GET_CHANGE_V2`, `GOOGLEDRIVE_GET_TEAM_DRIVE`, `GOOGLEDRIVE_GET_TEAM_DRIVE_V2`, `GOOGLEDRIVE_INSERT_TEAM_DRIVE`, `GOOGLEDRIVE_LIST_TEAM_DRIVES`, `GOOGLEDRIVE_LIST_TEAM_DRIVES_V2`, `GOOGLEDRIVE_UPDATE_TEAM_DRIVE`, `GOOGLEDRIVE_UPDATE_TEAM_DRIVE_V2`

  **Google Photos**
  `GOOGLEPHOTOS_LIST_SHARED_ALBUMS`

  **Happy Scribe**
  `HAPPY_SCRIBE_HS_RETRIEVE_TRANSLATION_TASK`

  **HERE**
  `HERE_GET_META_INFO_TILE`

  **HubSpot**
  `HUBSPOT_PURGE_SCHEMA_BY_OBJECT_TYPE`

  **Kaleido**
  `KALEIDO_GET_RELEASES`

  **Lexoffice**
  `LEXOFFICE_GET_DELIVERY_NOTE_DOCUMENT`

  **Loops**
  `LOOPS_SO_LIST_CUSTOM_FIELDS`

  **Loyverse**
  `LOYVERSE_DELETE_CATEGORY`

  **Mailchimp**
  `MAILCHIMP_GET_CONVERSATION`, `MAILCHIMP_LIST_CONVERSATIONS`, `MAILCHIMP_LIST_MESSAGES`

  **Mem0**
  `MEM0_LIST_ENTITIES_WITH_OPTIONAL_ORG_AND_PROJECT_FILTERS`

  **Metabase**
  `METABASE_DELETE_API_CARD_ID`, `METABASE_PUT_API_DASHBOARD_ID_CARDS`, `METABASE_UPDATE_DASHBOARD_CARDS`

  **Mixmax**
  `MIXMAX_CREATE_CONTACT_GROUP`, `MIXMAX_DELETE_CONTACT_GROUP`, `MIXMAX_GET_CONTACT_NOTES`, `MIXMAX_GET_CONTACT_GROUP`, `MIXMAX_LIST_CONTACTS`, `MIXMAX_UPDATE_CONTACT_GROUP`

  **monday.com**
  `MONDAY_ADD_SUBSCRIBERS_TO_BOARD`

  **Neon**
  `NEON_DELETE_AUTH_DOMAIN_FROM_PROJECT`, `NEON_LIST_AUTH_OAUTH_PROVIDERS`, `NEON_GET_AUTH_EMAIL_SERVER`, `NEON_UPDATE_AUTH_OAUTH_PROVIDERS`

  **New Relic**
  `NEW_RELIC_DELETE_ALERTS_NOTIFICATION_CHANNEL`

  **PagerDuty**
  `PAGERDUTY_DELETE_RESPONSE_PLAY`, `PAGERDUTY_DELETE_RULE_FROM_RULESET_BY_ID`, `PAGERDUTY_GET_OAUTH_DELEGATIONS_REVOCATION_REQUESTS_STATUS`, `PAGERDUTY_GET_RESPONSE_PLAYS`, `PAGERDUTY_RETRIEVE_RESPONSE_PLAY_BY_ID`

  **PostHog**
  `POSTHOG_LIST_AND_FILTER_PROJECT_EVENTS`, `POSTHOG_RETRIEVE_PERSONS_FUNNEL_CORRELATION_DATA`

  **Postman**
  `POSTMAN_CREATE_A_COLLECTION_FROM_A_SCHEMA`, `POSTMAN_GET_ALL_API_RELEASES`, `POSTMAN_MERGE_A_FORK`, `POSTMAN_GET_ALL_TEST_RELATIONS`, `POSTMAN_GET_DOCUMENTATION_RELATIONS`, `POSTMAN_GET_ENVIRONMENT_RELATIONS`, `POSTMAN_GET_CONTRACT_TEST_RELATIONS`, `POSTMAN_GET_INTEGRATION_TEST_RELATIONS`, `POSTMAN_GET_TEST_SUITE_RELATIONS`

  **Recruitee**
  `RECRUITEE_LIST_CAREERS_LIST_TIME_FORMAT`

  **ReferralRock**
  `REFERRALROCK_POST_MEMBERACCESS`, `REFERRALROCK_POST_REFERRALS_STATUS`

  **SafetyCulture**
  `SAFETYCULTURE_GET_TASKS_INCIDENTS`

  **Salesforce**
  `SALESFORCE_GET_UI_API_MRU_LIST_RECORDS_ACCOUNT`, `SALESFORCE_GET_UI_API_MRU_LIST_INFO_ACCOUNT`

  **Salesforce Service Cloud**
  `SALESFORCE_SERVICE_CLOUD_AGENT_SENSITIVE_DATA_RULE_TRIGGERED`, `SALESFORCE_SERVICE_CLOUD_END_CHAT_SESSION`

  **ScrapingAnt**
  `SCRAPINGANT_GET_V1_USAGE`, `SCRAPINGANT_SCRAPE_WEBPAGE_V1_POST`

  **SendGrid**
  `SENDGRID_ADD_A_SINGLE_RECIPIENT_TO_A_LIST`, `SENDGRID_DELETE_A_RECIPIENT`, `SENDGRID_DELETE_A_SINGLE_RECIPIENT_FROM_A_SINGLE_LIST`, `SENDGRID_DELETE_SEGMENT`, `SENDGRID_RETRIEVE_A_SINGLE_RECIPIENT`, `SENDGRID_SEND_A_TEST_CAMPAIGN`

  **Sentry**
  `SENTRY_GET_ACTIVATION_OF_ALERT_RULE_FOR_ORGANIZATION`, `SENTRY_SUBMIT_PROJECT_USER_FEEDBACK`, `SENTRY_SUBMIT_USER_FEEDBACK`

  **Seqera**
  `SEQERA_CREATE_WAVE_CONTAINER_TOKEN`

  **Shopify**
  `SHOPIFY_ACTIVATE_ONE_TIME_CHARGE`, `SHOPIFY_COUNT_SCRIPTTAG`, `SHOPIFY_CREATE_PRODUCT`, `SHOPIFY_CREATE_COUNTRIES`, `SHOPIFY_CREATE_ORDER_RISK`, `SHOPIFY_DEL_ORDER_RISK`, `SHOPIFY_DELETE_COUNTRIES_PARAM_COUNTRY_ID`, `SHOPIFY_DELETE_SCRIPT_TAG`, `SHOPIFY_GET_COUNTRIES_COUNT`, `SHOPIFY_GET_ORDER_RISKS`, `SHOPIFY_GET_PRICE_RULE`, `SHOPIFY_LIST_ABANDONED_CHECKOUTS`, `SHOPIFY_RECEIVE_A_LIST_OF_ALL_COUNTRIES`, `SHOPIFY_REMOVE_AN_EXISTING_COUNTRY`, `SHOPIFY_RETRIEVES_A_LIST_OF_ABANDONED_CHECKOUTS`, `SHOPIFY_RETRIEVES_A_SINGLE_ORDER_RISK_BY_ITS_ID`, `SHOPIFY_UPDATE_COUNTRIES_PARAM_COUNTRY_ID`, `SHOPIFY_UPDATE_COUNTRY`, `SHOPIFY_UPDATE_EVENT_BRIDGE_WEBHOOK_SUBSCRIPTION`, `SHOPIFY_UPDATE_ORDER_RISK`, `SHOPIFY_UPDATES_AN_EXISTING_PROVINCE_FOR_A_COUNTRY`

  **Shortcut**
  `SHORTCUT_CREATE_MILESTONE`, `SHORTCUT_DELETE_MILESTONE`, `SHORTCUT_GET_MILESTONE`, `SHORTCUT_LIST_MILESTONE_EPICS`, `SHORTCUT_LIST_MILESTONES`, `SHORTCUT_UPDATE_MILESTONE`

  **Simplesat**
  `SIMPLESAT_CREATE_OR_UPDATE_CUSTOMER_V0`, `SIMPLESAT_LIST_ANSWERS`

  **Slack**
  `SLACK_MARK_REMINDER_AS_COMPLETE`, `SLACK_USERS_SET_ACTIVE`, `SLACK_RTM_START`

  **SoundCloud**
  `SOUNDCLOUD_FETCH_USER_FAVORITED_TRACKS`, `SOUNDCLOUD_GET_FOLLOWER_USER_DETAILS`

  **Spotify**
  `SPOTIFY_GET_AVAILABLE_GENRE_SEEDS`, `SPOTIFY_GET_CATEGORY_S_PLAYLISTS`, `SPOTIFY_GET_SEVERAL_TRACKS_AUDIO_FEATURES`, `SPOTIFY_GET_TRACK_S_AUDIO_FEATURES`

  **Stripe**
  `STRIPE_GET_CUSTOMERS_CUSTOMER_SOURCES_ID`, `STRIPE_GET_SOURCES_SOURCE`, `STRIPE_POST_CHARGES`, `STRIPE_POST_SOURCES_SOURCE`

  **Supabase**
  `SUPABASE_GET_PERFORMANCE_ADVISORS`, `SUPABASE_GET_DATABASE_METADATA`, `SUPABASE_GET_LEGACY_SIGNING_KEY`, `SUPABASE_GET_PROJECT_LEGACY_API_KEYS`, `SUPABASE_GET_SECURITY_ADVISORS`

  **Trello**
  `TRELLO_UPDATE_BOARDS_MY_PREFS_SHOW_LIST_GUIDE_BY_ID_BOARD`, `TRELLO_UPDATE_SESSIONS_STATUS_BY_ID_SESSION`

  **Turbot Pipes**
  `TURBOT_PIPES_CREATE_USER_CONNECTION_DEPRECATED`, `TURBOT_PIPES_DELETE_USER_CONNECTION_DEPRECATED`, `TURBOT_PIPES_GET_USER_CONNECTION_DEPRECATED`, `TURBOT_PIPES_LIST_USER_CONNECTION_DEPRECATED`, `TURBOT_PIPES_TEST_USER_CONNECTION_DEPRECATED`, `TURBOT_PIPES_UPDATE_ORG_CONNECTION_DEPRECATED`, `TURBOT_PIPES_UPDATE_USER_CONNECTION_DEPRECATED`

  **Vercel**
  `VERCEL_GET_ALL_LOG_DRAINS`

  **Wix**
  `WIX_FIND_EVENT`, `WIX_QUERY_EVENTS_EVENTS`, `WIX_GET_SENDER_DETAILS`, `WIX_LIST_CATALOGS`, `WIX_LIST_SESSIONS`

  **YouTube**
  `YOUTUBE_MARK_COMMENT_AS_SPAM`

  **Zoom**
  `ZOOM_LIST_IQ_SETTINGS_INDICATORS`

  **Zulip**
  `ZULIP_MARK_ALL_AS_READ`, `ZULIP_REMOVE_FCM_TOKEN`, `ZULIP_SEND_TEST_NOTIFICATION`
</details>

### Why This Matters

* **Cleaner tool selection**: Agents no longer see deprecated tools when browsing available tools, reducing confusion and failed tool executions
* **No breaking changes**: Deprecated tools are flagged, not removed — they'll still work as long as the upstream API endpoint remains available

## 26 Toolkits Deprecated

26 toolkits have been deprecated — 7 for dead/defunct services and 19 that were duplicates, rebrands, or naming variants of existing toolkits.

### Dead Services (7)

These services are no longer operational:

`cloudpress`, `bench`, `leadoku`, `induced_ai`, `docnify`, `logoraisr`, `ncscale`

### Duplicates, Rebrands, and Naming Variants (19)

These toolkits were redundant with existing ones and have been deprecated in favor of the canonical version:

| Deprecated Toolkit | Use Instead | Reason |
| - | - | - |
| `doppler_secretops` | `doppler` | Duplicate |
| `rev_ai` | `rev` | Duplicate |
| `metaphor` | `exa` | Rebranded |
| `reply` | `reply_io` | Duplicate |
| `foursquare_v1` | `foursquare` | Legacy version |
| `foursquare_v2` | `foursquare` | Legacy version |
| `polygon_io` | `polygon` | Subset |
| `customer_io` | `customerio` | Naming variant |
| `parsio_io` | `parsio` | Naming variant |
| `onbee_app` | `onbee` | Naming variant |
| `fixer_io` | `fixer` | Naming variant |
| `ip2location_io` | `ip2location` | Naming variant |
| `cloudflare_api_key` | `cloudflare` | Different auth only |
| `onesignal_user_auth` | `onesignal_rest_api` | Identical functionality |
| `firecrawl2` | `firecrawl` | Version variant |
| `openweather_api` | `weathermap` | Same API |
| `scheduleonce` | `oncehub` | Rebranded |
| `elevenreader` | `elevenlabs` | Duplicate |
| `sendbird_ai_chabot` | `sendbird` | Subset |

### Why This Matters

* **Less confusion**: Developers won't accidentally pick a deprecated variant when a canonical toolkit exists
* **Cleaner discovery**: Toolkit listings now surface only the actively maintained version of each service

**Feb 20, 2026**

Slackbot toolkit now includes only actions that work with bot tokens

## Slackbot Toolkit: Bot-Compatible Actions Only

**Toolkit version:** `20260223_00`

The Slackbot toolkit inherits actions from the Slack toolkit. Previously, it included all 155 actions — but many of these were admin-only endpoints (`admin.*`) that require user tokens and don't work with bot tokens.

We've filtered the action list down to **89 bot-compatible actions** — only actions whose Slack API endpoints are callable with a bot token.

### What Changed

| Category | Count |
| - | - |
| Bot-compatible actions (included) | 89 |
| Admin/non-bot actions (removed) | 62 |
| Triggers (unchanged) | 9 |

### Why This Matters

* **Actions that work**: Every action in the Slackbot toolkit now works with standard bot tokens
* **Clearer scope**: No more confusion about which actions require elevated permissions
* **All triggers kept**: Event-based triggers work with bot tokens and remain available

### Removed Actions

The following action categories were removed because they require user tokens or admin permissions:

* `admin.*` endpoints (workspace administration)
* `audit.*` endpoints (audit logs)
* SCIM endpoints (user provisioning)

If you need admin-level Slack functionality, use the full Slack toolkit with appropriate user token authentication.

**Feb 15, 2026**

All newly created organizations will now use Webhook Payload V3 by default

## Webhook V3 Now Default for New Organizations

As announced in our [Webhook Payload V3 lookahead](https://composio-preview.mintlify.site/docs/changelog/2025/12/30), **Webhook Payload V3 is now the default for all newly created organizations**.

## What's Changed?

Starting today, every new organization created on Composio will automatically use **Webhook Payload V3** for all webhook and Pusher deliveries. This means new organizations benefit from the improved webhook structure out of the box, with no additional configuration needed.

### For New Organizations

* Webhook payloads follow the [Standard Webhooks specification](https://github.com/standard-webhooks/standard-webhooks/blob/main/spec/standard-webhooks.md)
* Trigger data is cleanly separated from Composio metadata via the `metadata` and `data` fields
* The `x-composio-webhook-version: V3` header is included in all webhook deliveries

### For Existing Organizations

Nothing changes for existing organizations. If your organization was created before today:

* You will continue to receive webhooks in your current format (V1 or V2)
* You can opt-in to V3 at any time through your [project settings](https://dashboard.composio.dev?utm_source=docs\&utm_medium=content\&utm_campaign=changelog-02-15-26-webhook-v3-default-new-orgs)

## V3 Payload Recap

```json theme={null}
{
  "id": "msg_a1b2c3d4-5e6f-7a8b-9c0d-1e2f3a4b5c6d",
  "timestamp": "2026-02-15T12:00:00.000Z",
  "type": "composio.trigger.message",
  "metadata": {
    "log_id": "log_TpxVOLXYnwXZ",
    "trigger_slug": "GMAIL_NEW_GMAIL_MESSAGE",
    "auth_config_id": "ac_aCYTppZ5RsRc",
    "connected_account_id": "ca_cATYssZ5RrSc",
    "trigger_id": "ti_JZFoTyYKbzhB",
    "user_id": "your-user-id"
  },
  "data": {
    // Clean trigger data without Composio metadata
  }
}
```

## How to Switch to V3 (Existing Organizations)

1. Go to your project settings in the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs\&utm_medium=content\&utm_campaign=changelog-02-15-26-webhook-v3-default-new-orgs)
2. Navigate to the Webhooks section
3. Select **Webhook Payload Version: V3**
4. Update your webhook handlers using the [migration guide](https://composio-preview.mintlify.site/docs/changelog/2025/12/30#migration-guide)
5. Test thoroughly before enabling in production

> [!NOTE]
>
> We strongly recommend all organizations migrate to V3 for a better developer experience, standards compliance, and access to new features like [connection expiry events](https://composio-preview.mintlify.site/docs/changelog/2026/02/06#new-event-composio-connected_account-expired).

**Feb 12, 2026**

Composio managed credentials are no longer available for the Twitter toolkit. Developers must bring their own credentials to continue using Twitter integrations.

## Removal of Composio Managed Credentials for Twitter Toolkit

Composio managed credentials for the Twitter toolkit have been removed. Going forward, developers will need to provide their own Twitter API credentials to continue integrating Twitter into their applications.

### What's Changing?

Previously, Composio provided managed credentials for the Twitter toolkit, allowing developers to use Twitter integrations without setting up their own Twitter API credentials. This managed credential support has now been removed.

### Impact

If you were relying on Composio managed credentials for the Twitter toolkit, your Twitter integrations will no longer work until you configure your own credentials.

### Migration

To continue using the Twitter toolkit, you will need to:

1. Create a Twitter Developer account and obtain your own API credentials from the [Twitter Developer Portal](https://developer.x.com/en/portal/dashboard).
2. Set up a custom auth configuration with your Twitter API credentials in Composio.

> [!WARNING]
>
> **Action Required**
>
> If you are currently using Composio managed credentials for Twitter, you must bring your own Twitter API credentials to avoid disruption. Set up your own auth configuration before your existing connections expire.

**Feb 11, 2026**

All toolkits now use a consistent set of categories for better discovery and organization

## Standardized Toolkit Categories

We've standardized the category taxonomy across all toolkits. Previously, categories were inconsistently applied with variations in naming and structure. Now, every toolkit is assigned categories from a well-defined set that can be extended as needed.

## What Changed

All toolkits have been recategorized using a standardized set of categories:

**AI & Automation**: Artificial Intelligence, AI Agents, AI Assistants, AI Chatbots, AI Content Generation, AI Document Extraction, AI Meeting Assistants, AI Models, AI Safety Compliance Detection, AI Sales Tools, AI Web Scraping, Model Context Protocol

**Business & Commerce**: Business Intelligence, Analytics, Dashboards, Reviews, Commerce, Accounting, eCommerce, Fundraising, Payment Processing, Proposal & Invoice Management, Taxes

**Communication**: Communication, Call Tracking, Email, Fax, Notifications, Phone & SMS, Team Chat, Team Collaboration, Video Conferencing

**Content & Files**: Content & Files, Documents, File Management & Storage, Images & Design, Notes, Transcription, Video & Audio

**Human Resources**: Human Resources, Education, HR Talent & Recruitment

**IT & Development**: IT Operations, Databases, Developer Tools, Online Courses, Security & Identity Tools, Server Monitoring, Internet of Things

**Lifestyle**: Lifestyle & Entertainment, Fitness, Gaming, News & Lifestyle

**Marketing**: Marketing, Ads & Conversion, Drip Emails, Email Newsletters, Event Management, Marketing Automation, Social Media Accounts, Social Media Marketing, Transactional Email, URL Shortener, Webinars

**Productivity**: Productivity, Bookmark Managers, Calendar, Product Management, Project Management, Spreadsheets, Task Management, Time Tracking Software

**Sales & Support**: Sales & CRM, Contact Management, CRM, Forms & Surveys, Scheduling & Booking, Signatures, Support, Customer Appreciation, Customer Support

**Web & Apps**: Website & App Building, App Builder, Website Builders

## Why This Matters

* **Better discovery**: Find relevant toolkits faster with consistent categorization
* **Cleaner filtering**: Filter toolkits by category in the dashboard and API with predictable values
* **Extensible**: New categories can be added as the toolkit ecosystem grows

## API Impact

The `categories` field in toolkit responses now returns values from this standardized set. If you're filtering toolkits by category, update your queries to use the new category names.

**Feb 9, 2026**

Four new native toolkits are now available for tool calling and Tool Router workflows.

## Granola, monday.com, Context7, and Wix Toolkits

We've shipped four new toolkits in the first wave of external MCPs now available as native toolkits in Composio. Use them directly for tool calling or via Tool Router.

### New Toolkits

* **Granola**: AI meeting notes that transcribe and summarize calls into structured notes.
* **monday.com**: Work management platform for projects, tasks, and team workflows.
* **Context7**: Up-to-date library documentation and code examples for LLMs.
* **Wix**: Build and manage projects with business solutions like eCommerce, Bookings, and Payments in a few prompts via AI tools (Cursor/Claude) through the Wix MCP server.

**Feb 6, 2026**

Typed responses now cover 130+ toolkits with 75+ newly typed toolkits. Response wrapping is now consistent across all actions, with data always nested under a top-level data field. New API for managing webhook configurations with event filtering, plus a new event to notify when connected accounts expire

## 75+ More Toolkits Get Typed Responses & Consistent Response Schema Wrapping

We've expanded typed response coverage to 75+ additional toolkits. In total, over 130 toolkits now return strongly typed response objects. Additionally, we've standardized response schema wrapping so that all action responses consistently nest their output under a top-level `data` field.

> [!WARNING]
>
> **Breaking Change for `latest` Version**
>
> Two breaking changes ship in this release:
>
> 1. **Newly typed toolkits** — If your code depends on the old `response_data` structure for any of the 75+ newly typed toolkits listed below, you'll need to update your code to work with the new typed response schemas.
> 2. **Consistent response wrapping** — Actions that previously had `data` at the root level of their response schema now wrap the entire response under a `data` field. See the migration guide below.

### Consistent Response Schema Wrapping

Previously, actions whose response schema already contained a `data` field at the root level would surface all fields (including `data`) alongside `successful` and `error` at the top level. Now, all action responses are uniformly wrapped: the full response object is nested inside a `data` field, with `successful` and `error` at the top level.

#### Affected: Toolkits with `data` in their response model (e.g., Pipedrive `PIPEDRIVE_LIST_UPDATES_ABOUT_A_DEAL`)

These actions had a `data` field in their original response schema. Previously, those fields were spread at the root level alongside `successful` and `error`. Now, they are nested under a top-level `data` field.

**Before:**

```json theme={null}
{
  "data": { "deal_id": 1, "field_key": "stage_id", "old_value": "1", "new_value": "2" },
  "successful": true,
  "error": null
}
```

**After:**

```json theme={null}
{
  "data": {
    "data": { "deal_id": 1, "field_key": "stage_id", "old_value": "1", "new_value": "2" }
  },
  "successful": true,
  "error": null
}
```

If your code accesses fields directly at the root level (e.g., `result["data"]`), update it to access them under `result["data"]["data"]` instead.

#### Not affected: Toolkits without `data` in their response model (e.g., GitHub `GITHUB_GET_THE_LATEST_RELEASE`)

These actions never had a `data` field in their original response schema, so their wrapping behavior is unchanged. The response fields are nested under `data` as before.

```json theme={null}
{
  "data": {
    "url": "https://api.github.com/repos/octocat/Hello-World/releases/1",
    "tag_name": "v1.0.0",
    "name": "v1.0.0",
    "draft": false,
    "prerelease": false,
    "author": { "login": "octocat", "id": 1 }
  },
  "successful": true,
  "error": null
}
```

No migration needed for these toolkits.

> [accordion] Affected Toolkits (280+)
>
> **abuselpdb**, **active\_campaign**, **active\_trail**, **adyntel**, **affinda**, **agentql**, **agenty**, **agiled**, **alpha\_vantage**, **ambee**, **amcards**, **amplitude**, **anchor\_browser**, **anthropic\_administrator**, **api\_bible**, **api\_labz**, **apify**, **apipie\_ai**, **apiverve**, **appcircle**, **asana**, **attio**, **bamboohr**, **beaconchain**, **beaconstac**, **benchmark\_email**, **benzinga**, **better\_proposals**, **better\_stack**, **bigpicture\_io**, **bitbucket**, **bitquery**, **blackbaud**, **boloforms**, **brightdata**, **browseai**, **browserless**, **byteforms**, **cal**, **calendarhero**, **callerapi**, **callingly**, **callpage**, **canvas**, **carbone**, **cardly**, **census\_bureau**, **certifier**, **chaser**, **claid\_ai**, **clearout**, **clickhouse**, **clicksend**, **close**, **cloudcart**, **cloudconvert**, **cloudinary**, **cloudlayer**, **codemagic**, **cody**, **coinbase**, **coinmarketcal**, **coinmarketcap**, **coinranking**, **connecteam**, **contentful\_graphql**, **corrently**, **crowdin**, **cults**, **customerio**, **customgpt**, **databricks**, **datagma**, **datarobot**, **deepimage**, **deepseek**, **demio**, **dialmycalls**, **diffbot**, **dnsfilter**, **dock\_certs**, **docsumo**, **documenso**, **documint**, **docupilot**, **docupost**, **docuseal**, **dotsimple**, **dovetail**, **dripcel**, **dromo**, **dropcontact**, **emailoctopus**, **emelia**, **endorsal**, **enigma**, **esignatures\_io**, **esputnik**, **etermin**, **eversign**, **exa**, **faceup**, **fibery**, **figma**, **files\_com**, **finage**, **findymail**, **fireberry**, **firecrawl**, **fireflies**, **firmao**, **flutterwave**, **fluxguard**, **folk**, **forcemanager**, **formbricks**, **freshdesk**, **gamma**, **gan\_ai**, **getform**, **giphy**, **github**, **givebutter**, **gleap**, **goody**, **googlesheets**, **gosquared**, **groqcloud**, **gtmetrix**, **habitica**, **headout**, **helpwise**, **heygen**, **hookdeck**, **hotspotsystem**, **html\_to\_image**, **hunter**, **hyperbrowser**, **icypeas**, **imgbb**, **imgix**, **insighto\_ai**, **instagram**, **instantly**, **intelliprint**, **intercom**, **ip2location**, **iqair\_airvisual**, **jobnimbus**, **junglescout**, **kadoa**, **kaggle**, **kibana**, **klaviyo**, **klipfolio**, **ko\_fi**, **laposta**, **leadfeeder**, **leiga**, **lemon\_squeezy**, **lever**, **linear**, **listclean**, **lodgify**, **loops\_so**, **mailcoach**, **mailerlite**, **mailersend**, **mails\_so**, **mapulus**, **melo**, **memberspot**, **memberstack**, **metaads**, **metabase**, **minerstat**, **miro**, **mistral\_ai**, **monday**, **moneybird**, **msg91**, **multionai**, **mx\_toolbox**, **nango**, **needle**, **nextdns**, **omnisend**, **openai**, **openrouter**, **paradym**, **passcreator**, **pdfless**, **peopledatalabs**, **perigon**, **persistiq**, **phantombuster**, **piggy**, **pilvio**, **pinecone**, **pipedrive**, **placid**, **plain**, **plisio**, **polygon**, **postgrid**, **postgrid\_verify**, **postman**, **prisma**, **productboard**, **promptmate\_io**, **proofly**, **proxiedmail**, **pushbullet**, **rafflys**, **raisely**, **ramp**, **reddit**, **refiner**, **remarkety**, **remote\_retrieval**, **remove\_bg**, **reply**, **reply\_io**, **resend**, **respond\_io**, **retailed**, **retently**, **rocket\_reach**, **rocketlane**, **rootly**, **satismeter**, **scrapfly**, **segment**, **semrush**, **sendbird**, **sendfox**, **sendlane**, **sendloop**, **shopify**, **shotstack**, **signaturely**, **simple\_analytics**, **skyfire**, **slack**, **smtp2go**, **snowflake**, **snowflake\_basic**, **sourcegraph**, **stannp**, **statuscake**, **stormglass\_io**, **stripe**, **survey\_monkey**, **svix**, **sympla**, **telnyx**, **teltel**, **textcortex**, **textrazor**, **thanks\_io**, **tiktok**, **timelinesai**, **toggl**, **token\_metrics**, **tomba**, **tripadvisor**, **tripadvisor\_content\_api**, **truvera**, **twelve\_data**, **v0**, **vercel**, **verifiedemail**, **virustotal**, **wakatime**, **whatsapp**, **workday**, **wrike**, **writer**, **yelp**, **ynab**, **zoho**, **zoho\_bigin**, **zoho\_mail**

### 75+ Newly Typed Response Toolkits

All outputs for these toolkits now return strongly typed objects with clear field documentation instead of generic `response_data` blobs. Combined with the 60+ toolkits typed in the previous release, over 130 toolkits now have typed responses.

> [accordion] Newly Typed Toolkits (78)
>
> #### Developer & DevOps
>
> bitquery, docusign, hookdeck, metabase, neon, parsera, postgrid, sentry, servicenow
>
> #### Communication & Collaboration
>
> dailybot, dialpad, gleap, gong, googlemeet, retellai, smtp2go
>
> #### CRM & Business
>
> bamboohr, coupa, forcemanager, lever, mixpanel, monday, okta, peopledatalabs, pipedrive, productboard, workday
>
> #### Marketing & Analytics
>
> amplitude, datagma, diffbot, lemlist, mailerlite, posthog, remarkety, resend, retently, sendgrid
>
> #### AI & Automation
>
> bolna, multionai
>
> #### Media & Entertainment
>
> giphy, soundcloud, spotify, spotlightr
>
> #### Real Estate & Location
>
> acculynx, apaleo, foursquare, foursquare\_v1, foursquare\_v2, hotspotsystem
>
> #### E-commerce & Payments
>
> moneybird, open\_sea, plisio, zoho\_inventory
>
> #### Education & Learning
>
> blackboard, canvas, d2lbrightspace, habitica
>
> #### Project Management
>
> pagerduty, shortcut, taskade, wrike, workspace
>
> #### Productivity & Personal
>
> borneo, box, cal, etermin, formdesk, google\_admin, junglescout, klipfolio, onepage, strava, typefully, wakatime, zenrows, zoho, zoho\_mail
>
> #### Other
>
> semanticscholar

## Webhook Subscriptions API & Connection Expiry Events

A new API for managing webhook configurations with event filtering, HMAC signature verification, and support for platform lifecycle events. This replaces the legacy project-level webhook settings with a more flexible, subscription-based model.

## Summary

| Change | Type | Action Required |
| - | - | - |
| New Webhook Subscriptions API | New Feature | No |
| `composio.connected_account.expired` event | New Feature | Opt-in |
| Legacy webhook endpoints | Deprecated | Migration recommended |
| `webhook_url`, `webhook_secret` in Project | Deprecated | Use new API |

***

## API Overview

See the [Webhook Subscriptions API Reference](https://composio-preview.mintlify.site/reference/api-reference/webhook-subscriptions) for complete details.

### Endpoints

| Method | Endpoint | Description |
| - | - | - |
| `POST` | `/api/v3/webhook_subscriptions` | Create a subscription |
| `GET` | `/api/v3/webhook_subscriptions` | List all subscriptions |
| `GET` | `/api/v3/webhook_subscriptions/{id}` | Get subscription details |
| `PATCH` | `/api/v3/webhook_subscriptions/{id}` | Update subscription |
| `DELETE` | `/api/v3/webhook_subscriptions/{id}` | Delete subscription |
| `POST` | `/api/v3/webhook_subscriptions/{id}/rotate_secret` | Rotate signing secret |
| `GET` | `/api/v3/webhook_subscriptions/event_types` | List available event types |

### Key Capabilities

* **Event filtering**: Subscribe only to events you need
* **HMAC-SHA256 signatures**: Every webhook includes a cryptographic signature for verification
* **Secret rotation**: Rotate signing secrets on demand

### Creating a Subscription

```bash theme={null}
curl -X POST "https://backend.composio.dev/api/v3/webhook_subscriptions" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "webhook_url": "https://your-server.com/webhooks/composio",
    "enabled_events": ["composio.trigger.message"],
    "version": "V3"
  }'
```

**Response:**

```json theme={null}
{
  "id": "ws_your-subscription-id",
  "webhook_url": "https://your-server.com/webhooks/composio",
  "version": "V3",
  "enabled_events": ["composio.trigger.message"],
  "secret": "<your-webhook-secret>",
  "created_at": "2026-02-06T12:00:00.000Z",
  "updated_at": "2026-02-06T12:00:00.000Z"
}
```

> [!WARNING]
>
> The `secret` is only returned once at creation time or when rotated. Store it securely for signature verification.

### Notes

* **1 subscription per project**: Currently limited to one webhook subscription per project. This will be expanded in future releases.
* **HTTPS required**: Webhook URLs must use HTTPS in production environments.

***

## New Event: `composio.connected_account.expired`

A new platform event that notifies you when an **OAuth2** connected account's authentication expires and cannot be automatically refreshed.

> [!NOTE]
>
> This event is **only available in V3 format**. We strongly recommend using V3 for all new integrations to access the latest features and follow standard webhook practices.

### Use Cases

* Prompt users to re-authenticate before workflows fail
* Track connection health across your user base
* Automate re-connection flows
* Build proactive notification systems

### Subscribing to Connection Expiry Events

```bash theme={null}
curl -X POST "https://backend.composio.dev/api/v3/webhook_subscriptions" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "webhook_url": "https://your-server.com/webhooks/composio",
    "enabled_events": [
      "composio.trigger.message",
      "composio.connected_account.expired"
    ],
    "version": "V3"
  }'
```

### Payload Structure

The `composio.connected_account.expired` event follows the V3 envelope format:

```json theme={null}
{
  "id": "evt_847cdfcd-d219-4f18-a6dd-91acd42ca94a",
  "timestamp": "2026-02-06T12:00:00.000Z",
  "type": "composio.connected_account.expired",
  "metadata": {
    "project_id": "pr_your-project-id",
    "org_id": "ok_your-org-id"
  },
  "data": {
    "toolkit": {
      "slug": "gmail"
    },
    "auth_config": {
      "id": "ac_your-auth-config-id",
      "auth_scheme": "OAUTH2",
      "is_composio_managed": true,
      "is_disabled": false
    },
    "id": "ca_your-connected-account-id",
    "status": "EXPIRED",
    "created_at": "2025-12-01T10:00:00.000Z",
    "updated_at": "2026-02-06T12:00:00.000Z",
    "status_reason": "OAuth refresh token expired",
    "is_disabled": false
  }
}
```

> [!NOTE]
>
> The `data` object matches the response from [`GET /api/v3/connected_accounts/{id}`](https://composio-preview.mintlify.site/reference/api-reference/connected-accounts/getConnectedAccountsByNanoid), making it easy to process with existing code and SDK types.

***

## Verifying Webhook Signatures

All webhooks include an HMAC signature in the `webhook-signature` header. Use the SDK's built-in verification functions or see the [Triggers documentation](https://composio-preview.mintlify.site/docs/triggers.md) for implementation details.

***

## Available Event Types

Query available events and their version compatibility:

```bash theme={null}
curl "https://backend.composio.dev/api/v3/webhook_subscriptions/event_types" \
  -H "x-api-key: YOUR_API_KEY"
```

| Event Type | Description | Supported Versions |
| - | - | - |
| `composio.trigger.message` | Trigger events from integrations | V1, V2, V3 |
| `composio.connected_account.expired` | Connection authentication expired | **V3 only** |

***

## Deprecations

### Deprecated Endpoints

The following legacy endpoints are deprecated and will be removed in a future release:

| Deprecated Endpoint | Replacement |
| - | - |
| `GET /api/v3/org/project/webhook` | `GET /api/v3/webhook_subscriptions` |
| `POST /api/v3/org/project/webhook/update` | `POST /api/v3/webhook_subscriptions` |
| `DELETE /api/v3/org/project/webhook` | `DELETE /api/v3/webhook_subscriptions/{id}` |
| `POST /api/v3/org/project/webhook/refresh` | `POST /api/v3/webhook_subscriptions/{id}/rotate_secret` |

### Deprecated Fields in Project Response

| Field | Status | Notes |
| - | - | - |
| `webhook_url` | Deprecated | Use Webhook Subscriptions API |
| `webhook_secret` | Deprecated | Use Webhook Subscriptions API |
| `event_webhook_url` | Deprecated | Never implemented |
| `is_new_webhook` | Deprecated | Use Webhook Subscriptions API |

***

## Backward Compatibility

> [!WARNING]
>
> **No immediate action required.** Your existing webhook configurations will continue to work.

### What We've Done For You

* **Automatic migration**: We've created a webhook subscription for all existing projects that had webhook URLs configured, with `composio.trigger.message` enabled by default
* **Same payload format**: If you were using V1, V2, or V3 triggers, they continue with the same format

### What Continues to Work

* Legacy webhook endpoints (deprecated but functional)
* Existing project webhook configurations
* All existing trigger payload formats (V1, V2, V3)
* Signature verification with your existing secret

***

## Payload Version Comparison

| Version | Format | Recommendation |
| - | - | - |
| V1 | Legacy flat structure | For backward compatibility only |
| V2 | Nested with metadata | For existing integrations |
| **V3** | Structured envelope with `id`, `timestamp`, `type`, `metadata`, `data` | **Recommended for all new integrations** |

**Feb 4, 2026**

When fetching tools with a limit parameter, the important flag is no longer automatically applied, ensuring users get the exact number of tools requested

## Limit Parameter Now Prevents Important Flag Auto-Apply

## Version Information

### TypeScript/JavaScript

* Package: `@composio/core` and all provider packages
* Version: `0.6.3`+
* PR: [#2570](https://github.com/ComposioHQ/composio/pull/2570)

The `important` flag auto-apply logic has been updated to respect the `limit` parameter. When you provide a `limit`, the SDK no longer automatically applies `important: true`, ensuring you get the exact number of tools you requested.

## What Changed

Previously, when querying tools by toolkit with both `toolkits` and `limit` parameters, the SDK would auto-apply `important: true`. This could result in returning fewer tools than the requested limit if the toolkit had limited important tools.

**Before:**

```typescript theme={null}
// Could return < 50 tools if only 10 important tools exist
const tools = await composio.tools.get('default', {
  toolkits: ['github'],
  limit: 50,
});
// Result: Only 10 tools (important ones only)
```

**After:**

```typescript theme={null}
// Returns exactly 50 tools (or all available if < 50)
const tools = await composio.tools.get('default', {
  toolkits: ['github'],
  limit: 50,
});
// Result: 50 tools (including non-important)
```

## Auto-Apply Logic

The `important` flag is now auto-applied **only when ALL** of these conditions are met:

* `toolkits` is provided
* `tools` is NOT provided
* `tags` is NOT provided
* `search` is NOT provided
* **`limit` is NOT provided** ← NEW
* `important` is NOT explicitly set to `false`

## Examples

### Auto-Applies Important (No Limit)

```typescript theme={null}
const tools = await composio.tools.get('default', {
  toolkits: ['github'],
});
// Returns: ~10-20 important tools
```

### Does NOT Auto-Apply (Limit Provided)

```typescript theme={null}
const tools = await composio.tools.get('default', {
  toolkits: ['github'],
  limit: 50,
});
// Returns: Exactly 50 tools (or all available)
```

### Explicit Important Overrides

```typescript theme={null}
const tools = await composio.tools.get('default', {
  toolkits: ['github'],
  limit: 50,
  important: true,
});
// Returns: Up to 50 important tools
```

### Prevents Auto-Apply (Tags Provided)

```typescript theme={null}
const tools = await composio.tools.get('default', {
  toolkits: ['github'],
  tags: ['important'],
});
// Returns: GitHub tools with 'important' tag (no auto-apply)
```

### Prevents Auto-Apply (Search Provided)

```typescript theme={null}
const tools = await composio.tools.get('default', {
  toolkits: ['github'],
  search: 'repository',
});
// Returns: GitHub tools matching search (no auto-apply)
```

## Why This Matters

When you provide a `limit`, you're explicitly requesting a specific number of tools. Auto-applying the `important` filter could prevent you from getting the requested number of tools. This change respects user intent and makes the SDK behavior more predictable.

**Use cases:**

1. **Pagination**: Get exactly N tools per page
2. **Performance**: Limit tool count for faster responses
3. **UI constraints**: Display a specific number of tools in your interface

## Backward Compatibility

This change is **backward compatible** with one caveat:

* **No code changes needed** for most users
* If you were relying on automatic `important` filtering with `limit`, you now need to explicitly pass `important: true`

**Migration (if needed):**

```typescript theme={null}
// Before (relied on auto-apply even with limit)
const tools = await composio.tools.get('default', {
  toolkits: ['github'],
  limit: 20,
});

// After (explicit important flag)
const tools = await composio.tools.get('default', {
  toolkits: ['github'],
  limit: 20,
  important: true, // Explicitly set if you want important tools
});
```

## Documentation

Full documentation with more examples is available in the [Tools API Reference](https://composio-preview.mintlify.site/reference/sdk-reference/typescript/tools.md).

**Feb 3, 2026**

60+ toolkits now feature typed responses, including newly typed GitHub, Mailchimp, and Trello. We're planning to expand response schemas to 40+ additional toolkits

## Expanded Typed Responses with GitHub, Mailchimp & Trello - Planning Further Expansion

We've expanded our typed response support to include three major toolkits—GitHub, Mailchimp, and Trello—while also adding more typed actions across previously updated toolkits. All outputs now return strongly typed objects with clear field documentation instead of generic `response_data` blobs, enabling better IDE support and more reliable agent interactions.

> [!WARNING]
>
> **Breaking Change for `latest` Version**
>
> If you're using the `latest` version and your code depends on the old `response_data` structure for GitHub, Mailchimp, or Trello, you'll need to update your code to work with the new typed response schemas.

### Why This Matters

* Enhanced type safety: GitHub, Mailchimp, and Trello now have fully typed responses
* Expanded action coverage: More actions in existing toolkits now return typed data
* Improved developer experience: Better autocomplete and field validation across all toolkits
* Agent-friendly schemas: Cleaner output shapes reduce parsing errors and improve AI tool usage

> [accordion] Newly Typed Toolkits & Enhanced Coverage
>
> #### Newly Typed Toolkits (3)
>
> **github**, **mailchimp**, **trello**
>
> #### Enhanced Existing Toolkits
>
> Additional typed actions added to:
>
> ##### Communication & Collaboration
>
> discordbot, microsoft\_teams, slack, zoom
>
> ##### CRM & Sales
>
> apollo, attio, hubspot, instantly, intercom, kommo, salesforce
>
> ##### Productivity & Docs
>
> coda, confluence, googledocs, googletasks, notion, todoist
>
> ##### Marketing & Social Media
>
> facebook, instagram, klaviyo, linkedin, metaads, reddit, tiktok
>
> ##### E-commerce & Payments
>
> brex, quickbooks, ramp, shopify, square, stripe, xero
>
> ##### Project Management
>
> clickup, linear
>
> ##### Design & Creative
>
> canva, figma
>
> ##### Data & Analytics
>
> ahrefs, airtable, apify, exa, pplx, serpapi, tavily
>
> ##### Email & Calendar
>
> calendly, outlook
>
> ##### Storage & Files
>
> one\_drive
>
> ##### Web Tools
>
> firecrawl, fireflies, google\_maps, google\_search\_console
>
> ##### AI & Media
>
> elevenlabs, heygen, lmnt, mem0
>
> ##### Customer Support
>
> freshdesk, zendesk
>
> ##### Video & Content
>
> youtube

### Coming Soon: 40+ More Toolkits

We're planning to expand typed response coverage to 40+ additional toolkits in upcoming releases.

> [accordion] Upcoming Typed Response Toolkits
>
> #### Developer & DevOps
>
> bitquery, clickhouse, composio, contentful\_graphql, docusign, hookdeck, metabase, neon, parsera, postgrid, sentry, servicenow
>
> #### Communication & Collaboration
>
> dailybot, dialpad, gleap, gong, googlemeet, plain, retellai, smtp2go
>
> #### CRM & Business
>
> bamboohr, coupa, forcemanager, lever, mixpanel, monday, okta, peopledatalabs, pipedrive, productboard, workday
>
> #### Marketing & Analytics
>
> amplitude, datagma, diffbot, lemlist, mailerlite, posthog, remarkety, resend, retently, sendgrid
>
> #### AI & Automation
>
> affinda, agentql, bolna, entelligence, kadoa, multionai
>
> #### Media & Entertainment
>
> giphy, soundcloud, spotify, spotlightr
>
> #### Real Estate & Location
>
> acculynx, apaleo, foursquare, foursquare\_v1, foursquare\_v2, hotspotsystem
>
> #### E-commerce & Payments
>
> moneybird, open\_sea, plisio, zoho\_inventory
>
> #### Education & Learning
>
> blackboard, canvas, d2lbrightspace, habitica
>
> #### Project Management
>
> pagerduty, shortcut, taskade, wrike, workspace
>
> #### Productivity & Personal
>
> borneo, box, cal, etermin, formdesk, formbricks, google\_admin, junglescout, klipfolio, onepage, strava, typefully, wakatime, zenrows, zoho, zoho\_mail
>
> #### Other Services
>
> cults, faceup, semanticscholar

**Feb 1, 2026**

The Python SDK now provides automatic type inference for tools.get() based on the provider

## Type-Safe get\_tools() for Python SDK

The Python SDK's `Composio` class is now generic over the provider type. When you pass a provider to `Composio()`, the return type of `tools.get()` is automatically inferred based on that provider.

### SDK Versions

| SDK | Version |
| - | - |
| Python | v0.11.1+ |

### What Changed

**Before:** The return type of `tools.get()` was always untyped or required manual type annotations.

**After:** Type checkers (mypy, Pyright) automatically infer the correct tool type from the provider you pass.

**Before (untyped):**

```python theme={null}
from composio import Composio
from composio_anthropic import AnthropicProvider

composio = Composio(provider=AnthropicProvider())
tools = composio.tools.get(user_id="user_123", toolkits=["github"])
# tools: Unknown type - no inference
```

**After (type-safe):**

```python theme={null}
from composio import Composio
from composio_anthropic import AnthropicProvider

composio = Composio(provider=AnthropicProvider())
tools = composio.tools.get(user_id="user_123", toolkits=["github"])
# tools: list[ToolParam] - automatically inferred!
```

### Automatic Type Inference

The `Composio` class now uses Python generics to provide type-safe return values:

```python theme={null}
from composio import Composio
from composio_openai import OpenAIProvider
from composio_anthropic import AnthropicProvider

# OpenAI provider -> list[ChatCompletionToolParam]
composio_openai = Composio(provider=OpenAIProvider())
openai_tools = composio_openai.tools.get(user_id="user", toolkits=["github"])

# Anthropic provider -> list[ToolParam]
composio_anthropic = Composio(provider=AnthropicProvider())
anthropic_tools = composio_anthropic.tools.get(user_id="user", toolkits=["github"])

# Default (no provider) -> list[ChatCompletionToolParam] (OpenAI)
composio_default = Composio()
default_tools = composio_default.tools.get(user_id="user", toolkits=["github"])
```

### Custom Provider Support

Custom providers automatically get proper type inference without requiring any changes to the Composio SDK:

```python theme={null}
import typing as t
from typing import Sequence

from composio import Composio
from composio.client.types import Tool
from composio.core.provider import NonAgenticProvider

class MyCustomTool(t.TypedDict):
    """Your custom tool format."""
    name: str
    description: str
    parameters: dict

MyCustomToolCollection = t.List[MyCustomTool]

class MyCustomProvider(
    NonAgenticProvider[MyCustomTool, MyCustomToolCollection],
    name="my-custom"
):
    def wrap_tool(self, tool: Tool) -> MyCustomTool:
        return MyCustomTool(
            name=tool.slug,
            description=tool.description or "",
            parameters=tool.input_parameters or {},
        )

    def wrap_tools(self, tools: Sequence[Tool]) -> MyCustomToolCollection:
        return [self.wrap_tool(tool) for tool in tools]

# Type inference works automatically!
composio = Composio(provider=MyCustomProvider())
tools = composio.tools.get(user_id="user", toolkits=["github"])
# tools: list[MyCustomTool] - correctly inferred
```

### Supported Providers

Type inference is supported for all built-in providers:

| Provider | Tool Type |
| - | - |
| OpenAI | `ChatCompletionToolParam` |
| OpenAI Responses | `dict[str, Any]` |
| Anthropic | `ToolParam` |
| Google (GenAI) | `FunctionDeclaration` |
| Gemini | `FunctionDeclaration` |
| Google ADK | `Tool` |
| LangChain | `StructuredTool` |
| LangGraph | `StructuredTool` |
| LlamaIndex | `FunctionTool` |
| CrewAI | `Tool` |
| AutoGen | `FunctionTool` |
| OpenAI Agents | `FunctionTool` |
| Claude Agent SDK | `Tool` |

### Backward Compatibility

This change is fully backward compatible:

* Existing code continues to work without modifications
* Type inference is opt-in via static type checkers
* No runtime behavior changes
* No migration required

**Jan 30, 2026**

Tool schemas are now cleaner for optional fields by removing redundant anyOf null constructs

## Simplified Schemas for Optional Fields

Tool schemas are now cleaner for optional fields by removing redundant `anyOf: [{type}, {type: "null"}]` constructs.

## Background: How JSON Schema Handles Optional Fields

In JSON Schema, there are two distinct concepts:

| Concept | Meaning | How it's expressed |
| - | - | - |
| **Optional** | Field can be omitted entirely | Field is NOT in the `required` array |
| **Nullable** | Field accepts `null` as a value | `anyOf: [{type}, {type: "null"}]` |

Previously, our schemas used `anyOf` with null type for all optional fields—even when the field wasn't in `required`. This was redundant: if a field can be omitted, explicitly marking it as "accepts null" adds no value.

## What Changed

For fields that are **not in the `required` array**, the schema processing now:

* Removes the redundant `{type: "null"}` from `anyOf` arrays
* Removes `default: null` since it's implied by being optional
* Flattens single-type `anyOf` to direct `type` declarations

## Before vs After

For example, the `page_token` field in `GOOGLECALENDAR_LIST_CALENDARS` (which is optional/not required):

**Previous (verbose):**

```json theme={null}
{
  "page_token": {
    "anyOf": [
      { "type": "string" },
      { "type": "null" }
    ],
    "default": null,
    "description": "Token for the page of results to return...",
    "title": "Page Token"
  }
}
```

**Now (simplified):**

```json theme={null}
{
  "page_token": {
    "type": "string",
    "description": "Token for the page of results to return...",
    "title": "Page Token"
  }
}
```

## What's Preserved

* **Required nullable fields**: Fields in the `required` array that accept null still use `anyOf` with null type
* **Union types**: Fields accepting multiple value types (e.g., `string | number`) retain their full `anyOf` array

## Why This Matters

* **Fewer tokens**: Simpler schemas reduce token usage when tools are passed to LLMs
* **Better compatibility**: Some code generators and validators handle direct types better than `anyOf` constructs
* **Clearer semantics**: Non-required fields don't need explicit null type—being optional already implies they can be omitted

**Jan 29, 2026**

Major release with Cloudflare Workers support, webhook verification updates, and Mastra v1 compatibility. Includes breaking changes for webhook APIs.

## SDK 0.6.0 Major Update: Cloudflare Workers Support and Breaking Changes

## Version Information

### TypeScript/JavaScript

* Package: `@composio/core` and all provider packages
* Version: `0.6.0`+

### Python

* Package: `composio` and all provider packages
* Version: `0.11.0`+

***

This major release focuses on Cloudflare Workers compatibility, platform-specific optimizations, and critical bug fixes. It includes **breaking changes** in both TypeScript and Python SDKs.

> [!WARNING]
>
> **Breaking Changes**: This release includes breaking changes that require code modifications:
>
> **TypeScript:**
>
> 1. Webhook verification: Now async + signature changed (must add `await` + new required params: `id`, `timestamp`)
> 2. Mastra provider updated to v1 API
>
> **Python:**
>
> 1. Webhook verification: Signature changed (new required parameters: `id`, `timestamp` - still synchronous)
>
> See the [Migration Guide](#migration-guide) for detailed upgrade instructions.

## Breaking Changes

### 1. Webhook Verification Breaking Changes

**TypeScript PR**: [#2436](https://github.com/ComposioHQ/composio/pull/2436) | **Python PR**: [#2361](https://github.com/ComposioHQ/composio/pull/2361)

The webhook verification API has breaking changes in both SDKs to support multiple webhook versions (v1, v2, v3) and edge runtime compatibility.

#### TypeScript: Now Async + Signature Changed

The `verifyWebhook()` method has **two breaking changes**: it's now async AND requires additional parameters.

**Before:**

```typescript theme={null}
import { Composio } from '@composio/core';

const composio = new Composio();

// Old signature - synchronous, fewer parameters
const payload = composio.triggers.verifyWebhook({
  payload: req.body.toString(),
  signature: req.headers['x-composio-signature'] as string,
  secret: process.env.COMPOSIO_WEBHOOK_SECRET!,
});
// Returns: TriggerEvent
```

**After:**

```typescript theme={null}
import { Composio } from '@composio/core';

const composio = new Composio();

// New signature - async, requires id and timestamp
const result = await composio.triggers.verifyWebhook({
  id: req.headers['webhook-id'] as string, // NEW: required
  payload: req.body.toString(),
  secret: process.env.COMPOSIO_WEBHOOK_SECRET!,
  signature: req.headers['webhook-signature'] as string, // header name changed
  timestamp: req.headers['webhook-timestamp'] as string, // NEW: required
  tolerance: 300, // optional, default 300 seconds
});
// Returns: VerifyWebhookResult with version info
```

**Key Changes:**

* ⚠️ **Now async** - Must use `await`
* ⚠️ New required parameter: `id` (from `webhook-id` header)
* ⚠️ New required parameter: `timestamp` (from `webhook-timestamp` header)
* ⚠️ Header name changed: `x-composio-signature` → `webhook-signature`
* ⚠️ Return type changed: `TriggerEvent` → `VerifyWebhookResult`

**Why?**

* Cloudflare Workers compatibility - uses Web Crypto API instead of `node:crypto`
* Supports v1, v2, and v3 webhook formats with improved signature verification

***

#### Python: Signature Changed (v1/v2/v3 Support)

The method signature changed to support new webhook versions and requires additional headers.

**Before:**

```python theme={null}
from composio import Composio

composio = Composio()

# Old signature - fewer parameters
event = composio.triggers.verify_webhook(
    payload=request.get_data(as_text=True),
    signature=request.headers.get('x-composio-signature'),
    secret=os.environ['COMPOSIO_WEBHOOK_SECRET'],
)
# Returns: TriggerEvent
```

**After:**

```python theme={null}
from composio import Composio

composio = Composio()

# New signature - requires id and timestamp headers
result = composio.triggers.verify_webhook(
    id=request.headers.get('webhook-id'),           # NEW: required
    payload=request.get_data(as_text=True),
    secret=os.environ['COMPOSIO_WEBHOOK_SECRET'],
    signature=request.headers.get('webhook-signature'),  # header name changed
    timestamp=request.headers.get('webhook-timestamp'),  # NEW: required
    tolerance=300,  # optional
)
# Returns: VerifyWebhookResult with version info
```

**Key Changes:**

* ✅ **Still synchronous** (no `await` needed)
* ⚠️ New required parameter: `id` (webhook-id header)
* ⚠️ New required parameter: `timestamp` (webhook-timestamp header)
* ⚠️ Header name changed: `x-composio-signature` → `webhook-signature`
* ⚠️ Return type changed: `TriggerEvent` → `VerifyWebhookResult`
* ⚠️ All parameters now keyword-only (must use `param=value`)

**Why?** Supports v1, v2, and v3 webhook formats with improved signature verification.

***

### 2. Mastra v1 Provider Update

**PR**: [#2433](https://github.com/ComposioHQ/composio/pull/2433)

The `@composio/mastra` provider has been updated to support Mastra v1, which has breaking API changes from v0.x.

#### Before (Mastra v0.x)

```typescript theme={null}
import { MastraProvider } from '@composio/mastra';
import { Mastra } from '@mastra/core';

const mastra = new Mastra({
  /* v0 config */
});
const provider = new MastraProvider();

// v0 API usage
const tools = await provider.wrapTools(composioTools);
```

#### After (Mastra v1)

```typescript theme={null}
import { MastraProvider } from '@composio/mastra';
import { Mastra } from '@mastra/core';

const mastra = new Mastra({
  /* v1 config */
});
const provider = new MastraProvider({ mastra });

// v1 API - different tool format
const tools = await provider.wrapTools(composioTools);
```

#### Changes Required

1. **Update Mastra dependency**: `npm install @mastra/core@latest`
2. **Update provider initialization**: Pass Mastra instance to provider
3. **Update tool handling**: Mastra v1 uses different tool schema format
4. **Check Zod version**: Mastra v1 supports both Zod v3 and v4
5. **Check Node.js version**: Mastra v1 requires [Node.js v22.13.0](https://mastra.ai/guides/migrations/upgrade-to-v1/overview#update-nodejs-version) or higher

> [!NOTE]
>
> We've added comprehensive E2E tests for both Zod v3 and v4 compatibility with Mastra v1 and Tool Router integration.

***

## Major Features

### 3. Platform-Specific File Tool Modifier

**PR**: [#2437](https://github.com/ComposioHQ/composio/pull/2437)

Separate implementations for Node.js and Cloudflare Workers to optimize file handling for each runtime.

**Key Improvements:**

* **Node.js**: Uses native file system APIs for better performance
* **Cloudflare Workers**: Uses platform-specific APIs, avoids Node.js-only code
* **Automatic selection**: SDK automatically picks the right implementation
* **No code changes needed**: Works transparently

> [!NOTE]
>
> **Related Change**: This platform-agnostic approach is why `composio.triggers.verifyWebhook()` became async in [Breaking Change #1](#1-webhook-verification-breaking-changes). Node.js `node:crypto` is mostly synchronous, but the standard `globalThis.crypto` (Web Crypto API) available in Cloudflare Workers is async. To support both platforms with a single API, the method had to become async.

***

### 4. Platform-Specific Config Defaults

**PR**: [#2437](https://github.com/ComposioHQ/composio/pull/2437)

Different default configurations for different runtimes to optimize behavior.

Changed the `autoUploadDownloadFiles` default configuration for the Cloudflare Workers runtime, to avoid triggering runtime errors on unsupported features.

**Cloudflare Workers defaults:**

```typescript theme={null}
{
  autoUploadDownloadFiles: false; // We don't currently support file uploads/downloads in Cloudflare Workers
}
```

> [!WARNING]
>
> **Removed in a later release.** The `autoUploadDownloadFiles` flag described above was removed in the v0.8.0 / Python v0.12.0 release train. Automatic file handling is now off by default on every runtime, and you opt in with `dangerouslyAllowAutoUploadDownloadFiles` instead. See [SDKs remove legacy automatic file handling config](https://composio-preview.mintlify.site/docs/changelog/2026/04/24) for the full migration.

**Benefits:**

* **Zero config** for common use cases
* **Optimized** for each platform's strengths
* **Override** defaults when needed

***

### 5. Node Buffer → Uint8Array Refactoring

**PR**: [#2438](https://github.com/ComposioHQ/composio/pull/2438)

All `node:buffer` usage replaced with standard `Uint8Array` for universal compatibility.

**Impact:**

* Works in **Node.js and Cloudflare Workers**
* **ESLint rules** enforce this pattern going forward
* **Better type safety** with standard types
* **Fully backward compatible** - no code changes needed

> [!NOTE]
>
> **Why This Matters**: Removing Node.js-specific APIs like `node:buffer` and `node:crypto` enables Cloudflare Workers support. Cloudflare Workers don't have access to Node.js built-in modules, so we use Web Standard APIs (`Uint8Array`, `globalThis.crypto`) that work in both Node.js and Cloudflare Workers.

***

## Bug Fixes

### 6. Tool Fetching with Specific Version

**PR**: [#2518](https://github.com/ComposioHQ/composio/pull/2518)

Fixed issues when executing tools with version constraints.

#### Before (Bug)

```typescript theme={null}
// This would fail or fetch wrong version
await composio.tools.execute('GITHUB_CREATE_ISSUE', {
  userId: 'user_123',
  version: '1.2.0', // Version constraint ignored
  arguments: {
    /* ... */
  },
});
```

#### After (Fixed)

```typescript theme={null}
// Now correctly respects version constraint
await composio.tools.execute('GITHUB_CREATE_ISSUE', {
  userId: 'user_123',
  version: '1.2.0', // Version constraint honored
  arguments: {
    /* ... */
  },
});
```

**Test Coverage**: Added 174 new test cases to prevent regression.

***

### 7. Python JSON Schema Default Values

**PR**: [#2506](https://github.com/ComposioHQ/composio/pull/2506)

Fixed type coercion for stringified default values in JSON schemas.

#### Before (Bug)

```python theme={null}
# Schema with stringified default
{
  "type": "integer",
  "default": "42"  # String instead of int
}

# Would cause runtime errors
```

#### After (Fixed)

```python theme={null}
# SDK automatically coerces to correct type
{
  "type": "integer",
  "default": 42  # Properly coerced to int
}

# Works correctly
```

**Impact**: Fixes runtime errors with tools that have stringified defaults in their schemas.

***

### 8. Salesforce Type Error Fix

**PR**: [#2426](https://github.com/ComposioHQ/composio/pull/2426)

Fixed `SALESFORCE_CREATE_LEAD` type error with `custom_fields` parameter.

#### Before (Bug)

```python theme={null}
# Would fail with type error
composio.tools.execute('SALESFORCE_CREATE_LEAD', {
    'user_id': 'user_123',
    'arguments': {
        'custom_fields': {
            'CustomField__c': 'value'
        }
    }
})
```

#### After (Fixed)

```python theme={null}
# Now works correctly
composio.tools.execute('SALESFORCE_CREATE_LEAD', {
    'user_id': 'user_123',
    'arguments': {
        'custom_fields': {
            'CustomField__c': 'value'
        }
    }
})
```

**Technical Details**: Implemented proper support for `anyOf` and `allOf` JSON Schema constructs in Python SDK.

***

## Migration Guide

### Step 1: Update Dependencies

> [tab] npm
>
> ```bash theme={null}
> npm update @composio/core@latest # Update provider packages if using them npm update
>     @composio/openai@latest npm update @composio/anthropic@latest npm update @composio/vercel@latest
>     # etc.
> ```

> [tab] pnpm
>
> ```bash theme={null}
> pnpm update @composio/core@latest # Update provider packages if using them pnpm update
>     @composio/openai@latest pnpm update @composio/anthropic@latest pnpm update
>     @composio/vercel@latest # etc.
> ```

> [tab] yarn
>
> ```bash theme={null}
> yarn upgrade @composio/core@latest # Update provider packages if using them yarn upgrade
>     @composio/openai@latest yarn upgrade @composio/anthropic@latest yarn upgrade
>     @composio/vercel@latest # etc.
> ```

> [tab] pip
>
> ```bash theme={null}
> pip install --upgrade composio
> ```

> [tab] uv
>
> ```bash theme={null}
> uv pip install --upgrade composio
> ```

***

### Step 2: Update Webhook Verification (Required)

> [tab] TypeScript
>
> **Update signature with new parameters and add `await`:**
>
> ```typescript theme={null}
> // Before - old signature
> const payload = composio.triggers.verifyWebhook({
>   payload: req.body.toString(),
>   signature: req.headers['x-composio-signature'] as string,
>   secret: process.env.COMPOSIO_WEBHOOK_SECRET!,
> });
>
> // After - new signature with await and additional parameters
> const result = await composio.triggers.verifyWebhook({
>   id: req.headers['webhook-id'] as string, // NEW
>   payload: req.body.toString(),
>   secret: process.env.COMPOSIO_WEBHOOK_SECRET!,
>   signature: req.headers['webhook-signature'] as string, // header name changed
>   timestamp: req.headers['webhook-timestamp'] as string, // NEW
> });
>
> // Access the normalized payload and version info
> const event = result.payload;
> const version = result.version; // 'V1', 'V2', or 'V3'
> ```
>
> **Express.js Example:**
>
> ```typescript theme={null}
> import express from 'express';
> import { Composio } from '@composio/core';
>
> const app = express();
> const composio = new Composio();
>
> // Make route handler async
> app.post('/webhook', express.raw({ type: 'application/json' }), async (req, res) => {
>   try {
>     // New signature with all required headers
>     const result = await composio.triggers.verifyWebhook({
>       id: req.headers['webhook-id'] as string,
>       payload: req.body.toString(),
>       secret: process.env.COMPOSIO_WEBHOOK_SECRET!,
>       signature: req.headers['webhook-signature'] as string,
>       timestamp: req.headers['webhook-timestamp'] as string,
>     });
>
>     // Access verified webhook data
>     console.log('Webhook version:', result.version);
>     console.log('Received trigger:', result.payload.triggerSlug);
>
>     res.status(200).send('OK');
>   } catch (error) {
>     console.error('Webhook verification failed:', error);
>     res.status(401).send('Unauthorized');
>   }
> });
> ```
>
> **Cloudflare Workers Example:**
>
> ```typescript theme={null}
> import { Composio } from '@composio/core';
>
> export default {
>   async fetch(request: Request, env: Env): Promise<Response> {
>     const composio = new Composio({ apiKey: env.COMPOSIO_API_KEY });
>
>     try {
>       const body = await request.text();
>
>       // Now works in Cloudflare Workers!
>       const result = await composio.triggers.verifyWebhook({
>         id: request.headers.get('webhook-id') || '',
>         payload: body,
>         secret: env.COMPOSIO_WEBHOOK_SECRET,
>         signature: request.headers.get('webhook-signature') || '',
>         timestamp: request.headers.get('webhook-timestamp') || '',
>       });
>
>       // Process verified webhook
>       console.log('Trigger:', result.payload.triggerSlug);
>
>       return new Response('OK', { status: 200 });
>     } catch (error) {
>       return new Response('Unauthorized', { status: 401 });
>     }
>   },
> };
> ```

> [tab] Python
>
> **Update signature to include new required parameters:**
>
> ```python theme={null}
> # Before - old signature
> event = composio.triggers.verify_webhook(
>     payload=request.get_data(as_text=True),
>     signature=request.headers.get('x-composio-signature'),
>     secret=os.environ['COMPOSIO_WEBHOOK_SECRET'],
> )
>
> # After - new signature with additional parameters
> result = composio.triggers.verify_webhook(
>     id=request.headers.get('webhook-id'),           # NEW
>     payload=request.get_data(as_text=True),
>     secret=os.environ['COMPOSIO_WEBHOOK_SECRET'],
>     signature=request.headers.get('webhook-signature'),  # header name changed
>     timestamp=request.headers.get('webhook-timestamp'),  # NEW
> )
>
> # Access the normalized payload
> event = result['payload']
> # Check webhook version
> version = result['version']  # 'V1', 'V2', or 'V3'
> ```
>
> **FastAPI Example:**
>
> ```python theme={null}
> from fastapi import FastAPI, Request, HTTPException
> from composio import Composio
> import os
>
> app = FastAPI()
> composio = Composio()
>
> @app.post("/webhook")
> def webhook(request: Request):  # Still synchronous!
>     # New signature with all required headers
>     try:
>         result = composio.triggers.verify_webhook(
>             id=request.headers.get('webhook-id', ''),
>             payload=request.body().decode('utf-8'),
>             secret=os.environ['COMPOSIO_WEBHOOK_SECRET'],
>             signature=request.headers.get('webhook-signature', ''),
>             timestamp=request.headers.get('webhook-timestamp', ''),
>         )
>
>         # Access normalized payload and version info
>         print(f"Webhook version: {result['version']}")
>         print(f"Trigger: {result['payload']['trigger_slug']}")
>
>         return {"success": True}
>     except Exception as e:
>         raise HTTPException(status_code=401, detail=str(e))
> ```
>
> **Flask Example:**
>
> ```python theme={null}
> from flask import Flask, request
> from composio import Composio
> import os
>
> app = Flask(__name__)
> composio = Composio()
>
> @app.route('/webhook', methods=['POST'])
> def webhook():  # Still synchronous!
>     try:
>         result = composio.triggers.verify_webhook(
>             id=request.headers.get('webhook-id', ''),
>             payload=request.get_data(as_text=True),
>             secret=os.environ['COMPOSIO_WEBHOOK_SECRET'],
>             signature=request.headers.get('webhook-signature', ''),
>             timestamp=request.headers.get('webhook-timestamp', ''),
>         )
>
>         # Process verified webhook
>         event = result['payload']
>         return 'OK', 200
>     except Exception as e:
>         return 'Unauthorized', 401
> ```

***

### Step 3: Update Mastra Integration (If Using)

**Only required if you use `@composio/mastra` provider**

> [tab] npm
>
> ```bash theme={null}
> # Update to Mastra v1 npm install @mastra/core@latest @composio/mastra@latest
> ```

> [tab] pnpm
>
> ```bash theme={null}
> pnpm update @mastra/core@latest @composio/mastra@latest
> ```

> [tab] yarn
>
> ```bash theme={null}
> yarn upgrade @mastra/core@latest @composio/mastra@latest
> ```

**Update your code:**

```typescript theme={null}
// Before
import { MastraProvider } from '@composio/mastra';

const provider = new MastraProvider();

// After
import { MastraProvider } from '@composio/mastra';
import { Mastra } from '@mastra/core';

const mastra = new Mastra({
  // Your Mastra v1 config
});

const provider = new MastraProvider({ mastra });
```

> [!NOTE]
>
> **Zod Compatibility**: Mastra v1 works with both Zod v3 and v4. We test both versions in CI to ensure compatibility.

***

### Step 4: Test Your Integration

1. **Run your test suite** to catch any issues
2. **Test webhook verification** if you use triggers
3. **Test file uploads/downloads** - behavior improved but API unchanged
4. **Test in your target runtime** (Node.js, Cloudflare Workers, etc.)

***

## Backward Compatibility

### Fully Compatible (No Changes Needed)

The following features work without any code changes:

* ✅ All tool execution APIs
* ✅ Connected accounts management
* ✅ Authentication flows
* ✅ Custom tools
* ✅ Tool Router sessions
* ✅ File upload/download (API unchanged, implementation improved)
* ✅ All provider packages (except Mastra)
* ✅ Python SDK usage (except webhook verification)

### Requires Changes

The following features require code updates:

* ⚠️ **Webhook verification (TypeScript)** - Must add `await` AND add `id` + `timestamp` parameters, update header names
* ⚠️ **Webhook verification (Python)** - Must add `id` + `timestamp` parameters, update header names (still synchronous)
* ⚠️ **Mastra integration (TypeScript only)** - Must update to v1 API

***

## Impact Summary

| Change | TypeScript Breaking | Python Breaking | Migration Required | Effort |
| - | - | - | - | - |
| Webhook verification - TypeScript | ✅ Yes (async + signature) | N/A | ✅ Required | Medium - Add `await` + params |
| Webhook verification - Python | N/A | ✅ Yes (signature only) | ✅ Required | Low - Add parameters |
| Mastra v1 support | ✅ Yes | N/A | ✅ Required (if using) | Medium - Update API |
| Platform-specific file modifier | ❌ No | ❌ No | ❌ Optional | None - Automatic |
| Config defaults | ❌ No | ❌ No | ❌ Optional | None - Automatic |
| Buffer → Uint8Array | ❌ No | N/A | ❌ Optional | None - Automatic |
| Tool version fix | ❌ No | ❌ No | ❌ Optional | None - Automatic |
| JSON schema coercion | ❌ No | ❌ No | ❌ Optional | None - Automatic |
| Salesforce type fix | ❌ No | ❌ No | ❌ Optional | None - Automatic |

***

## Cloudflare Workers Support

This release adds support for Cloudflare Workers:

```typescript theme={null}
import { Composio } from '@composio/core';

export default {
  async fetch(request: Request, env: Env): Promise<Response> {
    const composio = new Composio({
      apiKey: env.COMPOSIO_API_KEY,
    });

    // SDK now works in Cloudflare Workers!
    const tools = await composio.tools.get('user_123', {
      toolkits: ['github'],
    });

    const result = await composio.tools.execute('GITHUB_CREATE_ISSUE', {
      userId: 'user_123',
      arguments: {
        /* ... */
      },
    });

    return new Response(JSON.stringify(result));
  },
};
```

**Key Features Working in Cloudflare Workers:**

* ✅ Tool execution
* ✅ Connected accounts
* ✅ Webhook verification
* ✅ File upload/download
* ✅ Custom tools

***

## Testing

This release includes extensive E2E testing:

* ✅ **Node.js**: Both CJS and ESM compatibility tests
* ✅ **Cloudflare Workers**: Multiple test suites including Tool Router
* ✅ **Mastra v1**: Tests for both Zod v3 and v4
* ✅ **File handling**: Comprehensive tests for all platforms
* ✅ **Webhook verification**: Tests for all supported runtimes

**Total new tests**: 200+ test cases added across TypeScript and Python SDKs.

***

## Getting Help

If you encounter issues during migration:

1. **Check the docs**: [docs.composio.dev](https://composio-preview.mintlify.site/)
2. **Join our Discord**: [discord.composio.dev](https://discord.composio.dev)
3. **Open an issue**: [github.com/ComposioHQ/composio/issues](https://github.com/ComposioHQ/composio/issues)
4. **Email support**: [support@composio.dev](mailto:support@composio.dev)

***

## What's Next

Future releases will focus on:

* 🚀 Performance optimizations
* 🔧 More platform-specific improvements
* 📚 Enhanced TypeScript types
* 🛠️ New tool integrations
* 🔐 Advanced authentication flows

Stay tuned for updates!

**Jan 22, 2026**

Tool Router sessions now support timezone-aware assistive prompts configuration

## Experimental Assistive Prompts and API Updates

## Version Information

### TypeScript/JavaScript

* Package: `@composio/core`
* Version: `0.5.5`+

### Python

* Package: `composio`
* Version: `0.10.10`+

## New Features

### Experimental Assistive Prompt Configuration

Tool Router sessions now support experimental configuration for timezone-aware assistive prompts. When you provide a user's timezone, the session returns a contextual assistive prompt that includes timezone-specific guidance.

> [!WARNING]
>
> This is an experimental feature. The API may change or be removed in future versions.

> [tab] Python
>
> ```python theme={null}
> from composio import Composio
>
> composio = Composio()
>
> session = composio.tool_router.create(
>     user_id="user_123",
>     toolkits=["github"],
>     experimental={
>         "assistive_prompt": {
>             "user_timezone": "America/New_York",
>         }
>     },
> )
>
> # Access the generated assistive prompt
> if session.experimental:
>     print(session.experimental.assistive_prompt)
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from "@composio/core";
>
> const composio = new Composio();
>
> const session = await composio.toolRouter.create("user_123", {
>   toolkits: ["github"],
>   experimental: {
>     assistivePrompt: {
>       userTimezone: "America/New_York",
>     },
>   },
> });
>
> // Access the generated assistive prompt
> if (session.experimental) {
>   console.log(session.experimental.assistivePrompt);
> }
> ```

> [!NOTE]
>
> The `experimental` field is only available on sessions created with `create()`. Sessions retrieved with `use()` do not include the experimental data.

### Toolkit Endpoint Method

The toolkit retrieve response now includes `getCurrentUserEndpointMethod` (TypeScript) / `get_current_user_endpoint_method` (Python) to indicate the HTTP method for the current user endpoint.

## Breaking Changes

### Trigger Pagination: `page` Replaced with `cursor`

The `page` parameter in `listActive` / `list_active` for trigger instances has been replaced with `cursor` for cursor-based pagination. There was a bug in earlier APIs which caused `page` param to be ignored, going ahead for pagination please use `cursor` instead.

> [tab] Python
>
> ```python theme={null}
> # Before (deprecated)
> triggers = composio.triggers.list_active(page=1, limit=10)
>
> # After
> triggers = composio.triggers.list_active(cursor="cursor_string", limit=10)
> # Use response.next_cursor for the next page
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> // Before (deprecated)
> const triggers = await composio.triggers.listActive({ page: 1, limit: 10 });
>
> // After
> const triggers2 = await composio.triggers.listActive({ cursor: "cursor_string", limit: 10 });
> // Use response.nextCursor for the next page
> ```

## Impact Summary

| Change | Runtime Breaking | TypeScript Breaking | Migration Required |
| - | - | - | - |
| Experimental assistive prompts | No | No | No |
| `getCurrentUserEndpointMethod` field | No | No | No |
| `page` → `cursor` in triggers | Yes | Yes | Yes (if using `page`) |

## Migration Guide

If you are using the `page` parameter in `listActive` / `list_active`:

1. Replace `page` with `cursor`
2. For the first request, omit the `cursor` parameter or pass `undefined`/`None`
3. Use the `nextCursor` / `next_cursor` from the response for subsequent requests

**Jan 21, 2026**

The initiate method now only considers ACTIVE connected accounts when checking for duplicates

## Connected Account Initiate Now Filters by ACTIVE Status

## Version Information

### TypeScript/JavaScript

* Package: `@composio/core`
* Version: `0.5.4`+

### Python

* Package: `composio`
* Version: `0.10.9`+

***

The `initiate()` method now only considers ACTIVE connected accounts when checking for duplicates. Previously, expired or inactive accounts would incorrectly trigger the multiple accounts error.

## What Changed

When calling `connectedAccounts.initiate()`, the SDK now filters by `statuses: ["ACTIVE"]` when checking for existing accounts. This prevents expired or inactive accounts from blocking new connection creation.

### Before (Bug)

```typescript theme={null}
// Expired accounts would incorrectly trigger ComposioMultipleConnectedAccountsError
await composio.connectedAccounts.initiate(userId, authConfigId);
// ❌ Error: Multiple connected accounts found (even if they're all expired)
```

### After (Fixed)

```typescript theme={null}
// Only ACTIVE accounts are considered
await composio.connectedAccounts.initiate(userId, authConfigId);
// ✅ Works - expired/inactive accounts are ignored
```

## Affected SDKs

* **TypeScript**: `@composio/core`
* **Python**: `composio`

## Backward Compatibility

This is a bug fix with no breaking changes. The behavior now matches the expected intent of the multiple accounts check.

**Jan 20, 2026**

File handling modifiers now properly handle nested anyOf, oneOf, and allOf JSON Schema declarations Files from tool execution now use presigned URLs with configurable 1-hour default TTL

## File Upload/Download Fixes for latest tool with anyOf, oneOf, and allOf Schemas

## Version Information

### TypeScript/JavaScript

* Package: `@composio/core` and provider packages
* Version: `0.5.3`+

### Python

* Package: `composio` and provider packages
* Version: `0.10.8`+

***

The file handling modifiers now properly handle `file_uploadable` and `file_downloadable` properties nested within `anyOf`, `oneOf`, and `allOf` JSON Schema declarations. Previously, only direct child properties (and partial `allOf` support) were detected for file upload/download transformations.

> [!NOTE]
>
> We recommend updating to version `0.5.3` (TypeScript) or `0.10.8` (Python) or later to ensure file uploads and downloads work correctly with tools that use union or intersection types in their schemas.

## What Changed

### Before (Bug)

File properties inside `anyOf`, `oneOf`, or `allOf` were not detected:

```typescript theme={null}
// This schema's file_uploadable was NOT being processed
inputParameters: {
  type: 'object',
  properties: {
    fileInput: {
      anyOf: [
        {
          type: 'string',
          file_uploadable: true  // ❌ Not detected
        },
        {
          type: 'null'
        }
      ]
    }
  }
}
```

### After (Fixed)

File properties are now correctly detected and processed at any nesting level:

```typescript theme={null}
// Now properly detected and transformed
inputParameters: {
  type: 'object',
  properties: {
    fileInput: {
      anyOf: [
        {
          type: 'string',
          file_uploadable: true  // ✅ Detected and processed
        },
        {
          type: 'null'
        }
      ]
    }
  }
}
```

## Affected Scenarios

| Scenario | Before | After |
| - | - | - |
| `file_uploadable` in `anyOf` | Not detected | ✅ Works |
| `file_uploadable` in `oneOf` | Not detected | ✅ Works |
| `file_uploadable` in `allOf` | Not detected | ✅ Works |
| `file_downloadable` in `anyOf` | Not detected | ✅ Works |
| `file_downloadable` in `oneOf` | Not detected | ✅ Works |
| `file_downloadable` in `allOf` | Not detected | ✅ Works |
| Nested objects inside union types | Not detected | ✅ Works |
| Array items with union types | Not detected | ✅ Works |

## How to Update

### TypeScript/JavaScript

> [tab] npm
>
> ```bash theme={null}
> npm update @composio/core@latest
> ```

> [tab] pnpm
>
> ```bash theme={null}
> pnpm update @composio/core@latest
> ```

> [tab] yarn
>
> ```bash theme={null}
> yarn upgrade @composio/core@latest
> ```

### Python

> [tab] pip
>
> ```bash theme={null}
> pip install --upgrade composio
> ```

> [tab] uv
>
> ```bash theme={null}
> uv pip install --upgrade composio
> ```

> [tab] poetry
>
> ```bash theme={null}
> poetry update composio
> ```

## Backward Compatibility

This release is fully backward compatible:

* All existing code continues to work without modifications
* No migration required
* File upload/download for direct properties continues to work as before
* The fix only adds support for previously unsupported schema patterns

## Impact Summary

| Change | Runtime Breaking | TypeScript Breaking | Migration Required |
| - | - | - | - |
| `anyOf` support for file uploads | No | No | No |
| `oneOf` support for file uploads | No | No | No |
| `allOf` support for file uploads | No | No | No |
| `anyOf` support for file downloads | No | No | No |
| `oneOf` support for file downloads | No | No | No |
| `allOf` support for file downloads | No | No | No |

## File handling in tool execution now uses presigned URLs

## Summary

Files involved in tool execution are now shared via presigned URLs with a default TTL (time-to-live) of 1 hour. You can customize the file TTL through your project configuration.

## What changed

When tools return files (images, documents, exports, etc.), these files are now delivered as presigned URLs with a configurable TTL instead of non-expiring URLs. This provides:

* **Automatic cleanup** - Files expire after the configured TTL
* **Configurable retention** - Adjust file availability based on your application's needs

## Default behavior

All files returned from tool execution now have a **1 hour TTL** by default. After this period, the presigned URLs expire and files are no longer accessible.

## Configuring file TTL

You can adjust the file TTL to match your application's needs.

### Via Dashboard

1. Navigate to **Project Settings** in your Composio dashboard
2. Find the **File TTL** configuration option
3. Set your desired TTL value

### Via API

Use the Update Project Config API to programmatically configure the file TTL:

```bash theme={null}
curl -X PATCH "https://backend.composio.dev/api/v3/org/projects/config" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "fileTtl": 3600
  }'
```

## Impact

| Aspect | Before | After |
| - | - | - |
| File delivery | Non-expiring URLs | Presigned URLs with TTL |
| Default expiry | None | 1 hour |
| TTL customization | Not available | Configurable via project settings |

## Migration

No code changes are required. Your existing integrations will continue to receive file URLs as before, but these URLs will now expire after the configured TTL.

If your application stores or caches file URLs for later use, ensure you handle URL expiration appropriately by either:

* Downloading files before the TTL expires
* Re-executing the tool to obtain fresh URLs when needed
* Increasing the TTL via project settings to match your retention requirements

**Jan 14, 2026**

Auth config PATCH endpoint now preserves omitted fields instead of clearing them

## True PATCH Semantics for Auth Config Updates

## Version Information

### TypeScript/JavaScript

* Package: `@composio/core` and provider packages
* Version: `0.5.1`+

### Python

* Package: `composio-core` and provider packages
* Version: `0.10.7`+

***

The `PATCH /api/v3/auth_configs/{id}` endpoint now implements proper partial update semantics. Previously, omitting fields would clear them (behaving like PUT). Now, omitted fields are preserved—only explicitly provided fields are modified.

> [!WARNING]
>
> **Breaking Change**: If you relied on omitting fields to clear them, you must now explicitly send `null` or `[]`. See [Migration Guide](#migration-guide) below.

## What Changed

| Field | Before (Buggy) | After (Correct) |
| - | - | - |
| `credentials` | Required on every update | Optional—merged with existing |
| `tool_access_config` | Reset to `{}` if omitted | Preserved if omitted |
| `scopes` (type: default) | Cleared if omitted | Preserved if omitted |
| `restrict_to_following_tools` | Reset to `[]` if omitted | Preserved if omitted |

> [!NOTE]
>
> **Merge Behavior**: The `credentials` object is merged—send only the fields you want to change, and existing fields are preserved.

## New Capabilities

### Rotate a Single Credential Field

Update just `client_secret` without resending `client_id` or other fields:

> [tab] Python
>
> ```python theme={null}
> from composio import Composio
>
> composio = Composio()
>
> # Only send the field you want to update - other credentials are preserved
>
> composio.auth_configs.update(
>     "ac_yourAuthConfigId",
>     options={
>         "type": "custom",
>         "credentials": {
>             "client_secret": "new_rotated_secret",
>         },
>     },
> )
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from "@composio/core";
>
> const composio = new Composio();
>
> // Only send the field you want to update - other credentials are preserved
> await composio.authConfigs.update("ac_yourAuthConfigId", {
>   type: "custom",
>   credentials: {
>     client_secret: "new_rotated_secret",
>   },
> });
> ```

### Update Tool Restrictions Without Touching Credentials

Previously, this would fail because `credentials` was required. Now it works:

> [tab] Python
>
> ```python theme={null}
> from composio import Composio
>
> composio = Composio()
>
> # Update tool restrictions - credentials are automatically preserved
>
> composio.auth_configs.update(
>     "ac_yourAuthConfigId",
>     options={
>         "type": "custom",
>         "tool_access_config": {
>             "tools_available_for_execution": ["GMAIL_SEND_EMAIL", "GMAIL_READ_EMAIL"],
>         },
>     },
> )
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from "@composio/core";
>
> const composio = new Composio();
>
> // Note: TypeScript SDK currently requires credentials for custom type updates
> await composio.authConfigs.update("ac_yourAuthConfigId", {
>   type: "custom",
>   credentials: {
>     // Include existing credentials when using TS SDK
>   },
>   toolAccessConfig: {
>     toolsAvailableForExecution: ["GMAIL_SEND_EMAIL", "GMAIL_READ_EMAIL"],
>   },
> });
> ```

## Migration Guide

### Am I Affected?

**Yes**, if your code relied on omitting fields to clear them.

**No**, if you always send complete payloads or only use PATCH to update specific fields.

### How to Clear Fields Explicitly

| To Clear | Python SDK | TypeScript SDK |
| - | - | - |
| `tool_access_config` | `"tool_access_config": {"tools_available_for_execution": []}` | `toolAccessConfig: { toolsAvailableForExecution: [] }` |
| `scopes` (default) | `"scopes": ""` | `scopes: ""` (via HTTP API) |

> [tab] Python
>
> ```python theme={null}
> from composio import Composio
>
> composio = Composio()
>
> # Explicitly clear tool restrictions with empty array
>
> composio.auth_configs.update(
>     "ac_yourAuthConfigId",
>     options={
>         "type": "custom",
>         "tool_access_config": {
>             "tools_available_for_execution": [],
>         },
>     },
> )
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> import { Composio } from "@composio/core";
>
> const composio = new Composio();
>
> // Explicitly clear tool restrictions with empty array
> await composio.authConfigs.update("ac_yourAuthConfigId", {
>   type: "custom",
>   credentials: {
>     // Include existing credentials when using TS SDK
>   },
>   toolAccessConfig: {
>     toolsAvailableForExecution: [],
>   },
> });
> ```

### Raw HTTP API

For users calling the API directly:

```bash theme={null}
# Rotate single credential
curl -X PATCH "https://backend.composio.dev/api/v3/auth_configs/{id}" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type": "custom", "credentials": {"client_secret": "new_secret"}}'

# Clear tool restrictions
curl -X PATCH "https://backend.composio.dev/api/v3/auth_configs/{id}" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type": "custom", "tool_access_config": {"tools_available_for_execution": []}}'
```

**Jan 12, 2026**

Added waitForConnections property and other enhancements to Tool Router sessions

## Tool Router Improvements and New Features

## Version Information

### TypeScript/JavaScript

* Package: `@composio/core` and provider packages
* Version: `0.3.4` to `0.4.0`

### Python

* Package: `composio-core` and provider packages
* Version: `0.10.4` to `0.10.5`

## New Features

### 1. Wait for Connections Property

Added `waitForConnections` (TypeScript) / `wait_for_connections` (Python) property to manage connections configuration. This allows tool router sessions to wait for users to complete authentication before proceeding to the next step.

**TypeScript:**

```typescript theme={null}
const session = await composio.toolRouter.create(userId, {
  manageConnections: {
    enable: true,
    callbackUrl: 'https://example.com/callback',
    waitForConnections: true  // NEW
  }
});
```

**Python:**

```python theme={null}
session = tool_router.create(
    user_id="user_123",
    manage_connections={
        "enable": True,
        "callback_url": "https://example.com/callback",
        "wait_for_connections": True  # NEW
    }
)
```

### 2. Session-Specific Modifier Types

Introduced new modifier types for better session-based tool execution: `SessionExecuteMetaModifiers` and `SessionMetaToolOptions`.

**TypeScript:**

```typescript theme={null}
const tools = await session.tools({
  modifySchema: ({ toolSlug, toolkitSlug, schema }) => schema,
  beforeExecute: ({ toolSlug, toolkitSlug, sessionId, params }) => params,
  afterExecute: ({ toolSlug, toolkitSlug, sessionId, result }) => result
});
```

**Python:**

```python theme={null}
from composio.core.models import before_execute_meta, after_execute_meta

@before_execute_meta
def before_modifier(tool, toolkit, session_id, params):
    return params

@after_execute_meta
def after_modifier(tool, toolkit, session_id, response):
    return response

tools = session.tools(modifiers=[before_modifier, after_modifier])
```

### 3. Dedicated Method for Tool Router Meta Tools

Added `getRawToolRouterMetaTools` (TypeScript) / `get_raw_tool_router_meta_tools` (Python) method in the Tools class for fetching meta tools directly from a tool router session.

**TypeScript:**

```typescript theme={null}
const metaTools = await composio.tools.getRawToolRouterMetaTools('session_123', {
  modifySchema: ({ toolSlug, toolkitSlug, schema }) => {
    // Customize schema
    return schema;
  }
});
```

**Python:**

```python theme={null}
meta_tools = tools_model.get_raw_tool_router_meta_tools(
    session_id="session_123",
    modifiers=[schema_modifier]
)
```

## Internal Improvements

### 1. Performance Optimization

Eliminated unnecessary tool fetching during tool router execution, resulting in faster tool execution with fewer API calls.

### 2. Improved Architecture

Tool router sessions now fetch tools directly from the session API endpoint instead of using tool slugs, providing better consistency and reliability.

### 3. Simplified Implementation

Removed redundant tool schema fetching in execution paths, using a hardcoded 'composio' toolkit slug for meta tools.

## Backward Compatibility

This release is fully backward compatible:

* All existing code continues to work without modifications
* New properties are optional with sensible defaults
* New modifier types can be adopted incrementally
* Internal changes have no impact on public APIs
* No migration required

## Impact Summary

| Change | Runtime Breaking | TypeScript Breaking | Migration Required |
| - | - | - | - |
| `wait_for_connections` property | No | No | No |
| Session-specific modifiers | No | No | No |
| `getRawToolRouterMetaTools` method | No | No | No |
| Tool router uses session API | No | No | No |
| Optimized tool execution | No | No | No |

All changes follow semantic versioning principles and maintain full backward compatibility.

**Jan 9, 2026**

Shortened 181 tool enum names to ensure compatibility with 64-character limit in agent frameworks

## Tool Enum Name Shortening

Shortened tool enum names across 181 actions to ensure compatibility with all AI agent frameworks.

## Why This Change?

Some agent frameworks have a **64-character limit** on tool/function names. Several tool enums exceeded this limit, causing compatibility issues.

## No Action Required

**This change will not break your integration if you are using `latest` toolkit versions** or fetching tools dynamically. The SDK automatically resolves the correct tool names.

<details>
  <summary>**View All Enum Changes (181 tools)**</summary>

  | Old Enum | New Enum |
  | - | - |
  | `ACTIVE_TRAIL_GET_ACCOUNT_INTEGRATIONDATA_ACTIVECOMMERCE` | `ACTIVE_TRAIL_GET_ACCOUNT_INTEGRATIONDATA` |
  | `ACTIVE_TRAIL_GET_AUTOMATION_REPORTS_SMS_CAMPAIGN_SUMMARY_REPORT` | `ACTIVE_TRAIL_GET_AUTOMATION_REPORTS_SMS_CAMPAIGN_SUMMARY` |
  | `BIG_DATA_CLOUD_REVERSE_GEOCODING_WITH_TIMEZONE_API` | `BIG_DATA_CLOUD_REVERSE_GEOCODING_TIMEZONE_API` |
  | `CLICKSEND_RECHARGE_TRANSACTIONS_BY_TRANSACTION_ID_GET` | `CLICKSEND_RECHARGE_TXNS_BY_TXN_ID_GET` |
  | `CODEMAGIC_API_V3_VARIABLE_GROUPS_VARIABLE_GROUP_ID_UPDATE_GROUP` | `CODEMAGIC_API_V3_VARIABLE_GROUPS_VARIABLE_GROUP_ID_UPDATE` |
  | `COUPA_GET_ALL_FUNDS_TRANSFERS_IN_A_SPECIFIC_PAYMENT_BATCH_BY_PAYMENT_BATCH_ID` | `COUPA_GET_ALL_FUNDS_TRANSFERS_SPECIFIC_PAYMENT_BATCH` |
  | `COUPA_GET_PO_CONFIRMATION_IN_CANCELLED_STATUS_AND_NOT_EXPORTED` | `COUPA_GET_PO_CONFIRMATION_CANCELLED_STATUS_NOT_EXPORTED` |
  | `DATABRICKS_CATALOG_CREDENTIALS_GENERATE_TEMPORARY_SERVICE_CREDENTIAL` | `DATABRICKS_CATALOG_CREDS_GENERATE_TEMP_SERVICE_CRED` |
  | `DATABRICKS_CATALOG_CREDENTIALS_VALIDATE_CREDENTIAL` | `DATABRICKS_CATALOG_CREDS_VALIDATE_CRED` |
  | `DATABRICKS_CATALOG_EXTERNAL_METADATA_UPDATE_EXTERNAL_METADATA` | `DATABRICKS_CATALOG_EXTERNAL_METADATA_UPDATE_EXTERNAL` |
  | `DATABRICKS_CATALOG_RFA_GET_ACCESS_REQUEST_DESTINATIONS` | `DATABRICKS_CATALOG_RFA_GET_ACCESS_REQUEST_DESTS` |
  | `DATABRICKS_CATALOG_RFA_UPDATE_ACCESS_REQUEST_DESTINATIONS` | `DATABRICKS_CATALOG_RFA_UPDATE_ACCESS_REQUEST_DESTS` |
  | `DATABRICKS_CATALOG_TEMPORARY_PATH_CREDENTIALS_GENERATE_TEMPORARY_PATH_CREDENTIALS` | `DATABRICKS_CATALOG_TEMP_PATH_CREDS_GENERATE_TEMP_PATH_CREDS` |
  | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_GET_PERMISSION_LEVELS` | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_GET_PERM_LEVELS` |
  | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_GET_PERMISSIONS` | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_GET_PERMS` |
  | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_SET_PERMISSIONS` | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_SET_PERMS` |
  | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_UPDATE_PERMISSIONS` | `DATABRICKS_COMPUTE_CLUSTER_POLICIES_UPDATE_PERMS` |
  | `DATABRICKS_COMPUTE_INSTANCE_POOLS_GET_PERMISSION_LEVELS` | `DATABRICKS_COMPUTE_INSTANCE_POOLS_GET_PERM_LEVELS` |
  | `DATABRICKS_COMPUTE_INSTANCE_POOLS_UPDATE_PERMISSIONS` | `DATABRICKS_COMPUTE_INSTANCE_POOLS_UPDATE_PERMS` |
  | `DATABRICKS_COMPUTE_POLICY_COMPLIANCE_FOR_CLUSTERS_ENFORCE_COMPLIANCE` | `DATABRICKS_COMPUTE_POLICY_COMPL_FOR_CLUSTERS_ENFORCE_COMPL` |
  | `DATABRICKS_COMPUTE_POLICY_COMPLIANCE_FOR_CLUSTERS_GET_COMPLIANCE` | `DATABRICKS_COMPUTE_POLICY_COMPL_FOR_CLUSTERS_GET_COMPL` |
  | `DATABRICKS_DASHBOARDS_GENIE_DELETE_CONVERSATION_MESSAGE` | `DATABRICKS_DASHBOARDS_GENIE_DELETE_CONV_MESSAGE` |
  | `DATABRICKS_DASHBOARDS_GENIE_EXECUTE_MESSAGE_ATTACHMENT_QUERY` | `DATABRICKS_DASHBOARDS_GENIE_EXECUTE_MESSAGE_ATTACH_QUERY` |
  | `DATABRICKS_DASHBOARDS_GENIE_GET_MESSAGE_ATTACHMENT_QUERY_RESULT` | `DATABRICKS_DASHBOARDS_GENIE_GET_MESSAGE_ATTACH_QUERY_RESULT` |
  | `DATABRICKS_DASHBOARDS_GENIE_GET_MESSAGE_QUERY_RESULT_BY_ATTACHMENT` | `DATABRICKS_DASHBOARDS_GENIE_GET_MESSAGE_QUERY_RESULT_ATTACH` |
  | `DATABRICKS_DASHBOARDS_GENIE_LIST_CONVERSATION_MESSAGES` | `DATABRICKS_DASHBOARDS_GENIE_LIST_CONV_MESSAGES` |
  | `DATABRICKS_DASHBOARDS_LAKEVIEW_EMBEDDED_GET_PUBLISHED_DASHBOARD_TOKEN_INFO` | `DATABRICKS_DASHBOARDS_LAKEVIEW_EMBEDDED_GET_PUBLISHED_DASH` |
  | `DATABRICKS_DATABASE_DATABASE_GENERATE_DATABASE_CREDENTIAL` | `DATABRICKS_DATABASE_DATABASE_GENERATE_DATABASE_CRED` |
  | `DATABRICKS_IAM_PERMISSION_MIGRATION_MIGRATE_PERMISSIONS` | `DATABRICKS_IAM_PERM_MIGRATION_MIGRATE_PERMS` |
  | `DATABRICKS_IAMV2_WORKSPACE_IAM_V2_GET_WORKSPACE_ACCESS_DETAIL_LOCAL` | `DATABRICKS_IAMV2_WORKSPACE_IAM_V2_GET_WORKSPACE_ACCESS` |
  | `DATABRICKS_JOB_PERMISSION_LEVELS_GETPERMISSIONLEVELS` | `DATABRICKS_JOB_PERM_LEVELS_GETPERMISSIONLEVELS` |
  | `DATABRICKS_JOBS_POLICY_COMPLIANCE_FOR_JOBS_GET_COMPLIANCE` | `DATABRICKS_JOBS_POLICY_COMPL_FOR_JOBS_GET_COMPL` |
  | `DATABRICKS_MARKETPLACE_CONSUMER_INSTALLATIONS_CREATE` | `DATABRICKS_MKTPLACE_CONSUMER_INSTALLATIONS_CREATE` |
  | `DATABRICKS_MARKETPLACE_CONSUMER_INSTALLATIONS_DELETE` | `DATABRICKS_MKTPLACE_CONSUMER_INSTALLATIONS_DELETE` |
  | `DATABRICKS_MARKETPLACE_CONSUMER_INSTALLATIONS_UPDATE` | `DATABRICKS_MKTPLACE_CONSUMER_INSTALLATIONS_UPDATE` |
  | `DATABRICKS_MARKETPLACE_CONSUMER_LISTINGS_BATCH_GET` | `DATABRICKS_MKTPLACE_CONSUMER_LISTINGS_BATCH_GET` |
  | `DATABRICKS_MARKETPLACE_CONSUMER_PERSONALIZATION_REQUESTS_GET` | `DATABRICKS_MKTPLACE_CONSUMER_PERSONALIZATION_REQUESTS_GET` |
  | `DATABRICKS_MARKETPLACE_CONSUMER_PROVIDERS_BATCH_GET` | `DATABRICKS_MKTPLACE_CONSUMER_PROVIDERS_BATCH_GET` |
  | `DATABRICKS_MARKETPLACE_PROVIDER_EXCHANGES_DELETE_LISTING_FROM_EXCHANGE` | `DATABRICKS_MKTPLACE_PROVIDER_EXCHANGES_DELETE_LISTING` |
  | `DATABRICKS_MARKETPLACE_PROVIDER_PROVIDER_ANALYTICS_DASHBOARDS_CREATE` | `DATABRICKS_MKTPLACE_PROVIDER_ANALYTICS_DASHBOARDS_CREATE` |
  | `DATABRICKS_MARKETPLACE_PROVIDER_PROVIDER_ANALYTICS_DASHBOARDS_GET` | `DATABRICKS_MKTPLACE_PROVIDER_ANALYTICS_DASHBOARDS_GET` |
  | `DATABRICKS_MARKETPLACE_PROVIDER_PROVIDER_ANALYTICS_DASHBOARDS_GET_LATEST_VERSION` | `DATABRICKS_MKTPLACE_PROVIDER_ANALYTICS_DASH_GET_LATEST` |
  | `DATABRICKS_ML_FEATURE_ENGINEERING_DELETE_KAFKA_CONFIG` | `DATABRICKS_ML_FEATURE_ENG_DELETE_KAFKA_CONFIG` |
  | `DATABRICKS_ML_MATERIALIZED_FEATURES_DELETE_FEATURE_TAG` | `DATABRICKS_ML_MAT_FEATURES_DELETE_FEATURE_TAG` |
  | `DATABRICKS_ML_MATERIALIZED_FEATURES_GET_FEATURE_TAG` | `DATABRICKS_ML_MAT_FEATURES_GET_FEATURE_TAG` |
  | `DATABRICKS_ML_MATERIALIZED_FEATURES_UPDATE_FEATURE_TAG` | `DATABRICKS_ML_MAT_FEATURES_UPDATE_FEATURE_TAG` |
  | `DATABRICKS_ML_MODEL_REGISTRY_GET_PERMISSION_LEVELS` | `DATABRICKS_ML_MODEL_REGISTRY_GET_PERM_LEVELS` |
  | `DATABRICKS_PIPELINES_PIPELINES_GET_PERMISSION_LEVELS` | `DATABRICKS_PIPELINES_PIPELINES_GET_PERM_LEVELS` |
  | `DATABRICKS_QUALITYMONITORV2_QUALITY_MONITOR_V2_CREATE_QUALITY_MONITOR` | `DATABRICKS_QUALITYMONITORV2_QUALITY_MONITOR_V2_CREATE` |
  | `DATABRICKS_SERVING_SERVING_ENDPOINTS_CREATE_PROVISIONED_THROUGHPUT_ENDPOINT` | `DATABRICKS_SERVING_SERVING_ENDPOINTS_CREATE_PROV_THPUT` |
  | `DATABRICKS_SERVING_SERVING_ENDPOINTS_GET_PERMISSION_LEVELS` | `DATABRICKS_SERVING_SERVING_ENDPOINTS_GET_PERM_LEVELS` |
  | `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_ACCESS_POLICY_DELETE` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_ACCESS_POLICY_DELETE` |
  | `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_ACCESS_POLICY_GET` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_ACCESS_POLICY_GET` |
  | `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_ACCESS_POLICY_UPDATE` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_ACCESS_POLICY_UPDATE` |
  | `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_APPROVED_DOMAINS_DELETE` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_DOMAINS_DELETE` |
  | `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_APPROVED_DOMAINS_GET` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_APPROVED_DOMAINS_GET` |
  | `DATABRICKS_SETTINGS_AIBI_DASHBOARD_EMBEDDING_APPROVED_DOMAINS_UPDATE` | `DATABRICKS_SETTINGS_AIBI_DASH_EMBEDDING_DOMAINS_UPDATE` |
  | `DATABRICKS_SETTINGS_COMPLIANCE_SECURITY_PROFILE_GET` | `DATABRICKS_SETTINGS_COMPL_SECURITY_PROFILE_GET` |
  | `DATABRICKS_SETTINGS_DASHBOARD_EMAIL_SUBSCRIPTIONS_DELETE` | `DATABRICKS_SETTINGS_DASH_EMAIL_SUBS_DELETE` |
  | `DATABRICKS_SETTINGS_DASHBOARD_EMAIL_SUBSCRIPTIONS_GET` | `DATABRICKS_SETTINGS_DASH_EMAIL_SUBS_GET` |
  | `DATABRICKS_SETTINGS_DASHBOARD_EMAIL_SUBSCRIPTIONS_UPDATE` | `DATABRICKS_SETTINGS_DASH_EMAIL_SUBS_UPDATE` |
  | `DATABRICKS_SETTINGS_ENABLE_EXPORT_NOTEBOOK_GET_ENABLE_EXPORT_NOTEBOOK` | `DATABRICKS_SETTINGS_ENABLE_EXPORT_NOTEBOOK_GET_ENABLE` |
  | `DATABRICKS_SETTINGS_ENABLE_EXPORT_NOTEBOOK_PATCH_ENABLE_EXPORT_NOTEBOOK` | `DATABRICKS_SETTINGS_ENABLE_EXPORT_NOTEBOOK_PATCH_ENABLE` |
  | `DATABRICKS_SETTINGS_ENABLE_NOTEBOOK_TABLE_CLIPBOARD_GET_ENABLE_NOTEBOOK_TABLE_CLIPBOARD` | `DATABRICKS_SETTINGS_ENABLE_NOTEBOOK_TABLE_CLIPBOARD_GET` |
  | `DATABRICKS_SETTINGS_ENABLE_NOTEBOOK_TABLE_CLIPBOARD_PATCH_ENABLE_NOTEBOOK_TABLE_CLIPBOARD` | `DATABRICKS_SETTINGS_ENABLE_NOTEBOOK_TABLE_CLIPBOARD_PATCH` |
  | `DATABRICKS_SETTINGS_ENABLE_RESULTS_DOWNLOADING_GET_ENABLE_RESULTS_DOWNLOADING` | `DATABRICKS_SETTINGS_ENABLE_RESULTS_DOWNLOADING_GET_ENABLE` |
  | `DATABRICKS_SETTINGS_LLM_PROXY_PARTNER_POWERED_WORKSPACE_DELETE` | `DATABRICKS_SETTINGS_LLM_PROXY_PARTNER_WORKSPACE_DELETE` |
  | `DATABRICKS_SETTINGS_LLM_PROXY_PARTNER_POWERED_WORKSPACE_UPDATE` | `DATABRICKS_SETTINGS_LLM_PROXY_PARTNER_WORKSPACE_UPDATE` |
  | `DATABRICKS_SETTINGS_NOTIFICATION_DESTINATIONS_CREATE` | `DATABRICKS_SETTINGS_NOTIF_DESTS_CREATE` |
  | `DATABRICKS_SETTINGS_NOTIFICATION_DESTINATIONS_DELETE` | `DATABRICKS_SETTINGS_NOTIF_DESTS_DELETE` |
  | `DATABRICKS_SETTINGS_NOTIFICATION_DESTINATIONS_UPDATE` | `DATABRICKS_SETTINGS_NOTIF_DESTS_UPDATE` |
  | `DATABRICKS_SETTINGS_TOKEN_MANAGEMENT_GET_PERMISSION_LEVELS` | `DATABRICKS_SETTINGS_TOKEN_MGMT_GET_PERM_LEVELS` |
  | `DATABRICKS_SETTINGS_TOKEN_MANAGEMENT_GET_PERMISSIONS` | `DATABRICKS_SETTINGS_TOKEN_MGMT_GET_PERMS` |
  | `DATABRICKS_SETTINGS_TOKEN_MANAGEMENT_SET_PERMISSIONS` | `DATABRICKS_SETTINGS_TOKEN_MGMT_SET_PERMS` |
  | `DATABRICKS_SETTINGS_TOKEN_MANAGEMENT_UPDATE_PERMISSIONS` | `DATABRICKS_SETTINGS_TOKEN_MGMT_UPDATE_PERMS` |
  | `DATABRICKS_SETTINGSV2_WORKSPACE_SETTINGS_V2_GET_PUBLIC_WORKSPACE_SETTING` | `DATABRICKS_SETTINGSV2_WORKSPACE_SETTINGS_V2_GET_PUBLIC` |
  | `DATABRICKS_SQL_STATEMENT_EXECUTION_CANCEL_EXECUTION` | `DATABRICKS_SQL_STATEMENT_EXEC_CANCEL_EXEC` |
  | `DATABRICKS_VECTORSEARCH_VECTOR_SEARCH_ENDPOINTS_CREATE_ENDPOINT` | `DATABRICKS_VECTORSEARCH_VECTOR_SEARCH_ENDPOINTS_CREATE` |
  | `DATABRICKS_VECTORSEARCH_VECTOR_SEARCH_INDEXES_UPSERT_DATA_VECTOR_INDEX` | `DATABRICKS_VECTORSEARCH_VECTOR_SEARCH_INDEXES_UPSERT_DATA` |
  | `DEPLOYHQ_DELETE_PROJECTS_PROJECT_BUILD_CACHE_FILES_IDENTIFIER` | `DEPLOYHQ_DELETE_PROJECTS_PROJECT_BUILD_CACHE_FILES` |
  | `DROPBOX_SIGN_EDIT_AND_RESEND_EMBEDDED_SIGNATURE_REQUEST_WITH_TEMPLATE` | `DROPBOX_SIGN_EDIT_RESEND_EMBEDDED_SIGNATURE_REQUEST_TEMPLATE` |
  | `GITHUB_CREATE_OR_UPDATE_CUSTOM_PROPERTIES_FOR_AN_ORGANIZATION` | `GITHUB_CREATE_OR_UPDATE_CUSTOM_PROPERTIES_FOR_AN_ORG` |
  | `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_BIG_QUERY_LINKS_LIST` | `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_BIG_QUERY_LINKS` |
  | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_CHANNELGROUPS_LIST` | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_CHANNELGROUPS` |
  | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_CONVERSIONEVENTS_LIST` | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_CONVERSIONEVENTS` |
  | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_CUSTOMDIMENSIONS_LIST` | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_CUSTOMDIMENSIONS` |
  | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_DATASTREAMS_MEASUREMENTPROTOCOLSECRETS_LIST` | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_DATASTREAMS` |
  | `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_DISPLAY_VIDEO360_ADVERTISER_LINK_PROPOSALS_LIST` | `GOOGLE_ANALYTICS_ADMIN_PROPS_DV360_LINK_PROPOSALS_LIST` |
  | `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_DISPLAY_VIDEO360_ADVERTISER_LINKS_LIST` | `GOOGLE_ANALYTICS_ADMIN_PROPS_DV360_AD_LINKS_LIST` |
  | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_EXPANDEDDATASETS_LIST` | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_EXPANDEDDATASETS` |
  | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_FIREBASELINKS_LIST` | `GOOGLE_ANALYTICS_ANALYTICSADMIN_PROPERTIES_FIREBASELINKS` |
  | `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_GOOGLE_ADS_LINKS_LIST` | `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_GOOGLE_ADS` |
  | `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_SEARCH_ADS360_LINKS_LIST` | `GOOGLE_ANALYTICS_ANALYTICS_ADMIN_PROPERTIES_SEARCH_ADS360` |
  | `GOOGLE_ANALYTICS_PROPERTIES_DATASTREAMS_EVENTCREATERULES_LIST_ACTION` | `GOOGLE_ANALYTICS_PROPERTIES_DATASTREAMS_EVENTCREATERULES` |
  | `GOOGLE_CLASSROOM_COURSES_ANNOUNCEMENTS_ADD_ON_ATTACHMENTS_DELETE` | `GOOGLE_CLASSROOM_COURSES_ANNOUNCES_ADD_ON_ATTACHS_DELETE` |
  | `GOOGLE_CLASSROOM_COURSES_ANNOUNCEMENTS_ADD_ON_ATTACHMENTS_GET` | `GOOGLE_CLASSROOM_COURSES_ANNOUNCES_ADD_ON_ATTACHS_GET` |
  | `GOOGLE_CLASSROOM_COURSES_ANNOUNCEMENTS_ADD_ON_ATTACHMENTS_LIST` | `GOOGLE_CLASSROOM_COURSES_ANNOUNCES_ADD_ON_ATTACHS_LIST` |
  | `GOOGLE_CLASSROOM_COURSES_COURSE_WORK_ADD_ON_ATTACHMENTS_DELETE` | `GOOGLE_CLASSROOM_COURSES_COURSE_WORK_ADD_ON_ATTACHS_DELETE` |
  | `GOOGLE_CLASSROOM_COURSES_COURSE_WORK_MATERIALS_ADD_ON_ATTACHMENTS_LIST` | `GOOGLE_CLASSROOM_COURSES_COURSE_WORK_MATERIALS_ADD_ATTACHS` |
  | `GOOGLE_CLASSROOM_COURSES_COURSE_WORK_MATERIALS_GET_ADD_ON_CONTEXT` | `GOOGLE_CLASSROOM_COURSES_COURSE_WORK_MATERIALS_GET_ADD` |
  | `INSTANTLY_DFY_EMAIL_ACCOUNT_ORDERS_DOMAINS_PRE_WARMED_UP_LIST_POST` | `INSTANTLY_DFY_EMAIL_ACCOUNT_ORDERS_DOMAINS_PRE_WARMED_UP` |
  | `INSTANTLY_LIST_INBOX_PLACEMENT_BLACKLIST_AND_SPAM_ASSASSIN_REPORTS` | `INSTANTLY_LIST_INBOX_PLACEMENT_BLACKLIST_SPAM_ASSASSIN` |
  | `METABASE_DELETE_API_USER_KEY_VALUE_NAMESPACE_NAMESPACE_KEY_KEY` | `METABASE_DELETE_API_USER_KEY_VALUE_NAMESPACE_NAMESPACE_KEY` |
  | `METABASE_GET_API_AUTOMAGIC_DASHBOARDS_DATABASE_ID_CANDIDATES` | `METABASE_GET_API_AUTO_DASHBOARDS_DATABASE_ID_CANDIDATES` |
  | `METABASE_GET_API_AUTOMAGIC_DASHBOARDS_ENTITY_ENTITY_ID_OR_QUERY_CELL_CELL_QUERY` | `METABASE_GET_AUTOMAGIC_DASH_ENTITY_CELL_QUERY` |
  | `METABASE_GET_API_AUTOMAGIC_DASHBOARDS_ENTITY_ENTITY_ID_OR_QUERY_CELL_CELL_QUERY_RULE_PREFIX` | `METABASE_GET_AUTOMAGIC_DASH_ENTITY_CELL_QUERY_RULE` |
  | `METABASE_GET_API_AUTOMAGIC_DASHBOARDS_ENTITY_ENTITY_ID_OR_QUERY_QUERY_METADATA` | `METABASE_GET_AUTOMAGIC_DASH_ENTITY_QUERY_METADATA` |
  | `METABASE_GET_API_DASHBOARD_ID_PARAMS_PARAM_KEY_REMAPPING` | `METABASE_GET_API_DASH_ID_PARAMS_PARAM_KEY_REMAPPING` |
  | `METABASE_GET_API_DASHBOARD_ID_PARAMS_PARAM_KEY_VALUES` | `METABASE_GET_API_DASH_ID_PARAMS_PARAM_KEY_VALUES` |
  | `METABASE_POST_API_DASHBOARD_SAVE_COLLECTION_PARENT_COLLECTION_ID` | `METABASE_POST_API_DASH_SAVE_COLLECTION_PARENT_COLLECTION_ID` |
  | `METABASE_POST_API_EE_METABOT_TOOLS_CREATE_DASHBOARD_SUBSCRIPTION` | `METABASE_POST_API_EE_METABOT_TOOLS_CREATE_DASH_SUB` |
  | `METABASE_POST_API_EE_METABOT_TOOLS_GET_DASHBOARD_DETAILS` | `METABASE_POST_API_EE_METABOT_TOOLS_GET_DASH_DETAILS` |
  | `METABASE_POST_API_EE_METABOT_TOOLS_GET_DOCUMENT_DETAILS` | `METABASE_POST_API_EE_METABOT_TOOLS_GET_DOC_DETAILS` |
  | `SALESFORCE_GET_VALUES_FOR_ALL_PICKLIST_FIELDS_OF_A_RECORD_TYPE` | `SALESFORCE_GET_PICKLIST_VALUES_BY_RECORD_TYPE` |
  | `SALESFORCE_GET_UIAPI_LIST_INFO_ACCOUNT_RECENT_LISTS_ONLY_TRUE` | `SALESFORCE_GET_UI_API_LIST_INFO_RECENT` |
  | `SALESFORCE_GET_UIAPI_RELATED_LIST_PREFERENCES_BATCH_ACCOUNTRELATEDCONTACTLISTACCOUNTRELATEDOPPORTUNITYLIST` | `SALESFORCE_GET_RELATED_LIST_PREFS_BATCH` |
  | `SALESFORCE_SERVICE_CLOUD_VISITOR_SENSITIVE_DATA_RULE_TRIGGERED` | `SALESFORCE_SERVICE_CLOUD_VISITOR_SENSITIVE_DATA_RULE` |
  | `SAP_SUCCESSFACTORS_CREATE_OR_UPDATE_A_SUCCESSOR_NOMINATION_FOR_A_POSITION_OR_TALENT_POOL` | `SAP_SUCCESSFACTORS_CREATE_UPDATE_SUCCESSOR_NOMINATION` |
  | `SAP_SUCCESSFACTORS_DELETE_A_NOMINATION_FOR_A_POSITION_OR_TALENT_POOL` | `SAP_SUCCESSFACTORS_DELETE_NOMINATION_POSITION_TALENT_POOL` |
  | `SAP_SUCCESSFACTORS_GET_FEEDBACK_RECORDS_SERVICE_AVAILABLE_VIA_SAP_BUSINESS_ACCELERATOR_HUB` | `SAP_SUCCESSFACTORS_GET_FEEDBACK_RECORDS_SERVICE_AVAILABLE` |
  | `SAP_SUCCESSFACTORS_GET_ODATA_METADATA_FOR_CALIBRATION_SESSION_SERVICE` | `SAP_SUCCESSFACTORS_GET_ODATA_METADATA_CALIB_SESSION_SERVICE` |
  | `SAP_SUCCESSFACTORS_GET_ODATA_METADATA_FOR_CLOCK_INCLOCK_OUT_INTEGRATION_SERVICE` | `SAP_SUCCESSFACTORS_GET_ODATA_METADATA_CLOCK_INCLOCK_OUT` |
  | `SAP_SUCCESSFACTORS_GET_ODATA_METADATA_FOR_ONBOARDING_ADDITIONAL_SERVICES` | `SAP_SUCCESSFACTORS_GET_ODATA_METADATA_ONBOARDING_ADDL` |
  | `SAP_SUCCESSFACTORS_GET_PENDING_FEEDBACK_REQUESTS_OR_FEEDBACK_REQUEST_RECORDS` | `SAP_SUCCESSFACTORS_GET_PENDING_FEEDBACK_REQUESTS_FEEDBACK` |
  | `SAP_SUCCESSFACTORS_QUERY_A_CLOCK_IN_CLOCK_OUT_GROUP_BY_CODE_WITH_TIME_EVENT_TYPES` | `SAP_SUCCESSFACTORS_QUERY_CLOCK_CLOCK_OUT_GROUP_CODE_TIME` |
  | `SAP_SUCCESSFACTORS_QUERY_ALL_AVAILABLE_CLOCK_IN_CLOCK_OUT_GROUPS` | `SAP_SUCCESSFACTORS_QUERY_ALL_AVAILABLE_CLOCK_CLOCK_OUT` |
  | `SAP_SUCCESSFACTORS_REFRESH_METADATA_FOR_CONTINUOUS_FEEDBACK_SERVICE` | `SAP_SUCCESSFACTORS_REFRESH_METADATA_CONT_FEEDBACK_SERVICE` |
  | `SAP_SUCCESSFACTORS_UPDATE_THE_INTERNAL_USERNAME_OF_NEW_HIRES_AFTER_HIRING_PROCESS_IS_COMPLETED_FROM_ACTIVE_DIRECTORY` | `SAP_SUCCESSFACTORS_UPDATE_INTERNAL_USERNAME_NEW_HIRES_AFTER` |
  | `SENTRY_RETRIEVE_CUSTOM_INTEGRATION_ISSUE_LINKS_FOR_THE_GIVEN_SENTRY_ISSUE` | `SENTRY_RETRIEVE_CUSTOM_INTEG_ISSUE_LINKS_GIVEN_SENTRY_ISSUE` |
  | `SENTRY_RETRIEVE_THE_CUSTOM_INTEGRATIONS_CREATED_BY_AN_ORGANIZATION` | `SENTRY_RETRIEVE_THE_CUSTOM_INTEGS_CREATED_BY_AN_ORG` |
  | `SHOPIFY_ADJUSTS_THE_INVENTORY_LEVEL_OF_AN_INVENTORY_ITEM_AT_A_LOCATION` | `SHOPIFY_ADJUSTS_INVENTORY_LEVEL_INVENTORY_ITEM_AT_LOCATION` |
  | `SHOPIFY_CREATE_PRICE_RULES_PARAM_PRICE_RULE_ID_DISCOUNT_CODES` | `SHOPIFY_CREATE_PRICE_RULES_PARAM_PRICE_RULE_ID_DISCOUNT` |
  | `SHOPIFY_DELETE_FULFILLMENT_SERVICES_PARAM_FULFILLMENT_SERVICE_ID` | `SHOPIFY_DELETE_FULFILLMENT_SERVICES_PARAM_FULFILLMENT` |
  | `SHOPIFY_GET_COUNTRIES_PARAM_COUNTRY_ID_PROVINCES_PARAM_PROVINCE_ID` | `SHOPIFY_GET_COUNTRIES_PARAM_COUNTRY_ID_PROVINCES_PARAM` |
  | `SHOPIFY_GET_FULFILLMENT_ORDERS_PARAM_FULFILLMENT_ORDER_ID_LOCATIONS_FOR_MOVE` | `SHOPIFY_GET_FULFILLMENT_ORDERS_PARAM_FULFILLMENT_ORDER_ID` |
  | `SHOPIFY_GET_PRICE_RULES_PARAM_PRICE_RULE_ID_BATCH_PARAM_BATCH_ID` | `SHOPIFY_GET_PRICE_RULES_PARAM_PRICE_RULE_ID_BATCH_PARAM` |
  | `SHOPIFY_PERFORMS_BULK_OPERATIONS_FOR_MULTIPLE_CUSTOMER_ADDRESSES` | `SHOPIFY_PERFORMS_BULK_OPERATIONS_MULTIPLE_CUSTOMER_ADDRESSES` |
  | `SHOPIFY_RETRIEVE_A_LIST_OF_METAFIELDS_FROM_THE_RESOURCE_S_ENDPOINT` | `SHOPIFY_RETRIEVE_LIST_METAFIELDS_RESOURCE_S_ENDPOINT` |
  | `SHOPIFY_RETRIEVE_A_LIST_OF_PRODUCTS_BELONGING_TO_A_COLLECTION` | `SHOPIFY_RETRIEVE_LIST_PRODUCTS_BELONGING_COLLECTION` |
  | `SHOPIFY_RETRIEVES_A_LIST_OF_ALL_ARTICLE_TAGS_FROM_A_SPECIFIC_BLOG` | `SHOPIFY_RETRIEVES_LIST_ALL_ARTICLE_TAGS_SPECIFIC_BLOG` |
  | `SHOPIFY_RETRIEVES_A_LIST_OF_DISCOUNT_CODES_FOR_A_DISCOUNT_CODE_CREATION_JOB` | `SHOPIFY_RETRIEVES_LIST_DISCOUNT_CODES_DISCOUNT_CODE` |
  | `SHOPIFY_RETRIEVES_A_LIST_OF_STOREFRONT_ACCESS_TOKENS_THAT_HAVE_BEEN_ISSUED` | `SHOPIFY_RETRIEVES_LIST_STOREFRONT_ACCESS_TOKENS_THAT_HAVE` |
  | `SHOPIFY_RETRIEVES_FULFILLMENTS_ASSOCIATED_WITH_A_FULFILLMENT_ORDER` | `SHOPIFY_RETRIEVES_FULFILLMENTS_ASSOCIATED_FULFILLMENT_ORDER` |
  | `SHOPIFY_SETS_THE_INVENTORY_LEVEL_FOR_AN_INVENTORY_ITEM_AT_A_LOCATION` | `SHOPIFY_SETS_INVENTORY_LEVEL_INVENTORY_ITEM_AT_LOCATION` |
  | `SHOPIFY_SHOP_RETRIEVE_A_LIST_OF_METAFIELDS_FROM_THE_RESOURCE_S_ENDPOINT` | `SHOPIFY_SHOP_RETRIEVE_LIST_METAFIELDS_RESOURCE_S_ENDPOINT` |
  | `SHOPIFY_UPDATE_COUNTRIES_PARAM_COUNTRY_ID_PROVINCES_PARAM_PROVINCE_ID` | `SHOPIFY_UPDATE_COUNTRIES_PARAM_COUNTRY_ID_PROVINCES_PARAM` |
  | `STRIPE_DELETE_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS_SUBSCRIPTION_EXPOSED_ID` | `STRIPE_DELETE_CUSTOMER_SUB_EXPOSED_ID` |
  | `STRIPE_DELETE_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS_SUBSCRIPTION_EXPOSED_ID_DISCOUNT` | `STRIPE_DELETE_CUSTOMER_SUB_EXPOSED_ID_DISCOUNT` |
  | `STRIPE_GET_CUSTOMERS_CUSTOMER_BALANCE_TRANSACTIONS_TRANSACTION` | `STRIPE_GET_CUSTOMERS_CUSTOMER_BALANCE_TXNS_TXN` |
  | `STRIPE_GET_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS_SUBSCRIPTION_EXPOSED_ID` | `STRIPE_GET_CUSTOMERS_CUSTOMER_SUBS_SUB_EXPOSED_ID` |
  | `STRIPE_GET_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS_SUBSCRIPTION_EXPOSED_ID_DISCOUNT` | `STRIPE_GET_CUSTOMERS_CUSTOMER_SUBS_SUB_EXPOSED_ID_DISCOUNT` |
  | `STRIPE_GET_V1_ACCOUNTS_CAPABILITIES_CAPABILITIES_ACCOUNTS_CAPABILITIES` | `STRIPE_GET_V1_ACCOUNTS_CAPABILITIES_CAPABILITIES_ACCOUNTS` |
  | `STRIPE_GET_V1_BILLING_CREDIT_BALANCE_TRANSACTIONS_OVERVIEW_BILLING_CREDIT_BALANCE_TRANSACTIONS` | `STRIPE_GET_V1_BILLING_CREDIT_BALANCE_TXNS_OVERVIEW_BILLING` |
  | `STRIPE_GET_V1_BILLING_PORTAL_CONFIGURATIONS_OVERVIEW_BILLING_PORTAL_CONFIGURATIONS` | `STRIPE_GET_V1_BILLING_PORTAL_CONFIGS_OVERVIEW_BILLING` |
  | `STRIPE_GET_V1_ENTITLEMENTS_ACTIVE_ENTITLEMENTS_ACTIVE_ENTITLEMENT` | `STRIPE_GET_V1_ENTITLEMENTS_ACTIVE_ENTITLEMENTS_ACTIVE` |
  | `STRIPE_GET_V1_FINANCIAL_CONNECTIONS_ACCOUNTS_OVERVIEW_FINANCIAL_CONNECTIONS_ACCOUNTS` | `STRIPE_GET_V1_FIN_CONNS_ACCOUNTS_OVERVIEW_FIN_CONNS_ACCOUNTS` |
  | `STRIPE_GET_V1_PAYMENT_METHOD_CONFIGURATIONS_LIST_PAYMENT_METHOD` | `STRIPE_GET_V1_PAYMENT_METHOD_CONFIGS_LIST_PAYMENT_METHOD` |
  | `STRIPE_GET_V1_PAYMENT_METHOD_CONFIGURATIONS_LIST_PAYMENT_METHOD2` | `STRIPE_GET_V1_PAYMENT_METHOD_CONFIGS_LIST_PAYMENT_METHOD2` |
  | `STRIPE_GET_V1_QUOTES_COMPUTED_UPFRONT_LINE_ITEMS_LIST_ALL_QUOTES` | `STRIPE_GET_V1_QUOTES_COMPUTED_UPFRONT_LINE_ITEMS_LIST_ALL` |
  | `STRIPE_GET_V1_REPORTING_REPORT_TYPES_OVERVIEW_REPORTING_REPORT_TYPES` | `STRIPE_GET_V1_REPORTING_REPORT_TYPES_OVERVIEW_REPORTING` |
  | `STRIPE_GET_V1_TEST_HELPERS_TEST_CLOCKS_DELETE_A_TEST_TEST_HELPERS_TEST_CLOCKS` | `STRIPE_GET_V1_TEST_HELPERS_TEST_CLOCKS_DELETE_TEST_TEST` |
  | `STRIPE_POST_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS_SUBSCRIPTION_EXPOSED_ID` | `STRIPE_POST_CUSTOMERS_CUSTOMER_SUBS_SUB_EXPOSED_ID` |
  | `STRIPE_POST_PAYMENT_RECORDS_ID_REPORT_PAYMENT_ATTEMPT_CANCELED` | `STRIPE_POST_PAYMENT_RECORDS_REPORT_ATTEMPT_CANCELED` |
  | `STRIPE_POST_PAYMENT_RECORDS_ID_REPORT_PAYMENT_ATTEMPT_INFORMATIONAL` | `STRIPE_POST_PAYMENT_RECORDS_REPORT_ATTEMPT_INFO` |
  | `STRIPE_POST_TAX_TRANSACTIONS_CREATE_FROM_CALCULATION_OVERVIEW` | `STRIPE_POST_TAX_TXNS_CREATE_FROM_CALCULATION_OVERVIEW` |
  | `STRIPE_POST_TERMINAL_READERS_CANCEL_ACTION_SET_READER_DISPLAY` | `STRIPE_POST_TERMINAL_READERS_CANCEL_ACTION_SET_READER` |
  | `STRIPE_POST_TERMINAL_READERS_COLLECT_INPUTS_SET_READER_DISPLAY` | `STRIPE_POST_TERMINAL_READERS_COLLECT_INPUTS_SET_READER` |
  | `STRIPE_POST_TERMINAL_READERS_CONFIRM_PAYMENT_INTENT_SET_READER_DISPLAY` | `STRIPE_POST_TERMINAL_READERS_CONFIRM_PAYMENT_INTENT_SET` |
  | `STRIPE_POST_TEST_HELPERS_CUSTOMERS_FUND_CASH_BALANCE_FUND_A_TEST` | `STRIPE_POST_TEST_HELPERS_CUSTOMERS_FUND_CASH_BALANCE_FUND` |
  | `STRIPE_POST_TEST_HELPERS_TERMINAL_READERS_READER_PRESENT_PAYMENT_METHOD` | `STRIPE_POST_TEST_HELPERS_TERMINAL_READERS_READER_PRESENT` |
  | `STRIPE_POST_TEST_HELPERS_TERMINAL_READERS_READER_SUCCEED_INPUT_COLLECTION` | `STRIPE_POST_TEST_HELPERS_TERMINAL_READERS_READER_SUCCEED` |
  | `STRIPE_POST_TEST_HELPERS_TERMINAL_READERS_READER_TIMEOUT_INPUT_COLLECTION` | `STRIPE_POST_TEST_HELPERS_TERMINAL_READERS_READER_TIMEOUT` |
  | `STRIPE_POST_V1_BILLING_PORTAL_CONFIGURATIONS_OVERVIEW_BILLING_PORTAL_CONFIGURATIONS` | `STRIPE_POST_V1_BILLING_PORTAL_CONFIGS_OVERVIEW_BILLING` |
  | `STRIPE_POST_V1_PAYMENT_METHOD_CONFIGURATIONS_LIST_PAYMENT_METHOD2` | `STRIPE_POST_V1_PAYMENT_METHOD_CONFIGS_LIST_PAYMENT_METHOD2` |
  | `STRIPE_POST_V1_PAYMENT_METHOD_DOMAINS_PAYMENT_METHOD_DOMAINS2` | `STRIPE_POST_V1_PAYMENT_METHOD_DOMAINS_PAYMENT_METHOD` |
  | `STRIPE_POST_V1_PAYMENT_RECORDS_REPORT_PAYMENT_ATTEMPT_CANCELED_OVERVIEW` | `STRIPE_POST_V1_PAYMENT_RECORDS_REPORT_CANCELED` |
  | `STRIPE_POST_V1_PAYMENT_RECORDS_REPORT_PAYMENT_ATTEMPT_GUARANTEED_OVERVIEW` | `STRIPE_POST_V1_PAYMENT_RECORDS_REPORT_GUARANTEED` |
  | `STRIPE_POST_V1_PAYMENT_RECORDS_REPORT_PAYMENT_ATTEMPT_INFORMATIONAL_OVERVIEW` | `STRIPE_POST_V1_PAYMENT_RECORDS_REPORT_INFO` |
  | `STRIPE_POST_V1_PAYMENT_RECORDS_REPORT_PAYMENT_ATTEMPT_OVERVIEW` | `STRIPE_POST_V1_PAYMENT_RECORDS_REPORT_ATTEMPT` |
  | `STRIPE_POST_V1_TEST_HELPERS_CONFIRMATION_TOKENS_CREATE_A_TEST` | `STRIPE_POST_V1_TEST_HELPERS_CONFIRMATION_TOKENS_CREATE_TEST` |
  | `STRIPE_POST_V2_BILLING_METER_EVENT_ADJUSTMENTS_METER_EVENT_ADJUSTMENTS` | `STRIPE_POST_V2_BILLING_METER_EVENT_ADJUSTMENTS_METER_EVENT` |
</details>

## Migration

If you're referencing any affected tool enums by their old names, update to the new shortened names.

**Jan 8, 2026**

New project-level setting to require API key authentication for all MCP server requests

## Optional API Key Enforcement for MCP Servers

We've introduced a new project-level security setting that allows you to require API key authentication for all MCP server requests. This opt-in feature gives you fine-grained control over who can access your MCP endpoints.

> [!NOTE]
>
> **Opt-in today, default soon**: This feature is currently opt-in. Starting **March 1, 2026**, it will be enabled by default for new organizations. We recommend enabling it now to prepare your integrations.

## What's New

A new **"Require API Key for MCP"** toggle is now available in your Project Settings. When enabled, all requests to your MCP servers must include a valid Composio API key in the request headers.

| Setting | Default | Impact |
| - | - | - |
| `require_mcp_api_key` | `false` | Opt-in; no changes to existing behavior |

## How It Works

When the setting is **disabled** (default):

* MCP servers work without API key authentication
* Existing integrations continue to function unchanged

When the setting is **enabled**:

* All MCP requests must include the `x-api-key` header with a valid Composio API key
* Requests without a valid API key receive `401 Unauthorized`
* Only API keys belonging to the same project are accepted

### Request Examples

**Without API key (when enforcement is enabled):**

```bash theme={null}
curl -X POST "https://mcp.composio.dev/{your_mcp_server_url}" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'

# Response: 401 Unauthorized
```

**With API key:**

```bash theme={null}
curl -X POST "https://mcp.composio.dev/{your_mcp_server_url}" \
  -H "Content-Type: application/json" \
  -H "x-api-key: ak_your_api_key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'

# Response: 200 OK
```

## Enabling the Setting

### Via Dashboard

1. Navigate to [Project Settings](https://dashboard.composio.dev/~/project/settings/general?utm_source=docs\&utm_medium=content\&utm_campaign=changelog-01-08-26-mcp-api-key-enforcement)
2. Go to the **Project Configuration** tab
3. Find the **"Require API Key for MCP"** toggle
4. Enable the toggle

![MCP API Key Toggle in Project Settings](https://mintcdn.com/composio-preview/cL3pOAF8H-TYHF1S/assets/images/mcp-api-key-toggle.png?fit=max\&auto=format\&n=cL3pOAF8H-TYHF1S\&q=85\&s=fb910c994cf1a40eb53a2511cc2502d8)

### Via API

Update your project configuration using the API:

```bash theme={null}
curl -X PATCH "https://backend.composio.dev/api/v3/org/project/config" \
  -H "Content-Type: application/json" \
  -H "x-api-key: ak_your_api_key" \
  -d '{"require_mcp_api_key": true}'
```

**Response:**

```json theme={null}
{
  "require_mcp_api_key": true,
  "is_2FA_enabled": true,
  "mask_secret_keys_in_connected_account": true,
  "log_visibility_setting": "show_all"
}
```

### Via Code

> [tab] Python
>
> ```python theme={null}
> import requests
>
> response = requests.patch(
>     "https://backend.composio.dev/api/v3/org/project/config",
>     headers={
>         "Content-Type": "application/json",
>         "x-api-key": "ak_your_api_key"
>     },
>     json={"require_mcp_api_key": True}
> )
>
> print(response.json())
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> const response = await fetch(
>   "https://backend.composio.dev/api/v3/org/project/config",
>   {
>     method: "PATCH",
>     headers: {
>       "Content-Type": "application/json",
>       "x-api-key": "ak_your_api_key"
>     },
>     body: JSON.stringify({ require_mcp_api_key: true })
>   }
> );
>
> console.log(await response.json());
> ```

## When to Use This

Enable API key enforcement when you need to:

* **Prevent unauthorized access** to your MCP servers
* **Control which applications** can interact with your MCP endpoints
* **Add an extra security layer** for production deployments
* **Audit and track** MCP server usage through API key attribution

## API Reference

### Get Current Setting

```http theme={null}
GET /api/v3/org/project/config
```

### Update Setting

```http theme={null}
PATCH /api/v3/org/project/config
```

```json theme={null}
{
  "require_mcp_api_key": true
}
```

**Jan 7, 2026**

Tool execution errors now return standardized response format with status\_code and message fields

## Consistent Error Response Structure

Tool execution errors now return a standardized response format across all failure types. Previously, the `data` field was empty on errors—now it always includes `status_code` and `message`, matching the structure of successful responses.

## What Changed

All error responses from tool execution now include:

* `data.status_code`: HTTP status code (or `null` for non-HTTP errors)
* `data.message`: Detailed error message
* `error`: Same detailed message at the top level

## Before vs After

**Previous error response:**

```json theme={null}
{
  "data": {},
  "successfull": false,
  "error": "404 Client Error: Not Found for url: ...",
}
```

**New error response:**

```json theme={null}
{
  "data": {
      "http_error": "404 Client Error: Not Found for url: ...",
      "status_code": 404,
      "message": "Resource not found: The requested item does not exist"
  },
  "successfull": false,
  "error": "Resource not found: The requested item does not exist",
}
```

## Why This Matters

* **Easier parsing**: Agents and code can reliably access error details from `data.message` without special-casing empty `data` objects
* **Better debugging**: Detailed error messages replace generic HTTP error strings
* **Consistent schema**: Same response shape whether the tool succeeds or fails

***

## Union Types Preserved in Tool Schemas

Tool schemas now use standard JSON Schema `anyOf` for union types, providing accurate type information for LLMs and code generators.

## What Changed

Two changes affect how types appear in request/response schemas:

| Change | Scope | Description |
| - | - | - |
| **Nullable fields** | **All toolkits** | Fields that accept `null` now use `anyOf: [{type}, {type: "null"}]` instead of `type` + `nullable: true` |
| **Multi-type fields** | 157 toolkits | Fields accepting multiple value types (e.g., `string \| number`) preserve the full `anyOf` array instead of flattening to the first type |

> [accordion] Toolkits with multi-type union fields (157 total)
>
> **CRM & Sales:** active\_campaign, apollo, attio, autobound, capsule\_crm, firmao, forcemanager, gong, hubspot, instantly, intercom, kommo, leadfeeder, lever, magnetic, pipedrive, pipeline\_crm, salesforce, salesforce\_service\_cloud, zoominfo
>
> **Marketing & Email:** active\_trail, beamer, delighted, dripcel, enginemailer, mailerlite, moosend, mopinion, sendspark, toneden
>
> **Communication & Collaboration:** chmeetings, discord, helpdesk, helpwise, missive, slack, textit
>
> **Productivity & Project Management:** basecamp, clicksend, clientary, dart, fibery, monday, notion, onedesk, productboard, rocketlane, todoist
>
> **Developer Tools & APIs:** algolia, anonyflow, api\_ninjas, api\_sports, apify, appdrag, backendless, browserless, bubble, cloudconvert, cloudinary, cloudlayer, convertapi, databricks, datadog, datarobot, deepseek, deployhq, digital\_ocean, docmosis, docugenerate, encodian, gitea, gitlab, globalping, groqcloud, hookdeck, hyperbrowser, imgbb, imgix, kibana, neutrino, npm, openai, openrouter, parsera, parseur, phantombuster, pinecone, prismic, procfu, replicate, scrape\_do, serpapi, shotstack, snowflake, supabase, tavily, v0, vercel, writer, zenrows
>
> **E-commerce & Payments:** brex, btcpay\_server, coupa, flutterwave, gift\_up, lemon\_squeezy, quaderno, ramp, shopify, stripe, zoho\_invoice
>
> **HR & Recruiting:** ashby, bamboohr, recruitee
>
> **Data & Analytics:** amplitude, census\_bureau, college\_football\_data, currencyscoop, diffbot, ip2location, mixpanel, nasa, rosette\_text\_analytics, securitytrails, textrazor, twelve\_data
>
> **Documents & Files:** carbone, doc\_certs, documenso, dropbox, excel, files\_com, grist, pdf\_co, share\_point
>
> **Design & Media:** canva, canvas, claid\_ai, deepimage, heygen, metatextai
>
> **Customer Support:** freshdesk, retently, servicem8, sevdesk, storeganise
>
> **Calendar & Scheduling:** calendly, deadline\_funnel, etermin, googlecalendar
>
> **Social Media:** facebook, instagram, reddit
>
> **Location & Maps:** addresszen, geoapify, google\_maps, mapbox
>
> **Email Verification & Validation:** clearout, icypeas, neverbounce, zerobounce
>
> **Other Integrations:** bitwarden, canny, cardly, castingwords, confluence, formdesk, getform, habitica, headout, highergov, jira, keen\_io, landbot, moonclerk, one\_drive, outlook, googlesheets, resend, ritekit, sms\_alert, tapfiliate, thanks\_io, uptimerobot

## Before vs After

For example, the `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` request schema changes: **Previous (only a single type):**

```json theme={null}
{
  "timezone": {
    "default": 0,
    "description": "Timezone specification...",
    "title": "Timezone",
    "type": "string"
  }
}
```

**Now (Union types preserved):**

```json theme={null}
{
  "timezone": {
    "anyOf": [
      { "type": "string" },
      { "type": "number" }
    ],
    "default": 0,
    "description": "Timezone specification...",
    "title": "Timezone"
  }
}
```

Similarly, nullable fields like `page_token` in `GOOGLECALENDAR_LIST_CALENDARS`:

**Previous:**

```json theme={null}
{
  "page_token": {
    "default": null,
    "description": "Token for the page of results to return...",
    "nullable": true,
    "title": "Page Token",
    "type": "string"
  }
}
```

**Now:**

```json theme={null}
{
  "page_token": {
    "anyOf": [
      { "type": "string" },
      { "type": "null" }
    ],
    "default": null,
    "description": "Token for the page of results to return...",
    "title": "Page Token"
  }
}
```

## Why This Matters

* **Accurate schemas**: LLMs and code generators see the full set of allowed types
* **Better validation**: Input validation can now correctly accept all valid types, not just the first one

**Dec 31, 2025**

BEARER\_TOKEN auth deprecated for Airtable, Discord, Gmail, Google apps, and more

## Deprecating BEARER\_TOKEN auth scheme for 19 toolkits

We've **deprecated** the `BEARER_TOKEN` auth scheme for the following **19 toolkits**:

* `Airtable`
* `Discord`
* `Discordbot`
* `Gmail`
* `Google Classroom`
* `Google Search Console`
* `Google Calendar`
* `Google Docs`
* `Google Drive`
* `Google Slides`
* `Google Super`
* `Instagram`
* `Ntfy`
* `Sapling AI`
* `Slack`
* `Slackbot`
* `Tawk To`
* `TikTok`
* `Twitter`

### Recommendation

For these toolkits, we recommend using **alternative auth schemes** (for example, `OAUTH2`, `API_KEY`, or other toolkit-supported schemes) instead of `BEARER_TOKEN`.

### Backward compatibility (explicit)

This change is **fully backward compatible**:

* **Existing** auth configs and connected accounts created with `BEARER_TOKEN` **will continue to function**.
* **Creating new** auth configs and connected accounts with `BEARER_TOKEN` **will continue to work** (e.g., via API/SDK).
* To discourage new usage, `BEARER_TOKEN` auth configs / connected accounts **will not be displayed in the UI** for these toolkits.

**Dec 30, 2025**

Redesigned webhook structure following Standard Webhooks specification Proxy execute endpoint now supports binary data for file uploads and downloads

## Webhook Payload V3 - Lookahead Announcement

We're introducing **Webhook Payload V3** - a redesigned webhook structure that follows industry standards and provides better developer experience. This update affects how you receive trigger events via webhooks and Pusher.

## What's Changing?

### New Webhook Structure

We're adopting the [Standard Webhooks specification](https://github.com/standard-webhooks/standard-webhooks/blob/main/spec/standard-webhooks.md) for better consistency and reliability.

#### Headers

A new header will identify the webhook version:

```text theme={null}
x-composio-webhook-version: V3
```

#### Payload Structure

The payload structure is being reorganized to separate Composio metadata from trigger data:

**Before (V2):**

```json theme={null}
{
  "log_id": "log_TpxVOLXYnwXZ",
  "timestamp": "2025-12-23T13:06:07.695Z",
  "type": "gmail_new_gmail_message",
  "data": {
    "connection_id": "a1b2c3d4-5e6f-7a8b-9c0d-1e2f3a4b5c6d",
    "connection_nano_id": "ca_xYz9AbCdEfGh",
    "trigger_nano_id": "ti_JZFoTyYKbzhB",
    "trigger_id": "7f8e9d0c-1b2a-3c4d-5e6f-7a8b9c0d1e2f",
    "user_id": "usr-demo-12a3b4c5...",
    // ... actual trigger data mixed with metadata
  }
}
```

**After (V3):**

```json theme={null}
{
  "id": "msg_a1b2c3d4-5e6f-7a8b-9c0d-1e2f3a4b5c6d",
  "timestamp": "2025-12-23T13:06:07.695Z",
  "type": "composio.trigger.message",
  "metadata": {
    "log_id": "log_TpxVOLXYnwXZ",
    "trigger_slug": "GMAIL_NEW_GMAIL_MESSAGE",
    "auth_config_id": "ac_aCYTppZ5RsRc",
    "connected_account_id": "ca_cATYssZ5RrSc",
    "trigger_id": "ti_JZFoTyYKbzhB",
    "user_id": "pg-test-86c9fc84..."
  },
  "data": {
    // Clean trigger data without Composio metadata
  }
}
```

### Key Improvements

1. **Metadata Separation**: Composio-specific fields (connection IDs, trigger IDs, user IDs) are now in a dedicated `metadata` object
2. **Clean Data**: The `data` field now contains only the actual trigger payload without infrastructure metadata
3. **Standardized Type Field**: The `type` field now follows a consistent format (`composio.trigger.message`) instead of trigger-specific names like `gmail_new_gmail_message`
4. **Trigger Slug in Metadata**: The trigger slug (e.g., `GMAIL_NEW_GMAIL_MESSAGE`) is now available in `metadata.trigger_slug` for easy identification
5. **Standards Compliance**: Follows Standard Webhooks specification for better interoperability
6. **Consistent Structure**: Same payload structure for both webhooks and Pusher channels

## Migration Guide

### Updating Your Webhook Handlers

If you're accessing Composio metadata fields, update your code:

```python theme={null}
# Before (V2)
trigger_type = payload["type"]  # "gmail_new_gmail_message"
connection_id = payload["data"]["connection_id"]
trigger_id = payload["data"]["trigger_id"]
message_text = payload["data"]["message_text"]

# After (V3)
trigger_type = payload["type"]  # "composio.trigger.message"
trigger_slug = payload["metadata"]["trigger_slug"]  # "GMAIL_NEW_GMAIL_MESSAGE"
connection_id = payload["metadata"]["connected_account_id"]
trigger_id = payload["metadata"]["trigger_id"]
message_text = payload["data"]["message_text"]
```

```typescript theme={null}
// Before (V2)
const triggerSlug = payload.type;  // "gmail_new_gmail_message"
const connectionId = payload.data.connection_id;
const triggerId = payload.data.trigger_id;
const messageText = payload.data.message_text;

// After (V3)
const webhookType = payload.type;  // "composio.trigger.message"
const triggerSlug = payload.metadata.trigger_slug;  // "GMAIL_NEW_GMAIL_MESSAGE"
const connectionId = payload.metadata.connected_account_id;
const triggerId = payload.metadata.trigger_id;
const messageText = payload.data.message_text;
```

### Checking Webhook Version

You can detect the webhook version from headers:

```python theme={null}
webhook_version = headers.get("x-composio-webhook-version", "V2")
if webhook_version == "V3":
    # Use new structure
    metadata = payload["metadata"]
else:
    # Use old structure
    metadata = payload["data"]
```

## Rollout Timeline

* **December 2025**: V3 released, opt-in via project settings
* **February 15, 2026**: All new organizations will default to V3
* **Existing organizations**: Continue using V2 by default, can opt-in to V3 anytime

## How to Opt-In

1. Go to your project settings in the Composio dashboard
2. Navigate to the Webhooks section
3. Select "Webhook Payload Version: V3"
4. Update your webhook handlers to use the new structure
5. Test thoroughly before enabling in production

> [!NOTE]
>
> Organizations created **before February 15, 2026** will remain on V2 by default. You can switch to V3 at your convenience.
>
> Organizations created **on or after February 15, 2026** will use V3 by default.

## Benefits

* **Better DX**: Clear separation between metadata and actual trigger data
* **Standards Compliance**: Follows industry-standard webhook specifications
* **Consistency**: Same structure across webhooks and Pusher channels
* **Future-Proof**: Built on established standards for long-term compatibility

## Need Help?

If you have questions about migrating to V3 or need assistance:

* Join our [Discord community](https://discord.gg/composio)
* Check our [documentation](https://composio-preview.mintlify.site/)
* Contact support at [support@composio.dev](mailto:support@composio.dev)

## Binary Data Support for Proxy Execute

The `/api/v3/tools/execute/proxy` endpoint now supports binary data for both file uploads and downloads.

### File Uploads (`binary_body`)

To upload a file via the proxy, use the `binary_body` field in your request payload. This supports two approaches: specifying either a URL pointing to the file or providing the base64-encoded content directly.

#### Upload File via URL

```bash theme={null}
curl --location 'https://backend.composio.dev/api/v3/tools/execute/proxy' \
  --header 'accept: application/json' \
  --header 'x-api-key: <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
    "endpoint": "/upload-endpoint",
    "method": "POST",
    "connected_account_id": "<CONNECTED_ACCOUNT_ID>",
    "binary_body": {
      "url": "{URL_TO_THE_FILE}"
    }
  }'
```

#### Upload File via Base64 Content

Supported up to 4MB file size.

```bash theme={null}
curl --location 'https://backend.composio.dev/api/v3/tools/execute/proxy' \
  --header 'accept: application/json' \
  --header 'x-api-key: <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
    "endpoint": "/upload-endpoint",
    "method": "POST",
    "connected_account_id": "<CONNECTED_ACCOUNT_ID>",
    "binary_body": {
      "base64": "JVBERi0xLjQKJ...<base64_data>...",
      "content_type": "application/pdf"
    }
  }'
```

### File Downloads (`binary_data`)

When the proxied request returns a binary response (for example, a PDF or image), the proxy automatically uploads the file to temporary storage, and you receive a signed URL in the `binary_data` field. This enables you to download large files securely.

#### File Download Request

```bash theme={null}
curl --location 'https://backend.composio.dev/api/v3/tools/execute/proxy' \
  --header 'accept: application/json' \
  --header 'x-api-key: <YOUR_API_KEY>' \
  --header 'Content-Type: application/json' \
  --data '{
    "endpoint": "{YOUR_ENDPOINT}",
    "method": "GET",
    "connected_account_id": "{YOUR_CONNECTED_ACCOUNT_ID}"
  }'
```

#### File Download Response

```json theme={null}
{
  "data": {},
  "binary_data": {
    "url": "url to the file",
    "content_type": "content type of the file",
    "size": "size of the file",
    "expires_at": "expires at of the file"
  },
  "status": "status code of the response",
  "headers": "headers of the response"
}
```

### Summary

| Feature | Field | Description |
| - | - | - |
| File Upload via URL | `binary_body.url` | Provide a URL pointing to the file to upload |
| File Upload via Base64 | `binary_body.base64` + `binary_body.content_type` | Provide base64-encoded content (up to 4MB) |
| File Download | `binary_data` in response | Receive a signed URL to download binary responses |

We'd love your feedback on the new proxy execute capabilities. If anything feels unclear or you have suggestions for improvement, please reach out.

**Dec 29, 2025**

Base URL handling, auth method updates, and endpoint fixes across 16+ toolkits

## Authentication & Configuration Updates Across Multiple Toolkits

### Summary

This release includes significant authentication and configuration improvements across 16+ toolkits. The changes standardize Base URL handling, modernize authentication methods, and fix various endpoint configurations to improve reliability and flexibility.

| Toolkit | Change Type | Description |
| - | - | - |
| **Make** | Breaking | Removed Region field, replaced with Base URL |
| **Linear** | Improvement | Base URL is no longer configurable |
| **Kibana** | Improvement | Removed default value for Base URL |
| **Insightly** | Fix | Added default value for Pod field |
| **HelloBar** | Deprecated | Deprecated bearer authentication |
| **Gong** | Fix | Added default value for Base URL |
| **FormSite** | Deprecated | Deprecated bearer auth, added API key authentication |
| **DataScope** | Fix | Fixed Get Current User Endpoint |
| **D2L Brightspace** | Fix | Updated Get Current User Endpoint |
| **ClickUp** | Fix | Changed Base URL field type |
| **Bubble** | Breaking | Fixed Base URL field, removed Subdomain |
| **Brilliant Directories** | Fix | Implemented dynamic Base URL for user endpoint |
| **Braintree** | Improvement | Updated to production defaults with dynamic endpoints |
| **Auth0** | Improvement | Replaced hardcoded endpoint with dynamic tenant Base URL |

### Breaking Changes

We verified that active usage for these toolkits is practically zero before proceeding with these changes.

#### Make Toolkit

* **Removed Region field** in favor of explicit Base URL configuration
* Users must now provide the full Base URL instead of selecting a region
* This change provides more flexibility for custom deployments and regional endpoints

#### Bubble Toolkit

* **Removed Subdomain field** and restructured Base URL handling
* Users must now provide the complete Base URL instead of just the Subdomain
* This change standardizes URL configuration across all toolkits

### Deprecated Features

#### HelloBar Toolkit

* **Bearer authentication is now deprecated**
* While still functional, users are encouraged to migrate to newer authentication methods
* Support for bearer tokens will be removed in a future release

#### FormSite Toolkit

* **Bearer authentication deprecated** in favor of API key authentication
* New integrations should use API key authentication for improved security
* Existing bearer token implementations will continue to work but should be migrated

### Improvements & Fixes

#### Configuration Improvements

**Linear Toolkit** - Base URL is no longer a configurable field. The toolkit now uses a fixed endpoint, simplifying the authentication process.

**Kibana Toolkit** - Removed the default value for Base URL, allowing for more flexible deployment configurations. Users can now specify custom Kibana instances without overriding defaults.

**Gong Toolkit** - Added a sensible default value for Base URL to simplify initial setup. New users can connect without manually configuring the endpoint.

**Insightly Toolkit** - Added default value for the Pod field to streamline configuration. Reduces setup complexity for standard deployments.

**ClickUp Toolkit** - Fixed the Base URL field type for proper validation and handling. Ensures consistent URL formatting across all operations.

#### Dynamic Endpoint Updates

**Brilliant Directories Toolkit** - Implemented dynamic Base URL resolution for the Get Current User Endpoint. Automatically adapts to different deployment environments.

**Braintree Toolkit** - Updated configuration to use production defaults. Implemented dynamic endpoint resolution for better environment handling. Improved reliability for production deployments.

**Auth0 Toolkit** - Replaced hardcoded endpoints with dynamic tenant-based URL resolution. Supports multi-tenant deployments without manual configuration. Automatically constructs the correct endpoint based on the tenant configuration.

#### Endpoint Fixes

**DataScope Toolkit** - Fixed the Get Current User Endpoint to use the correct API path. Resolves authentication verification issues.

**D2L Brightspace Toolkit** - Updated the Get Current User Endpoint to match the latest API specifications. Ensures proper user identification and session validation.

### Migration Guide

For toolkits with breaking changes, please update your configurations as follows:

1. **Make**: Replace Region with the full Base URL (e.g., `https://us-east-1.make.com`)
2. **Bubble**: Replace Subdomain with the full Base URL (e.g., `https://myapp.bubbleapps.io`)

For deprecated authentication methods:

* **HelloBar & FormSite**: Generate new API keys from your account settings and update your authentication configuration

**Dec 26, 2025**

Auth config updates for Ashby, Freshdesk, Make, Mixpanel, Recall AI, and more

## Authentication Updates Across Multiple Toolkits

We've updated authentication configurations for several toolkits to improve security, fix issues, and support additional deployment options.

### Summary

| Toolkit | Change Type | Action Required |
| - | - | - |
| Ashby | Deprecated | No |
| Freshdesk | Deprecated | No |
| Freshservice | Deprecated | No |
| Make | Breaking | New auth config + user reconnect |
| Mixpanel | Fix | No |
| Recall AI | Breaking | New auth config + user reconnect |
| Relevance AI | Breaking | New auth config + user reconnect |
| SmartRecruiters | Breaking | New auth config + user reconnect |
| Supabase | Improvement | No |
| Trello | Deprecated | No |
| ZoomInfo | Deprecated | No |

### Breaking Changes

These toolkits had incorrect or outdated authentication configurations that needed fixing. We verified that active usage for these toolkits is practically zero before proceeding with these changes.

**Impact**: Existing connections will stop working. You'll need to create new auth configs and ask affected users to reconnect.

#### Make

Replaced region-based configuration with full base URL input. Users now provide the complete Make instance URL (e.g., `https://us2.make.com` or `https://us1.make.celonis.com`) instead of just a region code.

#### Recall AI

Updated from region-based to full base URL configuration. Fixed field descriptions and metadata. Updated categories to AI/Productivity/Communication and added proper documentation links.

#### Relevance AI

Simplified authentication by removing deprecated Project ID field. Added conditional mapping for region codes to API subdomains (AU→f1db6c, EU→d7b62b, US→bcbe5a). Region field now defaults to US.

#### SmartRecruiters

Fixed OAuth configuration with correct SmartRecruiters endpoints. Added proper default scopes for candidates, jobs, and users. Enabled PKCE and added refresh token support.

### Deprecated (Still Working)

These changes introduce new auth methods while keeping old ones functional:

#### Ashby

Added new API Key authentication scheme with automatic base64 encoding and proper authorization headers.

**No Action Required**: Old Basic Auth method is deprecated but continues to work. Existing connections are unaffected.

#### Freshdesk

Added new API Key authentication scheme requiring subdomain and API key with automatic base64 encoding.

**No Action Required**: Old Basic Auth method is deprecated but continues to work. Existing connections are unaffected.

#### Freshservice

Added new API Key authentication scheme requiring subdomain and API key with automatic base64 encoding.

**No Action Required**: Old Basic Auth method is deprecated but continues to work. Existing connections are unaffected.

#### Trello

Marked Bearer Token authentication as deprecated in favor of OAuth authentication.

**No Action Required**: Old Bearer auth continues to function. OAuth is recommended for new connections.

#### ZoomInfo

Added new OAuth2 authentication scheme with comprehensive scopes for contacts, companies, audiences, scoops, news, and intent data. Deprecated the old JWT-based Basic authentication. Password field now properly marked as secret.

**No Action Required**: Old JWT auth continues to function. New connections will use OAuth2.

### Non-Breaking Improvements

#### Mixpanel

Fixed region mapping logic for data residency. Added proper conditional evaluation to map regions to correct API hosts (EU, India, or Standard). Region field is now optional and defaults to Standard server. Service account secret now properly marked as secret.

**No Action Required**: Existing connections continue to work without changes.

#### Supabase

Changed `base_url` field type from `auth_config_field` to `connection_field` for both OAuth and API Key schemes. Updated base action logic to respect user-provided base URLs, enabling support for self-hosted Supabase instances.

**No Action Required**: Existing connections continue to work. Self-hosted instances now supported.

**Dec 22, 2025**

Deprecating 15 additional toolkits with no supported actions

## Toolkit Deprecation: Removing Empty Toolkits

### What's Changed

We're deprecating **15 toolkits** that currently have no supported actions. These toolkits will be reactivated once we add functional actions to them, ensuring you only see integrations that are ready to use.

### Deprecated Toolkits

The following toolkits are now deprecated:

* `BREATHEHR`, `DIXA`, `EGNYTE`, `EXPENSIFY`, `FREEAGENT`
* `GUSTO`, `NUTSHELL`, `OPENNUTRITION`, `OYSTERHR`, `RAKUTEN`
* `SALESFLARE`, `TEAMLEADER`, `WALGREENS`, `WHOOP`, `WIX`

### Impact on Your Integration

#### API Behavior Changes

**List Toolkits Endpoint**

The [GET /toolkits](https://composio-preview.mintlify.site/rest-api/toolkits/get-toolkits) endpoint will now exclude deprecated toolkits by default.

**Need to see deprecated toolkits?** Use the `include_deprecated` query parameter.

#### Backward Compatibility

**Your existing integrations are safe.** All other endpoints continue to work with deprecated toolkits:

* Retrieve the toolkit details
* Create auth configurations
* Manage connected accounts
* Configure MCP Servers

This ensures zero breaking changes to your current implementations.

### Why This Matters

This change helps you:

* **Focus on working integrations** - No clutter from non-functional toolkits
* **Avoid integration attempts** with toolkits that have no actions
* **Better developer experience** with a cleaner, more actionable toolkit list

### Questions?

If you have questions or need support with any deprecated toolkit, reach out to our team or check our [documentation](https://composio-preview.mintlify.site/).

**Dec 19, 2025**

Deprecating 60 toolkits with no supported actions to streamline the platform

## Toolkit Deprecation: Streamlining Our Platform

### What's Changed

We're deprecating **60 toolkits** that currently have no supported actions. These toolkits will be reactivated once we add functional actions to them, ensuring you only see integrations that are ready to use.

### Deprecated Toolkits

The following toolkits are now deprecated:

* `ACCELO`, `ADOBE`, `AERO_WORKFLOW`, `AMAZON`, `APEX27`
* `APPOINTO`, `APPSFLYER`, `ATLASSIAN`, `AUTH0`, `AXONAUT`
* `BATTLENET`, `BOLDSIGN`, `BRAINTREE`, `BREEZY_HR`, `BREX_STAGING`
* `BRIGHTPEARL`, `BROWSERHUB`, `CUSTOMER_IO`, `DEEL`, `DRIP_JOBS`
* `EPIC_GAMES`, `FACTORIAL`, `FITBIT`, `FRONT`, `GO_TO_WEBINAR`
* `GURU`, `HELCIM`, `HIGHLEVEL`, `ICIMS_TALENT_CLOUD`, `IDEA_SCALE`
* `KEAP`, `LASTPASS`, `LEVER_SANDBOX`, `LEXOFFICE`, `MANY_CHAT`
* `MBOUM`, `MICROSOFT_TENANT`, `MOXIE`, `ONCEHUB`, `POPTIN`
* `PRECORO`, `PRINTNODE`, `QUALAROO`, `RAVENSEOTOOLS`, `RING_CENTRAL`
* `RIPPLING`, `SAGE`, `SALESFORCE_MARKETING_CLOUD`, `SEISMIC`, `SMARTRECRUITERS`
* `TAPFORM`, `TERMINUS`, `TIMEKIT`, `TWITCH`, `VENLY`
* `VERO`, `VISME`, `WAVE_ACCOUNTING`, `WIZ`, `ZOHO_DESK`

### Impact on Your Integration

#### API Behavior Changes

**List Toolkits Endpoint**

The [GET /toolkits](https://composio-preview.mintlify.site/rest-api/toolkits/get-toolkits) endpoint will now exclude deprecated toolkits by default.

**Need to see deprecated toolkits?** Use the new `include_deprecated` query parameter.

#### Backward Compatibility

**Your existing integrations are safe.** All other endpoints continue to work with deprecated toolkits:

* Retrieve the toolkit details
* Create auth configurations
* Manage connected accounts
* Configure MCP Servers

This ensures zero breaking changes to your current implementations.

### Why This Matters

This change helps you:

* **Focus on working integrations** - No clutter from non-functional toolkits
* **Avoid integration attempts** with toolkits that have no actions
* **Better developer experience** with a cleaner, more actionable toolkit list

### Questions?

If you have questions or need support with any deprecated toolkit, reach out to our team or check our [documentation](https://composio-preview.mintlify.site/).

**Dec 16, 2025**

Cleaning up the Toolkits API by removing unused local toolkit fields

## Deprecation of is\_local\_toolkit Field and Removal of is\_local Query Parameter

We're cleaning up the Toolkits API by deprecating the `is_local_toolkit` response field and removing the `is_local` query parameter filter.

### What's Changing?

#### Response Field: `is_local_toolkit` (Deprecated)

The `is_local_toolkit` field in toolkit API responses is now **deprecated**. This field was originally intended to indicate whether a toolkit was local to a specific project, but it is no longer meaningful as no toolkits use this classification.

**Affected Endpoints:**

* `GET /api/v3/toolkits` - List toolkits
* `GET /api/v3/toolkits/{slug}` - Get single toolkit
* `GET /api/v3/toolkits/multi` - Get multiple toolkits

The field will continue to be returned in API responses for backward compatibility, but it will always return `false`. It is marked as `deprecated: true` in the OpenAPI specification.

#### Query Parameter: `is_local` (Removed)

The `is_local` query parameter filter has been **removed** from the following endpoints:

* `GET /api/v3/toolkits`
* `GET /api/v3/toolkits/multi`

This parameter was used to filter toolkits by their local status, but since no toolkits are classified as local, it served no practical purpose.

### Impact on Your Code

#### If You're Using the `is_local` Query Parameter

**Before:**

```typescript theme={null}
// This will no longer work
const toolkits = await fetch('/api/v3/toolkits?is_local=true');
```

**After:**

```typescript theme={null}
// Simply remove the is_local parameter
const toolkits = await fetch('/api/v3/toolkits');
```

#### If You're Reading the `is_local_toolkit` Response Field

The field will continue to be present in responses but will always return `false`. You can safely ignore this field or remove any logic that depends on it.

**Before:**

```typescript theme={null}
const toolkit = await composio.toolkits.get('github');
if (toolkit.is_local_toolkit) {
  // This condition will never be true
  handleLocalToolkit(toolkit);
}
```

**After:**

```typescript theme={null}
const toolkit = await composio.toolkits.get('github');
// Remove is_local_toolkit checks - they're no longer meaningful
```

**Dec 15, 2025**

Tool Router moves from experimental to stable in Python 0.10.1 and TypeScript 0.3.0

## Tool Router General Availability

The Composio SDKs achieved a significant milestone with Tool Router moving from experimental to stable production status in December 2025. The Tool Router is now a fully supported feature that enables creating isolated MCP sessions with scoped toolkit access across both Python 0.10.1 and TypeScript 0.3.0.

### Major Achievements

**Native Tool Execution:** Both SDKs now support direct tool execution through Tool Router sessions. The TypeScript implementation emphasizes improved type safety and error handling, while Python developers benefit from better integration with provider-wrapped tools.

**Webhook Security:** A new verification method was introduced. The system now provides secure webhook endpoint validation and signature verification for incoming webhooks, enhancing protection for trigger-based workflows.

**Framework Compatibility:** The stable Tool Router integrates with multiple AI platforms including OpenAI, Anthropic, LangChain, LlamaIndex, CrewAI, and Vercel AI SDK.

### Technical Improvements

The TypeScript SDK resolved significant CommonJS compatibility issues by switching bundlers. This addresses a common developer pain point, particularly for Node.js projects not using ES modules.

The Python SDK extended LangChain provider support to version 1, while simultaneously fixing a critical KeyError occurring when SUPABASE\_BETA\_RUN\_SQL\_QUERY is used with Agents.

### Migration Path

Users upgrading from experimental APIs should note the simplified approach—the Tool Router API now operates directly rather than through experimental namespaces, with comprehensive migration documentation provided.

**Dec 10, 2025**

57 toolkits now return strongly typed objects instead of generic response\_data The label query parameter has been removed from the connected accounts endpoint Sensitive fields now show first 4 characters instead of full REDACTED

## Typed Responses Across Toolkits

We've updated many toolkits so their outputs are now strongly typed objects instead of a generic `response_data` blob, meaning tools like Outlook, HubSpot, Notion, etc. now return well-shaped, documented fields you can rely on directly in your code and agents. These improvements apply to the latest toolkit versions—see our [toolkit versioning docs](https://composio-preview.mintlify.site/docs/tools-direct/toolkit-versioning.md) for how versions are managed.

> [!WARNING]
>
> **Breaking Change for `latest` Version**
>
> If you're using the `latest` version and your code post-processes the old `response_data` structure, you'll need to update your code to work with the new flattened, typed response schemas.

### Why This Matters

* Better developer experience for direct execute: clear fields and types
* Improved agent performance: flatter output shapes with explicit fields reduce nesting and invalid params
* Clearer docs and type safety: richer metadata for IDEs and autocomplete

> [accordion] Impacted Toolkits (57 total)
>
> #### Communication & Collaboration
>
> discordbot, microsoft\_teams, slack, zoom
>
> #### CRM & Sales
>
> apollo, attio, hubspot, instantly, intercom, kommo, salesforce
>
> #### Productivity & Docs
>
> coda, confluence, googledocs, googletasks, notion, todoist
>
> #### Marketing & Social Media
>
> facebook, instagram, klaviyo, linkedin, metaads, reddit, tiktok
>
> #### E-commerce & Payments
>
> brex, quickbooks, ramp, shopify, square, stripe, xero
>
> #### Project Management
>
> clickup, linear
>
> #### Design & Creative
>
> canva, figma
>
> #### Data & Analytics
>
> ahrefs, airtable, apify, exa, pplx, serpapi, tavily
>
> #### Email & Calendar
>
> calendly, outlook
>
> #### Storage & Files
>
> one\_drive
>
> #### Web Tools
>
> firecrawl, fireflies, google\_maps, google\_search\_console
>
> #### AI & Media
>
> elevenlabs, heygen, lmnt, mem0
>
> #### Customer Support
>
> freshdesk, zendesk
>
> #### Video & Content
>
> youtube

### Before vs After

**Previous (generic, version `20251202_00`):**

```json theme={null}
{
  "data": {
    "response_data": { "...": "..." }
  },
  "successful": true
}
```

**Now (typed example – Outlook List Messages, version `20251209_00`):**

```json theme={null}
{
  "data": {
    "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#users('me')/messages",
    "@odata.nextLink": "https://graph.microsoft.com/v1.0/me/messages?$skip=10",
    "value": [
      {
        "id": "abc123",
        "subject": "Hi there",
        "from": { "emailAddress": { "address": "a@b.com", "name": "Alice" } },
        "hasAttachments": true
      }
    ]
  },
  "successful": true
}
```

For the exact field mapping per toolkit, open `dashboard.composio.dev` → Toolkits → List Messages (or the relevant tool).

### Migration Notes

* Breaking change for consumers on the `latest` version who post-process the old nested `response_data` shape: outputs are now flattened and explicitly typed.
* New and modified fields include richer descriptions and examples; some legacy placeholders were removed.
* Re-fetch schemas for your tool/version to see the typed definitions. Use the toolkit view in `dashboard.composio.dev` for authoritative field details.

## Removal of label query parameter from connected accounts API

The `label` query parameter has been removed from the `GET /api/v3/connected_accounts` endpoint.

### What's changing?

The `label` query parameter is no longer supported when listing connected accounts. This parameter was previously accepted but had no functional behavior since label ingestion was removed in an earlier update.

### Impact

**None** - This is a cleanup change. The `label` query parameter was not performing any filtering since the underlying label ingestion functionality was already removed. If your code was passing this parameter, it was being silently ignored.

### Migration

No action required. If your code was passing the `label` query parameter, you can safely remove it from your API calls.

## Enhanced Security Masking for Sensitive Fields

We've improved the security masking for `REDACTED` fields in the following APIs:

* [Get Connected Account](https://composio-preview.mintlify.site/rest-api/connected-accounts/get-connected-accounts-by-nanoid)
* [List Connected Accounts](https://composio-preview.mintlify.site/rest-api/connected-accounts/get-connected-accounts)

**What's Changed:** Sensitive fields are now partially masked, revealing only the **first 4 characters** to help with debugging while maintaining security.

**Example:**

```text theme={null}
Before: REDACTED
After:  abcd...
```

### Disabling Masking

If you need to disable masking for your use case, you have two options:

1. **Via UI:** Navigate to **Project Settings** → **Configuration** tab and update the masking settings
2. **Via API:** Use the Patch Project Config API

**Dec 9, 2025**

Auth0, Blackbaud, BoldSign, Deel, Front, GoToWebinar, and PagerDuty now require your own credentials

## Transition to Self-Managed Credentials for Select Applications

> [!NOTE]
>
> This is a **non-breaking change**. Your existing integrations will continue to work as expected. This change only affects new integrations with the applications listed below.

### What's Changing?

Starting today, the following applications will require **your own developer credentials** instead of Composio-managed credentials:

* **Auth0**
* **Blackbaud**
* **BoldSign**
* **Deel**
* **Front**
* **GoToWebinar**
* **PagerDuty**
* **Pipedrive**
* **Shopify**
* **Strava**
* **SurveyMonkey**
* **Webex**

### What You Need to Do

To continue using these applications with Composio:

1. **Create Developer Accounts**: Register for developer accounts on the platforms you need
2. **Generate API Credentials**: Create OAuth apps following each platform's documentation
3. **Configure in Composio**: Add your credentials to Composio using [custom auth configs](https://composio-preview.mintlify.site/docs/auth-configuration/custom-auth-configs.md)
4. **Test Your Integration**: Test your integration with the new credentials

> [!NOTE]
>
> All other Composio applications continue to work with Composio-managed credentials. This change only affects the 12 applications listed above.

**Dec 3, 2025**

Incomplete connected accounts now auto-expire after 10 minutes

## Connected Account Expiration for Incomplete Connections

We're implementing automatic expiration for connected accounts that remain in incomplete states, helping maintain a cleaner and more efficient authentication system.

### What's Changing?

Connected accounts in `Initializing` and `Initiated` states will now automatically expire after **10 minutes**. This applies to connection attempts that were started but never completed.

### Why This Matters

This change provides:

* **Better Resource Management**: Automatically cleans up incomplete connection attempts
* **Improved System Hygiene**: Prevents accumulation of stale, unused connection records
* **Enhanced User Experience**: Reduces clutter from abandoned authentication flows

> [!NOTE]
>
> This is a **non-breaking change**. Your existing integrations and completed connections will continue to work as expected. This change only affects connection attempts that are never completed.

### Questions?

If you have any questions about this change, please reach out to our support team or check our [Connected Accounts documentation](https://composio-preview.mintlify.site/docs/auth-configuration/connected-accounts.md).

**Nov 13, 2025**

API key authentication becomes mandatory for MCP URLs starting December 15th, 2025

## Required API Key Authentication for MCP URLs

We're strengthening the security of Model Context Protocol (MCP) URLs by making API key authentication mandatory for all requests.

### What's Changing?

Starting **December 15th, 2025**, **all new Composio projects** must include the `x-api-key` header when making requests to MCP URLs. This header authenticates your application and ensures secure communication with the Composio platform.

### Why This Matters

This change provides:

* **Enhanced Authentication**: Ensures only authorized applications can access MCP endpoints
* **Industry Best Practices**: Aligns with standard API security patterns

### Impact on Existing Projects

**For existing projects**: We value backward compatibility and understand the need for a smooth transition. Your existing MCP URLs will continue to work without the `x-api-key` header until **April 15th, 2026**.

**Important**: After April 15th, 2026, all MCP URL requests without the `x-api-key` header will be rejected. Please ensure you update your applications before this date to avoid service disruption.

**Note**: If you're already passing the `x-api-key` header in your MCP requests, no action is required—you're all set!

### Migration Guide

To adopt this security enhancement in your existing projects:

1. **Locate Your API Key**: Find your API key in the Composio dashboard under Project Settings
2. **Update Your Code**: Add the `x-api-key` header to all MCP URL requests
3. **Test Thoroughly**: Verify the updated requests work in your development environment
4. **Deploy**: Roll out the changes to your production environment

### Questions?

If you have any questions about this security enhancement or need assistance with migration, please reach out to our support team or check our MCP documentation.

**Nov 10, 2025**

Trigger operations now support explicit toolkit version specification

## Toolkit Version Support for Triggers

### Summary

Added toolkit version support to trigger operations (`create` and `getType`) in both Python and TypeScript SDKs. This allows users to explicitly specify which toolkit version to use when creating trigger instances and retrieving trigger type information, ensuring consistent behavior across different toolkit versions.

Trigger operations now respect the global `toolkitVersions` configuration set during Composio initialization, providing better control over which trigger versions are used in your applications.

### Key Changes

#### TypeScript SDK (`ts/packages/core/`)

* Added `toolkit_versions` parameter to `triggers.create()` method
  * Passes the global toolkit versions configuration when creating trigger instances
  * Defaults to `'latest'` when no version is specified
* Modified `triggers.getType()` to respect global toolkit versions
  * Now accepts toolkit version configuration to fetch trigger types for specific versions
  * Improved error messages to include version-related fixes
* Updated trigger type documentation with comprehensive examples
* Added behavior documentation explaining version usage patterns

#### Python SDK (`python/composio/core/models/`)

* Added `toolkit_versions` parameter to `triggers.create()` method
  * Uses global toolkit version configuration when creating trigger instances
  * Converts `None` to `omit` for API compatibility
* Modified `triggers.get_type()` to respect toolkit versions
  * Implemented custom method replacing direct client binding
  * Passes toolkit version configuration to API calls
* Added comprehensive docstrings explaining version behavior

### Behavior

**Creating Triggers with Toolkit Versions:**

```typescript theme={null}
// TypeScript - Configure versions at initialization
const composio = new Composio({
  apiKey: 'your-api-key',
  toolkitVersions: {
    gmail: '12082025_00',
    github: '10082025_01'
  }
});

// Create trigger - uses version '12082025_00' for Gmail
const trigger = await composio.triggers.create('user@example.com', 'GMAIL_NEW_MESSAGE', {
  connectedAccountId: 'ca_abc123',
  triggerConfig: {
    labelIds: 'INBOX',
    userId: 'me',
    interval: 60,
  },
});
```

```python theme={null}
# Python - Configure versions at initialization
composio = Composio(
    api_key="your-api-key",
    toolkit_versions={"gmail": "12082025_00", "github": "10082025_01"}
)

# Create trigger - uses version '12082025_00' for Gmail
trigger = composio.triggers.create(
    slug="GMAIL_NEW_MESSAGE",
    user_id="user@example.com",
    trigger_config={"labelIds": "INBOX", "userId": "me", "interval": 60}
)
```

**Retrieving Trigger Types with Specific Versions:**

```typescript theme={null}
// TypeScript
const composio = new Composio({
  apiKey: 'your-api-key',
  toolkitVersions: { github: '10082025_01' }
});

// Get trigger type for specific version
const triggerType = await composio.triggers.getType('GITHUB_COMMIT_EVENT');
// Returns trigger type for version '10082025_01'
```

```python theme={null}
# Python
composio = Composio(
    api_key="your-api-key",
    toolkit_versions={"github": "10082025_01"}
)

# Get trigger type for specific version
trigger_type = composio.triggers.get_type("GITHUB_COMMIT_EVENT")
# Returns trigger type for version '10082025_01'
```

### Benefits

* **Version Control**: Explicitly specify which toolkit version to use for triggers
* **Consistency**: Ensure trigger behavior remains consistent across toolkit updates
* **Testing**: Test trigger integrations with specific versions before updating
* **Debugging**: Easier to debug issues by pinning to specific toolkit versions
* **Production Safety**: Avoid unexpected changes from automatic version updates

### Migration Guide

This is a **non-breaking change**. Existing code will continue to work with default behavior:

**Before (still works):**

```typescript theme={null}
// Uses 'latest' version by default
const trigger = await composio.triggers.create('user', 'GITHUB_COMMIT_EVENT', {...});
```

**After (recommended for production):**

```typescript theme={null}
// Explicitly configure versions for better control
const composio = new Composio({
  apiKey: 'your-api-key',
  toolkitVersions: { github: '10082025_01' }
});

const trigger = await composio.triggers.create('user', 'GITHUB_COMMIT_EVENT', {...});
```

For more details on toolkit versioning, see the [Toolkit Versioning documentation](https://composio-preview.mintlify.site/docs/tools-direct/toolkit-versioning.md).

**Nov 5, 2025**

MCP URLs now require user\_id or connected\_account\_id for better isolation

## Enhanced MCP URL Security Requirements

We're introducing improved security requirements for Model Context Protocol (MCP) URLs to ensure better isolation between user connections and prevent unauthorized access.

### What's Changing?

Starting today, **all new Composio projects** must include at least one of the following parameters in their MCP URLs:

* `user_id` - Identifies the specific user
* `connected_account_id` - Identifies the specific connected account

### Why This Matters

This change ensures that:

* **User Isolation**: Each user's connections remain completely separate from others
* **Enhanced Security**: Prevents potential cross-user data access scenarios
* **Better Multi-Tenancy**: Enables safer multi-tenant application architectures
* **Explicit Access Control**: Forces developers to explicitly specify which user or account context they're operating in

### Impact on Existing Projects

**For existing projects**: We understand the importance of backward compatibility. While we've sent email notifications to project owners about upgrading their MCP URLs, your existing integrations will continue to work until **January 15th, 2026**.

**Important**: After January 15th, 2026, MCP URLs without `user_id` or `connected_account_id` query parameters will no longer be supported. Please ensure you update your MCP URLs before this date to avoid service disruption.

**Note**: If your MCP URLs already include either `user_id` or `connected_account_id` query parameters, no action is required—you can safely ignore this notice.

### Implementation Example

**Before:**

```text theme={null}
https://dashboard.composio.dev/v3/mcp/{id}
```

**After (with user\_id):**

```text theme={null}
https://dashboard.composio.dev/v3/mcp/{id}?user_id=user_123
```

**After (with connected\_account\_id):**

```text theme={null}
https://dashboard.composio.dev/v3/mcp/{id}?connected_account_id=ca_xyz
```

### Migration Guide

If you're using an existing project and want to adopt this security enhancement:

1. Review your current MCP URL configuration
2. Add either `user_id` or `connected_account_id` parameter to your URLs
3. Update your application code to pass the appropriate identifier
4. Test the updated URLs in your development environment

For more details on choosing the right user identifiers for your application, see our [session documentation](https://composio-preview.mintlify.site/docs/how-composio-works.md).

### Questions?

If you have any questions about this security enhancement or need assistance with migration, please reach out to our support team or check our [MCP documentation](#).

**Oct 22, 2025**

Version validation for manual tool execution and performance improvements

## Adds Version Checks for Tool Execution and Improved Execution Speed in TS SDK

### Summary

Added version validation for manual tool execution to prevent unexpected behavior when using `latest` toolkit versions. This ensures users explicitly specify toolkit versions when executing tools manually, while allowing flexibility through a skip flag.

This release also eliminates a lot of redundant API calls made to check connected account during tool execution, effectively increasing the performance of tool execution.

### Key Changes

#### Python SDK (`python/`)

* Added `ToolVersionRequiredError` exception with detailed error messages and fix suggestions
* Added `dangerously_skip_version_check` parameter to `execute()` method
* Modified `_execute_tool()` to validate version is not `latest` unless skip flag is set
* Automatically passes `dangerously_skip_version_check=True` for agentic provider flows
* Added comprehensive test coverage (19 test methods) in `test_tool_execution.py`

#### TypeScript SDK (`ts/packages/core/`)

* Added `ComposioToolVersionRequiredError` error class with possible fixes
* Added `dangerouslySkipVersionCheck` parameter to execute flow
* Modified tool execution to validate version before API calls
* Updated execution type definitions in `tool.types.ts` and `modifiers.types.ts`
* Updated test files with date-based version format (`20251201_xx`)
* Improved tool execution by eliminating redundant API calls

### Behavior

**Before:** Tools could be executed with `latest` version, risking unexpected behavior on toolkit updates

**After:** Manual execution requires specific version or explicit skip flag:

```python theme={null}
# Raises ToolVersionRequiredError
tools.execute("GITHUB_CREATE_ISSUE", {...})

# Works - explicit version
tools.execute("GITHUB_CREATE_ISSUE", {...}, version="20251201_01")

# Works - configured toolkit versions
tools = Tools(client, provider, toolkit_versions={"github": "20251201_01"})

# Works - with skip flag (use cautiously)
tools.execute("GITHUB_CREATE_ISSUE", {...}, dangerously_skip_version_check=True)
```

### Breaking Changes

Manual tool execution without version specification now throws an error. Users must either:

1. Pass explicit version parameter
2. Configure toolkit versions in SDK initialization
3. Set environment variable `COMPOSIO_TOOLKIT_VERSION_<TOOLKIT_SLUG>`
4. Use `dangerously_skip_version_check=True` flag

**Sep 26, 2025**

Comprehensive MCP support and experimental ToolRouter for isolated, scoped sessions

## MCP (Model Control Protocol) & Experimental ToolRouter

Composio now introduces **comprehensive MCP (Model Control Protocol) support** and an **experimental ToolRouter** for creating isolated, scoped sessions with advanced toolkit management. These features enable seamless integration with modern AI frameworks and provide powerful session-based tool routing capabilities.

### Why Use MCP & ToolRouter?

* **Framework Integration**: Native MCP support for Vercel AI, Mastra, OpenAI Agents, and LangChain
* **Session Isolation**: Create isolated sessions with specific toolkit configurations
* **Advanced Authentication**: Flexible auth config management per toolkit
* **Scoped Access**: Control which tools are available within each session
* **Multi-Service Workflows**: Route tool calls efficiently across different services
* **Development & Testing**: Perfect for testing and development with scoped MCP server access

### TypeScript SDK (v0.1.53)

#### **Added: MCP API**

**Core MCP Features:**

* **MCP Server Creation**: Create and manage MCP server configurations
* **User-Specific URLs**: Generate unique MCP server URLs for individual users
* **Toolkit Configuration**: Support for multiple toolkits with custom auth configs
* **Tool Filtering**: Specify allowed tools per configuration
* **Connection Management**: Choose between manual and automatic account management

**Basic Usage:**

```typescript theme={null}
import { Composio } from '@composio/core';

const composio = new Composio({
  apiKey: process.env.COMPOSIO_API_KEY,
});

// Create MCP configuration
const mcpConfig = await composio.mcp.create('my-server-name', {
  toolkits: [
    { toolkit: 'github', authConfigId: 'ac_233434343' },
    { toolkit: 'gmail', authConfigId: 'ac_567890123' }
  ],
  allowedTools: ['GITHUB_CREATE_ISSUE', 'GMAIL_SEND_EMAIL'],
  manuallyManageConnections: false,
});

// Generate server instance for a user
const serverInstance = await composio.mcp.generate('user123', mcpConfig.id);
console.log('MCP URL:', serverInstance.url);
```

**Framework Integration Examples:**

```typescript theme={null}
// Vercel AI Integration
import { SSEClientTransport } from '@modelcontextprotocol/sdk/client/sse.js';
import { experimental_createMCPClient as createMCPClient } from 'ai';

const mcpClient = await createMCPClient({
  name: 'composio-mcp-client',
  transport: new SSEClientTransport(new URL(serverInstance.url)),
});

// Mastra Integration
import { MCPClient as MastraMCPClient } from '@mastra/mcp';

const mcpClient = new MastraMCPClient({
  servers: {
    composio: { url: new URL(mcpSession.url) },
  },
});

// OpenAI Agents Integration
import { hostedMcpTool } from '@openai/agents';

const tools = [
  hostedMcpTool({
    serverLabel: 'composio',
    serverUrl: mcpSession.url,
  }),
];
```

#### **Added: Experimental ToolRouter**

**Core ToolRouter Features:**

* **Session-Based Routing**: Create isolated sessions for specific users and toolkit combinations
* **Dynamic Configuration**: Configure toolkits and auth configs per session
* **MCP Server URLs**: Each session gets a unique MCP server endpoint
* **Flexible Toolkit Management**: Support for string names or detailed toolkit configurations
* **Connection Control**: Manual or automatic connection management per session

**Basic Usage:**

```typescript theme={null}
// Create session with simple toolkit names
const session = await composio.experimental.toolRouter.createSession('user_123', {
  toolkits: ['gmail', 'slack', 'github'],
});

// Create session with auth configs
const session = await composio.experimental.toolRouter.createSession('user_456', {
  toolkits: [
    { toolkit: 'gmail', authConfigId: 'ac_gmail_work' },
    { toolkit: 'slack', authConfigId: 'ac_slack_team' },
    { toolkit: 'github', authConfigId: 'ac_github_personal' },
  ],
  manuallyManageConnections: true,
});

console.log('Session ID:', session.sessionId);
console.log('MCP URL:', session.url);
```

**Advanced Multi-Service Integration:**

```typescript theme={null}
// Complex workflow session
const integrationSession = await composio.experimental.toolRouter.createSession('user_789', {
  toolkits: [
    { toolkit: 'gmail', authConfigId: 'ac_gmail_work' },
    { toolkit: 'slack', authConfigId: 'ac_slack_team' },
    { toolkit: 'github', authConfigId: 'ac_github_personal' },
    { toolkit: 'notion', authConfigId: 'ac_notion_workspace' },
    { toolkit: 'calendar', authConfigId: 'ac_gcal_primary' },
  ],
});

// Use with any MCP client
const mcpClient = new MCPClient(integrationSession.url);
```

**Framework-Specific Examples:**

```typescript theme={null}
// Mastra Integration
const mcpSession = await composio.experimental.toolRouter.createSession(userId, {
  toolkits: ["gmail"],
  manuallyManageConnections: true,
});

const agent = new MastraAgent({
  name: 'Gmail Assistant',
  model: openai('gpt-4o-mini'),
  tools: await mcpClient.getTools(),
});

// OpenAI Agents Integration
const tools = [
  hostedMcpTool({
    serverLabel: 'composio tool router',
    serverUrl: mcpSession.url,
    requireApproval: {
      never: { toolNames: ['GMAIL_FETCH_EMAILS'] },
    },
  }),
];
```

### Python SDK (v0.8.17)

#### **Added: MCP Support**

**Core MCP Features:**

* **Server Configuration**: Create and manage MCP server configurations
* **Toolkit Management**: Support for both simple toolkit names and detailed configurations
* **Authentication Control**: Per-toolkit auth config specification
* **Tool Filtering**: Specify allowed tools across all toolkits
* **User Instance Generation**: Generate user-specific MCP server instances

**Basic Usage:**

```python theme={null}
from composio import Composio

composio = Composio()

# Create MCP server with toolkit configurations
server = composio.mcp.create(
    'personal-mcp-server',
    toolkits=[
        {
            'toolkit': 'github',
            'auth_config_id': 'ac_xyz',
        },
        {
            'toolkit': 'slack',
            'auth_config_id': 'ac_abc',
        },
    ],
    allowed_tools=['GITHUB_CREATE_ISSUE', 'SLACK_SEND_MESSAGE'],
    manually_manage_connections=False
)

# Generate server instance for a user
mcp_instance = server.generate('user_12345')
print(f"MCP URL: {mcp_instance['url']}")
```

**Simple Toolkit Usage:**

```python theme={null}
# Using simple toolkit names
server = composio.mcp.create(
    'simple-mcp-server',
    toolkits=['composio_search', 'text_to_pdf'],
    allowed_tools=['COMPOSIO_SEARCH_DUCK_DUCK_GO_SEARCH', 'TEXT_TO_PDF_CONVERT_TEXT_TO_PDF']
)

# All tools from toolkits (default behavior)
server = composio.mcp.create(
    'all-tools-server',
    toolkits=['composio_search', 'text_to_pdf']
    # allowed_tools=None means all tools from these toolkits
)
```

**LangChain Integration:**

```python theme={null}
import asyncio
from composio import Composio
from langchain_mcp_adapters.client import MultiServerMCPClient
from langgraph.prebuilt import create_react_agent

composio = Composio()

mcp_config = composio.mcp.create(
    name="langchain-slack-mcp",
    toolkits=[{"toolkit": "slack", "auth_config_id": "<auth-config-id>"}],
)

mcp_server = mcp_config.generate(user_id='<user-id>')

client = MultiServerMCPClient({
    "composio": {
        "url": mcp_server["url"],
        "transport": "streamable_http",
    }
})

async def langchain_mcp(message: str):
    tools = await client.get_tools()
    agent = create_react_agent("openai:gpt-4.1", tools)
    response = await agent.ainvoke({"messages": message})
    return response

response = asyncio.run(langchain_mcp("Show me 20 most used slack channels"))
```

#### **Added: Experimental ToolRouter**

**Core ToolRouter Features:**

* **Session Management**: Create isolated tool routing sessions for users
* **Toolkit Configuration**: Support for both simple toolkit names and detailed configurations
* **Session Isolation**: Each session gets its own MCP URL and session ID
* **Flexible Authentication**: Per-session auth config management
* **Scoped Tool Access**: Control which tools are available within each session

**Basic Usage:**

```python theme={null}
from composio import Composio

composio = Composio()

# Create a tool router session
session = composio.experimental.tool_router.create_session(
    user_id='user_123',
    toolkits=['github', 'slack'],
    manually_manage_connections=False
)

print(f"Session ID: {session['session_id']}")
print(f"MCP URL: {session['url']}")
```

**Advanced Configuration:**

```python theme={null}
# Create session with detailed toolkit configurations
session = composio.experimental.tool_router.create_session(
    user_id='user_456',
    toolkits=[
        {
            'toolkit': 'github',
            'auth_config_id': 'ac_github_123'
        },
        {
            'toolkit': 'slack',
            'auth_config_id': 'ac_slack_456'
        }
    ],
    manually_manage_connections=True
)

# Minimal session (no specific toolkits)
session = composio.experimental.tool_router.create_session(
    user_id='user_789'
)
```

**Integration with AI Frameworks:**

```python theme={null}
import asyncio
from composio import Composio
from langchain_mcp_adapters.client import MultiServerMCPClient

composio = Composio()

# Create tool router session
session = composio.experimental.tool_router.create_session(
    user_id='ai_user',
    toolkits=['composio_search', 'text_to_pdf']
)

# Use with LangChain MCP client
client = MultiServerMCPClient({
    "composio": {
        "url": session["url"],
        "transport": "streamable_http",
    }
})

async def use_tool_router():
    tools = await client.get_tools()
    # Use tools in your AI workflow
    return tools

tools = asyncio.run(use_tool_router())
```

### Migration Guide

#### **TypeScript SDK: Migrating to New MCP API**

The new MCP API provides enhanced functionality and better integration patterns. Here's how to migrate from the previous MCP implementation:

##### **Before (Legacy MCP)**

```typescript theme={null}
// Legacy MCP approach (still accessible via deprecated.mcp)
import { Composio } from '@composio/core';

const composio = new Composio();

// Old MCP server creation
const legacyMCP = await composio.deprecated.mcp.createServer({
  name: 'my-server',
  toolkits: ['github', 'gmail'],
});

// Direct URL usage
const mcpUrl = legacyMCP.url;
```

##### **After (New MCP API)**

```typescript theme={null}
// New MCP API approach
import { Composio } from '@composio/core';

const composio = new Composio({
  apiKey: process.env.COMPOSIO_API_KEY,
});

// Step 1: Create MCP configuration
const mcpConfig = await composio.mcp.create('my-server', {
  toolkits: [
    { toolkit: 'github', authConfigId: 'ac_github_123' },
    { toolkit: 'gmail', authConfigId: 'ac_gmail_456' }
  ],
  allowedTools: ['GITHUB_CREATE_ISSUE', 'GMAIL_SEND_EMAIL'],
  manuallyManageConnections: false,
});

// Step 2: Generate user-specific server instance
const serverInstance = await composio.mcp.generate('user_123', mcpConfig.id);
const mcpUrl = serverInstance.url;
```

##### **Key Migration Changes**

1. **Two-Step Process**:
   * **Before**: Single step server creation
   * **After**: Create configuration, then generate user instances
2. **Enhanced Configuration**:
   * **Before**: Simple toolkit names only
   * **After**: Detailed toolkit configs with auth, tool filtering, connection management
3. **User-Specific URLs**:
   * **Before**: Single server URL for all users
   * **After**: Unique URLs per user for better isolation
4. **Backward Compatibility**:
   * **Legacy Access**: Old MCP functionality remains available via `composio.deprecated.mcp`
   * **Gradual Migration**: Migrate at your own pace without breaking existing implementations

##### **Migration Benefits**

* **Better Security**: User-specific sessions with isolated access
* **Enhanced Control**: Fine-grained toolkit and tool management
* **Framework Integration**: Native support for modern AI frameworks
* **Scalability**: Better resource management and user isolation

##### **Migration Timeline**

* **Phase 1**: New MCP API available alongside legacy implementation
* **Phase 2**: Legacy MCP accessible via `deprecated.mcp` namespace
* **Phase 3**: Full deprecation (timeline to be announced)

**Recommendation**: Start new projects with the new MCP API and gradually migrate existing implementations to benefit from enhanced features and better framework integration.

### Key Benefits & Use Cases

#### **Development & Testing**

* **Isolated Environments**: Test different toolkit combinations without affecting production
* **Scoped Access**: Limit tool access for security and testing purposes
* **Framework Flexibility**: Works with any MCP-compatible client or framework

#### **Production Workflows**

* **Multi-Service Integration**: Seamlessly combine tools from different services
* **User-Specific Sessions**: Each user gets their own isolated session with appropriate permissions
* **Authentication Management**: Fine-grained control over authentication per toolkit

#### **Framework Compatibility**

* **Vercel AI**: Native integration with Vercel AI SDK
* **Mastra**: Full support for Mastra agents and workflows
* **OpenAI Agents**: Direct integration with OpenAI's agent framework
* **LangChain**: Complete LangGraph and LangChain compatibility
* **Custom Clients**: Works with any MCP-compatible client

#### **Enterprise Features**

* **Session Management**: Track and manage multiple user sessions
* **Resource Control**: Limit concurrent sessions and resource usage
* **Audit Trail**: Full logging and monitoring of tool usage
* **Security**: Isolated sessions prevent cross-user data access

### Migration & Compatibility

Both MCP and ToolRouter features are designed to complement existing Composio functionality:

```typescript theme={null}
// Can be used alongside regular tool management
const regularTools = await composio.tools.get({ toolkits: ['github'] });
const mcpSession = await composio.experimental.toolRouter.createSession(userId, {
  toolkits: ['gmail', 'slack']
});

// Both approaches can coexist and serve different purposes
```

The experimental ToolRouter API provides a preview of advanced session management capabilities, while the MCP API offers production-ready Model Control Protocol support for modern AI frameworks.

### Bug Fixes

#### **Fixed: ToolRouter Dependency Issue**

**Python SDK (v0.8.19)**

**Issue Fixed:**

* **ToolRouter Functionality**: Fixed ToolRouter tests that were failing due to missing `tool_router` attribute in HttpClient
* **Dependency Update**: Updated `composio-client` dependency from version 1.9.1 to 1.10.0+ to include ToolRouter functionality
* **Version Compatibility**: Resolved compatibility issues between ToolRouter implementation and client library

**Details:** ToolRouter functionality was briefly broken in versions 0.8.15 to 0.8.18 due to a dependency version mismatch. The `composio-client` library version 1.9.1 did not include the `tool_router` attribute, causing all ToolRouter integration tests to fail with `AttributeError: 'HttpClient' object has no attribute 'tool_router'`.

This has been fixed in version 0.8.19 by:

* Updating the `composio-client` dependency to version 1.10.0+
* Ensuring all ToolRouter functionality is now available
* All ToolRouter integration tests now pass successfully

**Previous Issue:**

```python theme={null}
# This would fail in versions 0.8.15-0.8.18
session = composio.experimental.tool_router.create_session(user_id='test')
# AttributeError: 'HttpClient' object has no attribute 'tool_router'
```

**Fixed in 0.8.19:**

```python theme={null}
# This now works correctly
session = composio.experimental.tool_router.create_session(user_id='test')
# Returns: {'session_id': '...', 'url': '...'}
```

#### **Fixed: Missing Descriptions in Auth Config Fields**

**Python SDK (v0.8.17) & TypeScript SDK (v0.1.53)**

**Issue Fixed:**

* **Auth Config Connection Fields**: Added missing descriptions to toolkit auth configuration connection fields
* **Auth Config Creation Fields**: Added missing descriptions to toolkit auth configuration creation fields
* **Field Documentation**: Improved field documentation and help text for better developer experience

**Details:** Previously, when developers were setting up auth configurations for toolkits, many fields lacked proper descriptions, making it difficult to understand what information was required. This fix ensures all auth config fields now include:

* Clear, descriptive field labels
* Helpful placeholder text where appropriate
* Detailed explanations of field requirements

This improvement affects all toolkits and makes the authentication setup process more intuitive and error-free.

**Sep 16, 2025**

Pin specific toolkit versions for consistent behavior and controlled updates in production

## Toolkit Versioning in SDKs

Composio Toolkit Versioning provides **granular control over tool versions** across all your integrations. Instead of always using the latest version of tools, developers can now specify exact toolkit versions, ensuring consistent behavior and controlled updates in production environments.

### Why Use Toolkit Versioning?

* **Version Stability**: Pin specific toolkit versions to avoid unexpected changes in production
* **Controlled Updates**: Test new toolkit versions before deploying to production
* **Environment Consistency**: Ensure the same toolkit versions across development, staging, and production
* **Rollback Capability**: Easily revert to previous toolkit versions if issues arise
* **Fine-grained Control**: Set different versions for different toolkits based on your needs

***

### Python SDK (v0.8.11)

**Added**

* **Toolkit Versioning Support**: New `toolkit_versions` parameter for controlling tool versions
  * Added `toolkit_versions` parameter to `Composio` class initialization
  * Support for global version setting (e.g., `'latest'`)
  * Support for per-toolkit version mapping (e.g., `{'github': '20250902_00', 'slack': '20250902_00'}`)
  * Environment variable support with `COMPOSIO_TOOLKIT_VERSION_<TOOLKIT_NAME>` pattern
  * New `toolkit_version.py` utility module for version resolution logic

**Examples:**

```python theme={null}
# Global version for all toolkits, only `latest` is supported
composio = Composio(toolkit_versions='latest')

# Per-toolkit version mapping
composio = Composio(toolkit_versions={
    'github': '20250902_00',
    'slack': '20250902_00',
    'gmail': '20250901_01'
})

# Using environment variables
# Set COMPOSIO_TOOLKIT_VERSION_GITHUB=20250902_00
composio = Composio()  # Automatically picks up env vars

# Get tools with specific versions
tools = composio.tools.get('default', {'toolkits': ['github']})
```

### TypeScript SDK (v0.1.52)

**Added**

* **Toolkit Versioning Support**: Added `toolkitVersions` configuration option
  * New `toolkitVersions` parameter in `Composio` class constructor
  * Support for global version string or per-toolkit version mapping
  * Environment variable parsing with `getToolkitVersionsFromEnv()` utility
  * Enhanced `getRawComposioToolBySlug()` method for version-specific tool retrieval
  * Version-aware tool filtering and search capabilities

**Examples:**

```typescript theme={null}
// Global version for all toolkits
const composio = new Composio({
  toolkitVersions: '20250902_00'
});

// Per-toolkit version mapping
const composio = new Composio({
  toolkitVersions: {
    'github': '20250902_00',
    'slack': '20250902_00',
    'gmail': '20250901_01'
  }
});

// Using environment variables
// Set COMPOSIO_TOOLKIT_VERSION_GITHUB=20250902_00
const composio = new Composio(); // Automatically picks up env vars

// Get specific tool version
const tool = await composio.tools.getRawComposioToolBySlug(
  'GITHUB_GET_REPO',
);

// Get tools with version-aware filtering
const tools = await composio.tools.get('default', {
  toolkits: ['github'],
  limit: 10
});
```

### Key Benefits

* **Environment Variables**: Set `COMPOSIO_TOOLKIT_VERSION_<TOOLKIT_NAME>=<VERSION>` for automatic version resolution
* **Flexible Configuration**: Choose between global versions or per-toolkit version mapping
* **Backward Compatibility**: Existing code works unchanged - versioning is opt-in
* **Version Fallback**: Automatically falls back to 'latest' when no version is specified
* **Cross-Platform Consistency**: Identical developer experience across Python and TypeScript

### Version Format

Toolkit versions follow the format: `YYYYMMDD_NN` (e.g., `20250902_00`) or use `'latest'` for the most recent version only supported at global scope and not individual toolkit level.

### Environment Variables

```bash theme={null}
# Set specific versions for different toolkits
export COMPOSIO_TOOLKIT_VERSION_GITHUB=20250902_00
export COMPOSIO_TOOLKIT_VERSION_SLACK=20250902_00
export COMPOSIO_TOOLKIT_VERSION_GMAIL=20250901_01
```

### Migration Note

This feature is fully backward compatible. Existing code will continue to work without changes, using the latest versions by default. To enable versioning, simply add the `toolkit_versions` parameter during SDK initialization.

***

### Additional Updates

* **Package Updates**: Bumped all Python provider packages to v0.8.10
* **Documentation**: Enhanced API documentation with versioning examples
* **Testing**: Added comprehensive test coverage (400+ new test cases) for versioning functionality
* **Examples**: New versioning examples demonstrating practical usage patterns

**Sep 15, 2025**

Hosted authentication solution that eliminates the need for custom auth forms

## Introducing Composio Auth Links

Composio Auth Links provide a **hosted authentication solution** that eliminates the need for developers to build custom authentication forms. Instead of manually rendering OAuth consent screens, API key input forms, or custom authentication fields, developers can simply redirect users to a Composio-hosted URL that handles the entire authentication process automatically.

### Why Use Auth Links?

* **Zero UI Development**: No need to build forms for OAuth, API keys, or custom fields like subdomains
* **Universal Authentication**: Works seamlessly across all supported third-party services
* **Reduced Complexity**: Replace complex OAuth flows with a simple redirect
* **Better UX**: Professional, consistent authentication experience for end users
* **Faster Integration**: Get authentication working in minutes, not hours

***

### Python SDK (v0.8.11)

**Added**

* **Composio Connect Link Support**: New `link()` method for creating external authentication links
  * Added `link()` method to `ConnectedAccounts` class for generating user authentication links
  * Support for callback URL redirection after authentication
  * Enhanced user experience with external link-based authentication flow
  * **No manual form rendering required** - Composio handles all authentication UI

**Examples:**

```python theme={null}
# Basic usage - create a connection request
connection_request = composio.connected_accounts.link('user_123', 'auth_config_123')
redirect_url = connection_request.redirect_url
print(f"Visit: {redirect_url} to authenticate your account")

# Wait for the connection to be established
connected_account = connection_request.wait_for_connection()

# With callback URL
connection_request = composio.connected_accounts.link(
    'user_123',
    'auth_config_123',
    callback_url='<https://your-app.com/callback>'
)
```

### TypeScript SDK (v0.1.51)

**Added**

* **Composio Connect Links**: Added support for composio connect links
  * New `link()` method in `ConnectedAccounts` class for generating authentication URLs
  * Support for callback URL redirection with `CreateConnectedAccountLinkOptions`
  * Comprehensive TypeScript types and validation for link creation options
  * **Eliminates need for custom authentication forms** - just redirect users to the link

**Examples:**

```tsx theme={null}
// Basic usage - create a connection request
const connectionRequest = await composio.connectedAccounts.link('user_123', 'auth_config_123');
const redirectUrl = connectionRequest.redirectUrl;
console.log(`Visit: ${redirectUrl} to authenticate your account`);

// Wait for the connection to be established
const connectedAccount = await connectionRequest.waitForConnection();

// With callback URL
const connectionRequest = await composio.connectedAccounts.link('user_123', 'auth_config_123', {
  callbackUrl: '<https://your-app.com/callback>'
});
```

### Key Benefits

* **No Form Building**: Composio handles OAuth consent, API key collection, and custom field inputs
* **Hosted Authentication Flow**: Professional UI that works across all supported services
* **Callback URL Support**: Control where users return after successful authentication
* **Connection Waiting**: Built-in polling to detect when authentication completes
* **Cross-Platform Consistency**: Identical developer experience across Python and TypeScript

### Customisation

You can customise the app logo and name showed in the authentication page via the dashboard. Head over your project via `dashboard.composio.dev`  and choose Settings → Auth Links to upload a new logo and change the name.

### Migration Note

This feature replaces manual authentication form development with a simple redirect-based approach, significantly reducing integration time and complexity while providing a better user experience. Auth links are drop in replacement for `composio.connectedAccounts.initate`, you can safely swap this to `composio.connectedAccounts.link`
