Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Twilio Flex (BYOK) — connector documentation

  • MCP endpoint: https://byok-twilio-flex.connectorbay.com/mcp
  • REST API: POST https://byok-twilio-flex.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-twilio-flex.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Twilio Flex Account SID or API key SID (use a restricted API key, SID starts with SK, rather than the main Auth Token where possible), sent in the X-Upstream-Key header and the Auth Token, or the secret of the API key in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-twilio-flex.connectorbay.com/health · Tool schemas: https://byok-twilio-flex.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-twilio-flex · agent@connectorbay.com

What Twilio Flex (BYOK) is for

Twilio Flex (BYOK) lets an AI assistant read your own Twilio Flex data through the Twilio Flex API with a key you supply (Account SID or API key SID (use a restricted API key, SID starts with SK, rather than the main Auth Token where possible)). Read-only: 11 tools (get_flex_configuration, get_provisioning_status, list_flex_flows, get_flex_flow, list_web_channels, list_plugins, get_plugin, list_plugin_versions, list_plugin_configurations, list_configured_plugins, list_plugin_releases). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to flex-api.twilio.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Twilio Flex. Twilio Flex and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "What are my Twilio Flex instance settings?"
  • "Is my Twilio Flex account provisioned?"
  • "Which Flex flows do I have and are they enabled?"
  • "Is flex flow FO... enabled?"
  • "Which Flex web chat channels exist?"
  • "Which Flex plugins are registered?"

What it does

  • get_flex_configuration: Show the Flex instance settings: status, TaskRouter workspace, runtime domain, UI version, language, recording and CRM switches and plugin service flag.
  • get_provisioning_status: Show whether the Flex account is provisioned (status is active, in-progress, not-configured or failed).
  • list_flex_flows: List Flex Flows, which route incoming chat, SMS and messaging channels into Flex, with channel type, integration type and enabled flag.
  • get_flex_flow: Get one Flex Flow: channel type, integration type, whether it is enabled and long lived, and its chat service.
  • list_web_channels: List web chat channels created in Flex with the flow each belongs to and creation date.
  • list_plugins: List Flex plugins registered in the Plugins Service with unique name, description and archived flag.
  • get_plugin: Get one Flex plugin by SID or unique name.
  • list_plugin_versions: List the versions of one Flex plugin with version number, bundle URL, changelog, privacy and validated flags.
  • list_plugin_configurations: List Flex plugin configurations (named sets of plugin versions) with description and archived flag.
  • list_configured_plugins: List the plugins and versions that belong to one Flex plugin configuration, with their phase (required or optional).
  • list_plugin_releases: List Flex plugin releases (which configuration is live).

BYOK key

You bring your own Twilio Flex Account SID or API key SID (use a restricted API key, SID starts with SK, rather than the main Auth Token where possible) (https://www.twilio.com/docs/iam/api-keys/keys-in-console). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to flex-api.twilio.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Twilio Flex API (flex-api.twilio.com) with a BYOK key; documentation: https://www.twilio.com/docs/flex/developer/config-api. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Twilio Flex. Twilio Flex and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Twilio Flex account.

Built for: Worldwide. Languages: English.