SupportBee MCP integration for AI agents.
Connect AI agents to SupportBee through 17 structured actions, including get ticket, add label to ticket, and remove label from ticket. Review authentication…
- ACTION CONTRACTS
- 17
- 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 SupportBee integration exposes
The SupportBee Agent App exposes 17 provider-backed actions for communication and productivity work. Its current contract lets an authorized agent retrieve a supportbee ticket by id, add an existing supportbee label to a ticket, and remove a supportbee label from a ticket. 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 SupportBee account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real SupportBee capabilities.
Showing 12 of 17 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_ticketREADRetrieve a SupportBee ticket by ID.
INPUTS: id
add_label_to_ticketWRITEAdd an existing SupportBee label to a ticket.
INPUTS: ticket_id / label_name
remove_label_from_ticketHIGH IMPACTRemove a SupportBee label from a ticket.
INPUTS: ticket_id / label_name
create_ticketWRITECreate a SupportBee ticket with JSON body content and optional email recipients.
INPUTS: subject / requester_name / requester_email / cc / bcc
create_ticket_commentWRITECreate a SupportBee ticket comment with JSON body content.
INPUTS: ticket_id / text / html
create_ticket_replyWRITECreate a SupportBee ticket reply with JSON body content.
INPUTS: ticket_id / text / html / cc / bcc
create_userWRITECreate a SupportBee user or customer group.
INPUTS: email / name / role / team_ids / type
get_ticket_replyREADRetrieve one SupportBee ticket reply by ticket ID and reply ID.
INPUTS: ticket_id / reply_id
get_userREADRetrieve one SupportBee user or customer group by ID.
INPUTS: id / max_tickets
list_labelsREADList custom SupportBee labels for the connected desk.
list_teamsREADList SupportBee teams with optional user expansion filters.
INPUTS: with_users / user
list_ticket_commentsREADList comments for a SupportBee ticket.
INPUTS: ticket_id
INPUT CONTRACTS
Know what the action needs before it runs.
get_ticket
idREQUIRED- A positive SupportBee numeric identifier.
add_label_to_ticket
ticket_idREQUIRED- A positive SupportBee numeric identifier.
label_nameREQUIRED- The existing SupportBee label name to add.
remove_label_from_ticket
ticket_idREQUIRED- A positive SupportBee numeric identifier.
label_nameREQUIRED- The SupportBee label name to remove.
create_ticket
subjectOPTIONAL- The subject of the ticket.
requester_nameOPTIONAL- The name of the ticket requester.
requester_emailOPTIONAL- The email address of the ticket requester.
ccOPTIONAL- Email addresses sent to SupportBee.
bccOPTIONAL- Email addresses sent to SupportBee.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Ticket
Retrieve a SupportBee ticket 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_ticketControl Add Label To Ticket
Add an existing SupportBee label to a ticket. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_label_to_ticketVerify with Get Ticket Reply
Retrieve one SupportBee ticket reply by ticket ID and reply ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_ticket_replySAFETY BOUNDARY
Operate SupportBee with explicit limits
- Authorize SupportBee with API key and grant only the provider access required by the selected actions.
- 7 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `remove_label_from_ticket` 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 SupportBee rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the SupportBee task completed successfully.
CONNECTION MODEL
API key
SupportBee API token sent as an Authorization Bearer token. Find it from your SupportBee desk by clicking your profile picture and then API Token: https://supportbee.com/docs/api/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
- 10
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 1
- 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 SupportBee.