Paymo MCP integration for AI agents.
Connect AI agents to Paymo through 16 structured actions, including get client, create client, and delete client. Review authentication, inputs, workflows, a…
- ACTION CONTRACTS
- 16
- 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 Paymo integration exposes
The Paymo Agent App exposes 16 provider-backed actions for productivity and finance work. Its current contract lets an authorized agent get one paymo client by id, create one paymo client from a json client payload, and delete one paymo client by id. 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 Paymo account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Paymo capabilities.
Showing 12 of 16 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_clientREADGet one Paymo client by ID.
INPUTS: id / include / partial_include
create_clientWRITECreate one Paymo client from a JSON client payload.
INPUTS: data
delete_clientHIGH IMPACTDelete one Paymo client by ID.
INPUTS: id
create_projectWRITECreate one Paymo project from a JSON project payload.
INPUTS: data
create_taskWRITECreate one Paymo task from a JSON task payload.
INPUTS: data
delete_projectHIGH IMPACTDelete one Paymo project by ID.
INPUTS: id
delete_taskHIGH IMPACTDelete one Paymo task by ID.
INPUTS: id
get_current_userREADGet the Paymo user associated with the current API key.
get_projectREADGet one Paymo project by ID.
INPUTS: id / include / partial_include
get_taskREADGet one Paymo task by ID.
INPUTS: id / include / partial_include
list_clientsREADList Paymo clients with optional where and include query parameters.
INPUTS: where / include / partial_include
list_projectsREADList Paymo projects with optional where and include query parameters.
INPUTS: where / include / partial_include
INPUT CONTRACTS
Know what the action needs before it runs.
get_client
idREQUIRED- The Paymo numeric resource identifier.
includeOPTIONAL- The Paymo include expression for adding related content to the response.
partial_includeOPTIONAL- The Paymo partial_include expression for adding lightweight related content.
create_client
dataOPTIONAL- The Paymo client fields to create or update, such as name, email, phone, website, or address fields.
delete_client
idOPTIONAL- The Paymo numeric resource identifier.
create_project
dataOPTIONAL- The Paymo project fields to create or update, such as name, client_id, description, or workflow_id.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Client
Get one Paymo client 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_clientControl Create Client
Create one Paymo client from a JSON client payload. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_clientVerify with Get Current User
Get the Paymo user associated with the current API key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_current_userSAFETY BOUNDARY
Operate Paymo with explicit limits
- Authorize Paymo with API key and grant only the provider access required by the selected actions.
- 9 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_client`, `delete_project`, and `delete_task` 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 Paymo rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Paymo task completed successfully.
CONNECTION MODEL
API key
Paymo API key used as the Basic Auth username. Generate it from Paymo My Account: https://app.paymoapp.com/#Paymo.module.myaccount/
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
- 7
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 3
- 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 Paymo.