BotStar MCP integration for AI agents.
Connect AI agents to BotStar through 21 structured actions, including get bot, create bot, and delete bot attribute. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 21
- 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 BotStar integration exposes
The BotStar Agent App exposes 21 provider-backed actions for communication and marketing work. Its current contract lets an authorized agent get one botstar bot by id, create a new botstar bot, and delete a botstar bot attribute. 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 BotStar account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BotStar capabilities.
Showing 12 of 21 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_botREADGet one BotStar bot by ID.
INPUTS: botId
create_botWRITECreate a new BotStar bot.
INPUTS: name
delete_bot_attributeHIGH IMPACTDelete a BotStar bot attribute.
INPUTS: botId / attributeId / env
create_bot_attributeWRITECreate an attribute on a BotStar bot.
INPUTS: botId / env / name / data_type / desc
create_cms_entityWRITECreate a BotStar CMS entity.
INPUTS: botId / env / name / fields
create_cms_entity_itemWRITECreate an item in a BotStar CMS entity.
INPUTS: botId / entityId / env / name / status
create_user_attributeWRITECreate a custom user attribute field for a BotStar bot.
INPUTS: botId / field_name / field_type
delete_cms_entityHIGH IMPACTDelete a BotStar CMS entity.
INPUTS: botId / entityId / env
delete_cms_entity_itemHIGH IMPACTDelete an item from a BotStar CMS entity.
INPUTS: botId / entityId / entityItemId / env
get_cms_entityREADGet one BotStar CMS entity by ID.
INPUTS: botId / entityId / env
get_cms_entity_itemREADGet one item from a BotStar CMS entity.
INPUTS: botId / entityId / entityItemId / env
get_userREADGet a BotStar audience user by bot ID and user ID.
INPUTS: botId / userId
INPUT CONTRACTS
Know what the action needs before it runs.
get_bot
botIdREQUIRED- The BotStar bot ID.
create_bot
nameREQUIRED- The new bot name.
delete_bot_attribute
botIdREQUIRED- The BotStar bot ID.
attributeIdREQUIRED- The BotStar bot attribute ID.
envOPTIONAL- The BotStar environment target for mutation endpoints.
create_bot_attribute
botIdREQUIRED- The BotStar bot ID.
envOPTIONAL- The BotStar environment target for mutation endpoints.
nameREQUIRED- The bot attribute name.
data_typeREQUIRED- The bot attribute data type.
descOPTIONAL- The bot attribute description.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Bot
Get one BotStar bot by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_botControl Create Bot
Create a new BotStar 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 BotStar 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 BotStar with explicit limits
- Authorize BotStar with API key and grant only the provider access required by the selected actions.
- 13 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_bot_attribute`, `delete_cms_entity`, and `delete_cms_entity_item` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in BotStar rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BotStar task completed successfully.
CONNECTION MODEL
API key
BotStar API token sent as a Bearer token. Copy it from the BotStar account profile page: https://app.botstar.com/account/profile.
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
- 8
- WRITE SIGNALS
- 9
- HIGH IMPACT
- 4
- REVIEW SIGNALS
- 0
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 BotStar.