Botsonic MCP integration for AI agents.
Connect AI agents to Botsonic through 4 structured actions, including get conversation, generate response, and list conversations. Review authentication, inp…
- ACTION CONTRACTS
- 4
- 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 Botsonic integration exposes
The Botsonic Agent App exposes 4 provider-backed actions for ai and communication work. Its current contract lets an authorized agent get one botsonic conversation by chat identifier, generate one synchronous response from the connected botsonic bot, and list conversations for the connected botsonic bot token. 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 Botsonic account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Botsonic capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_conversationREADGet one Botsonic conversation by chat identifier.
INPUTS: chat_id
generate_responseREVIEWGenerate one synchronous response from the connected Botsonic bot.
INPUTS: input_text / chat_id / source / starter_question_id / user_unique_identifier
list_conversationsREADList conversations for the connected Botsonic bot token.
INPUTS: search_query / sort_by / sort_order / updated_after / updated_before
list_faqsREADList FAQs attached to the connected Botsonic bot token.
INPUTS: search_query / sort_by / sort_order / page / size
INPUT CONTRACTS
Know what the action needs before it runs.
get_conversation
chat_idOPTIONAL- The Botsonic conversation chat identifier.
generate_response
input_textREQUIRED- User question for the bot.
chat_idREQUIRED- The Botsonic chat identifier for this conversation.
sourceOPTIONAL- Optional source value for Botsonic to refer to.
starter_question_idOPTIONAL- Optional Botsonic starter question identifier.
user_unique_identifierOPTIONAL- Optional unique user identifier stored by Botsonic in the inbox.
list_conversations
search_queryOPTIONAL- Search query used to match Botsonic conversations.
sort_byOPTIONAL- The conversation sorting mode.
sort_orderOPTIONAL- The conversation sorting order.
updated_afterOPTIONAL- Filter conversations updated after this ISO 8601 timestamp.
updated_beforeOPTIONAL- Filter conversations updated before this ISO 8601 timestamp.
list_faqs
search_queryOPTIONAL- Search query used to match Botsonic FAQs.
sort_byOPTIONAL- The FAQ attribute to sort by.
sort_orderOPTIONAL- The FAQ sorting order.
pageOPTIONAL- The page number to request from Botsonic.
sizeOPTIONAL- The number of FAQs to request from Botsonic.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Conversation
Get one Botsonic conversation by chat identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_conversationVerify with List Conversations
List conversations for the connected Botsonic bot token. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_conversationsSAFETY BOUNDARY
Operate Botsonic with explicit limits
- Authorize Botsonic with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Botsonic data may still be sensitive and should be minimized before it enters model context.
- 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 Botsonic rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Botsonic task completed successfully.
CONNECTION MODEL
API key
Botsonic bot API token sent with the X-BOT-KEY header. Open your Botsonic dashboard, select a bot, then copy the token from Integration Page > REST API as described at https://docs.botsonic.com/docs/rest-api.
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
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
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 Botsonic.