Help Scout MCP integration for AI agents.
Connect AI agents to Help Scout through 24 structured actions, including get conversation, assign conversation, and replace conversation custom fields. Revie…
- ACTION CONTRACTS
- 24
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Help Scout integration exposes
The Help Scout Agent App exposes 24 provider-backed actions for communication and productivity work. Its current contract lets an authorized agent get one help scout conversation by id, assign a help scout conversation to a user or leave it unassigned, and replace the complete custom field state of a help scout conversation. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. 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 Help Scout account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Help Scout capabilities.
Showing 12 of 24 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_conversationREADGet one Help Scout conversation by ID.
INPUTS: conversationId / embedThreads
assign_conversationWRITEAssign a Help Scout conversation to a user or leave it unassigned.
INPUTS: conversationId / assignedUserId
replace_conversation_custom_fieldsREVIEWReplace the complete custom field state of a Help Scout conversation.
INPUTS: conversationId / customFields
create_conversationWRITECreate a Help Scout conversation with one initial text thread.
INPUTS: subject / inboxId / customerId / customerEmail / customerFirstName
create_customerWRITECreate a Help Scout customer with a primary email address.
INPUTS: email / emailType / firstName / lastName / phone
create_noteWRITEAdd an internal note to a Help Scout conversation.
INPUTS: conversationId / text / userId
create_replyWRITEAdd a published reply or draft reply to a Help Scout conversation.
INPUTS: conversationId / customerId / text / draft / userId
get_customerREADGet one Help Scout customer by ID.
INPUTS: customerId
get_saved_replyREADGet the complete email and chat content of a Help Scout saved reply.
INPUTS: inboxId / savedReplyId
list_conversationsREADList and filter conversations in the connected Help Scout account.
INPUTS: page / inboxIds / folderId / status / tagNames
list_customersREADList and filter customers in the connected Help Scout account.
INPUTS: page / inboxId / firstName / lastName / email
list_inbox_custom_fieldsREADList the custom field definitions and dropdown options for a Help Scout inbox.
INPUTS: inboxId
INPUT CONTRACTS
Know what the action needs before it runs.
get_conversation
conversationIdREQUIRED- The Help Scout conversation ID.
embedThreadsOPTIONAL- Whether to embed thread previews in the conversation.
assign_conversation
conversationIdOPTIONAL- The Help Scout conversation ID.
assignedUserIdOPTIONAL
replace_conversation_custom_fields
conversationIdOPTIONAL- The Help Scout conversation ID.
customFieldsOPTIONAL- The complete set of custom fields to apply; omitted existing fields are removed.
create_conversation
subjectREQUIRED- The conversation subject.
inboxIdREQUIRED- The Help Scout inbox where the conversation is created.
customerIdOPTIONAL- The existing Help Scout customer ID.
customerEmailOPTIONAL- The customer email address used to find or create the customer.
customerFirstNameOPTIONAL- The first name used when a new customer is created.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Conversation
Get one Help Scout conversation 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_conversationControl Assign Conversation
Assign a Help Scout conversation to a user or leave it unassigned. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
assign_conversationVerify with Get Customer
Get one Help Scout customer by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_customerSAFETY BOUNDARY
Operate Help Scout with explicit limits
- Authorize Help Scout with OAuth 2.0 and grant only the provider access required by the selected actions.
- 6 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.
- The sampled contract declares provider scopes including `helpscout.inbox.write` and `helpscout.inbox.read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Help Scout task completed successfully.
CONNECTION MODEL
OAuth 2.0
Help Scout uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
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
- 14
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 4
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 Help Scout.