2Chat MCP integration for AI agents.
Connect AI agents to 2Chat through 5 structured actions, including get api usage info, create contact, and test api key. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 5
- 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 2Chat integration exposes
The 2Chat Agent App exposes 5 provider-backed actions for communication and developer tools work. Its current contract lets an authorized agent fetch the current 2chat account, rate limit, and usage counters for the connected api key, create a contact in 2chat with one or more contact details and optional channel and profile picture metadata, and validate the connected 2chat api key and return normalized account, limit, and usage information. 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 2Chat account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real 2Chat capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_api_usage_infoREADFetch the current 2Chat account, rate limit, and usage counters for the connected API key.
create_contactWRITECreate a contact in 2Chat with one or more contact details and optional channel and profile picture metadata.
INPUTS: firstName / lastName / channelUuid / profilePicUrl / contactDetails
test_api_keyREVIEWValidate the connected 2Chat API key and return normalized account, limit, and usage information.
list_contactsREADList contacts from the connected 2Chat account, with optional pagination and channel filtering.
INPUTS: pageNumber / resultsPerPage / channelUuid
list_webhooksREADList the webhook subscriptions currently configured in the connected 2Chat account.
INPUT CONTRACTS
Know what the action needs before it runs.
create_contact
firstNameREQUIRED- The first name of the contact to create.
lastNameOPTIONAL- Optional last name of the contact to create.
channelUuidOPTIONAL- Optional channel UUID to associate with the created contact.
profilePicUrlOPTIONAL- Optional public profile picture URL for the contact.
contactDetailsREQUIRED- The contact details to create with the new contact.
list_contacts
pageNumberOPTIONAL- Optional page number to retrieve.
resultsPerPageOPTIONAL- Optional page size to request from 2Chat, from 1 to 100.
channelUuidOPTIONAL- Optional connected number UUID used to filter contacts by channel.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Api Usage Info
Fetch the current 2Chat account, rate limit, and usage counters for the connected API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_api_usage_infoControl Create Contact
Create a contact in 2Chat with one or more contact details and optional channel and profile picture metadata. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with List Contacts
List contacts from the connected 2Chat account, with optional pagination and channel filtering. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_contactsSAFETY BOUNDARY
Operate 2Chat with explicit limits
- Authorize 2Chat with API key and grant only the provider access required by the selected actions.
- 1 action is 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 2Chat rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the 2Chat task completed successfully.
CONNECTION MODEL
API key
2Chat API key sent with the X-User-API-Key header. Create or view it from the API Access tab in the 2Chat dashboard: https://app.2chat.io/developers?tab=api-access.
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
- 1
- 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 2Chat.