CallPage MCP integration for AI agents.
Connect AI agents to CallPage through 7 structured actions, including get call, create widget call, and get user. Review authentication, inputs, workflows, a…
- ACTION CONTRACTS
- 7
- 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 CallPage integration exposes
The CallPage Agent App exposes 7 provider-backed actions for communication and productivity work. Its current contract lets an authorized agent get one callpage call by identifier, create a callpage callback request for one widget and phone number, and get one callpage user by identifier or email address. 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 CallPage account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real CallPage capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_callREADGet one CallPage call by identifier.
INPUTS: call_id
create_widget_callWRITECreate a CallPage callback request for one widget and phone number.
INPUTS: widget_id / tel / department_id / manager_id
get_userREADGet one CallPage user by identifier or email address.
INPUTS: id / email
get_widgetREADGet one CallPage widget by identifier.
INPUTS: widget_id
list_callsREADList CallPage calls with optional filters such as widget, user, status, phone number, and time range.
INPUTS: display_hidden / call_ids / phone_number / user_ids / statuses
list_usersREADList CallPage users with pagination.
INPUTS: offset / limit
list_widgetsREADList CallPage widgets with pagination.
INPUTS: offset / limit
INPUT CONTRACTS
Know what the action needs before it runs.
get_call
call_idOPTIONAL- The CallPage call identifier.
create_widget_call
widget_idREQUIRED- The CallPage widget identifier.
telREQUIRED- The phone number to call in E.164 format.
department_idOPTIONAL- The CallPage department identifier.
manager_idOPTIONAL- The CallPage manager identifier.
get_user
idOPTIONAL- The CallPage user identifier.
emailOPTIONAL- The CallPage user email address.
get_widget
widget_idOPTIONAL- The CallPage widget identifier.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Call
Get one CallPage call by identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_callControl Create Widget Call
Create a CallPage callback request for one widget and phone number. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_widget_callVerify with Get User
Get one CallPage user by identifier or email address. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_userSAFETY BOUNDARY
Operate CallPage with explicit limits
- Authorize CallPage 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.
- The sampled contract declares provider scopes including `widgets.call`, `calls.view`, and `widgets.view`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the CallPage task completed successfully.
CONNECTION MODEL
API key
CallPage API token sent with the Authorization header. Generate or view it in the CallPage dashboard API settings: https://core.callpage.io/settings/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
- 6
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- 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 CallPage.