ChatBotKit MCP integration for AI agents.
Connect AI agents to ChatBotKit through 27 structured actions, including download file, create bot, and attach dataset file. Review authentication, inputs, w…
- ACTION CONTRACTS
- 27
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the ChatBotKit integration exposes
The ChatBotKit Agent App exposes 27 provider-backed actions for ai and developer tools work. Its current contract lets an authorized agent fetch the download url for an existing chatbotkit file, create a new chatbotkit bot, and attach an existing chatbotkit file to a dataset. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected ChatBotKit account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ChatBotKit capabilities.
Showing 12 of 27 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
download_fileREADFetch the download URL for an existing ChatBotKit file.
INPUTS: fileId
create_botWRITECreate a new ChatBotKit bot.
attach_dataset_fileREVIEWAttach an existing ChatBotKit file to a dataset.
INPUTS: datasetId / fileId / type
complete_conversationREVIEWSend a message to a ChatBotKit conversation and receive the next assistant reply.
INPUTS: conversationId
create_conversationWRITECreate a new ChatBotKit conversation.
create_conversation_messageWRITEAppend a message to an existing ChatBotKit conversation.
INPUTS: conversationId
create_datasetWRITECreate a new ChatBotKit dataset for knowledge retrieval.
create_dataset_recordWRITECreate a new record inside a ChatBotKit dataset.
INPUTS: datasetId
create_fileWRITECreate a new ChatBotKit file resource.
detach_dataset_fileREVIEWDetach a ChatBotKit file from a dataset.
INPUTS: datasetId / fileId / deleteRecords
fetch_botREVIEWFetch a single ChatBotKit bot by ID.
INPUTS: botId
fetch_conversationREVIEWFetch a single ChatBotKit conversation by ID.
INPUTS: conversationId
INPUT CONTRACTS
Know what the action needs before it runs.
download_file
fileIdREQUIRED- The unique identifier of the resource.
attach_dataset_file
datasetIdREQUIRED- The unique identifier of the resource.
fileIdREQUIRED- The unique identifier of the resource.
typeREQUIRED- The attachment type.
complete_conversation
conversationIdOPTIONAL- The unique identifier of the resource.
create_conversation_message
conversationIdOPTIONAL- The unique identifier of the resource.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Download File
Fetch the download URL for an existing ChatBotKit file. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
download_fileControl Create Bot
Create a new ChatBotKit bot. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_botVerify with Create Bot
Create a new ChatBotKit bot. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_botSAFETY BOUNDARY
Operate ChatBotKit with explicit limits
- Authorize ChatBotKit with API key and grant only the provider access required by the selected actions.
- 9 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in ChatBotKit rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ChatBotKit task completed successfully.
CONNECTION MODEL
API key
ChatBotKit API key used with the Authorization Bearer header. Generate it from your ChatBotKit account tokens page: https://chatbotkit.com/tokens.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 9
- WRITE SIGNALS
- 9
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 9
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by ChatBotKit.