Altoviz MCP integration for AI agents.
Connect AI agents to Altoviz through 4 structured actions, including find customers, create customer, and get customer. Review authentication, inputs, workfl…
- ACTION CONTRACTS
- 4
- 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 Altoviz integration exposes
The Altoviz Agent App exposes 4 provider-backed actions for finance and productivity work. Its current contract lets an authorized agent find altoviz customers by email, external-system id, or customer number, create a business, consumer, or government customer in altoviz, and retrieve one altoviz customer by its numeric customer 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 Altoviz account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Altoviz capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
find_customersREADFind Altoviz customers by email, external-system ID, or customer number.
INPUTS: email / internalId / number
create_customerWRITECreate a business, consumer, or government customer in Altoviz.
INPUTS: active / type / companyName / firstName / lastName
get_customerREADRetrieve one Altoviz customer by its numeric customer ID.
INPUTS: customerId
list_customersREADList Altoviz customers with full-text search, ordering, and stable pagination metadata.
INPUTS: pageIndex / pageSize / orderBy / query
INPUT CONTRACTS
Know what the action needs before it runs.
find_customers
emailOPTIONAL- The exact customer email to find.
internalIdOPTIONAL- The customer identifier from an external system.
numberOPTIONAL- The Altoviz customer number to find.
create_customer
activeOPTIONAL- Whether the customer is active.
typeOPTIONAL- The customer type.
companyNameOPTIONALfirstNameOPTIONALlastNameOPTIONAL
get_customer
customerIdOPTIONAL- The numeric Altoviz customer ID.
list_customers
pageIndexOPTIONAL- The one-based page index.
pageSizeOPTIONAL- The number of customers per page.
orderByOPTIONAL- The Altoviz customer field ordering expression.
queryOPTIONAL- A full-text customer search query.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Find Customers
Find Altoviz customers by email, external-system ID, or customer number. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
find_customersControl Create Customer
Create a business, consumer, or government customer in Altoviz. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_customerVerify with Get Customer
Retrieve one Altoviz customer by its numeric customer 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 Altoviz with explicit limits
- Authorize Altoviz 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 Altoviz rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Altoviz task completed successfully.
CONNECTION MODEL
API key
Altoviz API key sent with the x-api-key header. Create or regenerate it in Altoviz Settings under API access: https://app.altoviz.com/go/settings/apis.
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
- 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 Altoviz.