Holded MCP integration for AI agents.
Connect AI agents to Holded through 5 structured actions, including get contact, create contact, and get product. Review authentication, inputs, workflows, a…
- 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 Holded integration exposes
The Holded Agent App exposes 5 provider-backed actions for finance and productivity work. Its current contract lets an authorized agent get a holded contact by identifier, create a basic holded contact with json-friendly identity fields, and get a holded product by identifier. 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 Holded account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Holded capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_contactREADGet a Holded contact by identifier.
INPUTS: contactId
create_contactWRITECreate a basic Holded contact with JSON-friendly identity fields.
INPUTS: name / email / phone / mobile / code
get_productREADGet a Holded product by identifier.
INPUTS: productId
list_contactsREADList Holded contacts with exact-match filters and cursor pagination.
INPUTS: phone / mobile / email / code / customId
list_productsREADList Holded products with cursor pagination.
INPUTS: cursor / limit
INPUT CONTRACTS
Know what the action needs before it runs.
get_contact
contactIdREQUIRED- Holded object identifier.
create_contact
nameREQUIRED- The contact name.
emailOPTIONAL- The contact email address.
phoneOPTIONAL- The contact phone number.
mobileOPTIONAL- The contact mobile number.
codeOPTIONAL- The contact tax identification code.
get_product
productIdREQUIRED- Holded object identifier.
list_contacts
phoneOPTIONAL- Filter contacts by exact phone number.
mobileOPTIONAL- Filter contacts by exact mobile number.
emailOPTIONAL- Filter contacts by exact email address.
codeOPTIONAL- Filter contacts by exact tax identification code.
customIdOPTIONAL- Filter contacts by exact external custom identifier.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Contact
Get a Holded contact 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_contactControl Create Contact
Create a basic Holded contact with JSON-friendly identity fields. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Get Product
Get a Holded product by identifier. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_productSAFETY BOUNDARY
Operate Holded with explicit limits
- Authorize Holded 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 Holded rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Holded task completed successfully.
CONNECTION MODEL
API key
Holded API token used as a Bearer token.
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
- 4
- 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 Holded.