AroFlo MCP integration for AI agents.
Connect AI agents to AroFlo through 7 structured actions, including get client, get health status, and get task. Review authentication, inputs, workflows, an…
- 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 AroFlo integration exposes
The AroFlo Agent App exposes 7 provider-backed actions for productivity work. Its current contract lets an authorized agent retrieve a specific aroflo client by encoded client id, retrieve the public health status for the aroflo api, and retrieve a specific aroflo task by encoded task 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 AroFlo account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real AroFlo capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_clientREADRetrieve a specific AroFlo client by encoded client ID.
INPUTS: clientId / fields
get_health_statusREADRetrieve the public health status for the AroFlo API.
get_taskREADRetrieve a specific AroFlo task by encoded task ID.
INPUTS: taskId / fields
get_userREADRetrieve a specific AroFlo user by encoded user ID.
INPUTS: userId / fields
list_clientsREADList AroFlo clients with optional partial-name filtering and field selection.
INPUTS: name / fields
list_tasksREADList AroFlo tasks with business unit, status, resource, date, and pagination filters.
INPUTS: businessUnitId / status / assignedFilterUserId / scheduledFilterUserId / contractorId
list_usersREADList AroFlo users for an organisation with optional filters.
INPUTS: orgId / givenName / surname / billingPortalAccess / assignedUsersOnly
INPUT CONTRACTS
Know what the action needs before it runs.
get_client
clientIdREQUIRED- An AroFlo encoded identifier.
fieldsOPTIONAL- Comma-separated top-level AroFlo fields to include. Sub-entity fields can use bracket notation.
get_task
taskIdREQUIRED- An AroFlo encoded identifier.
fieldsOPTIONAL- Comma-separated top-level AroFlo fields to include. Sub-entity fields can use bracket notation.
get_user
userIdREQUIRED- An AroFlo encoded identifier.
fieldsOPTIONAL- Comma-separated top-level AroFlo fields to include. Sub-entity fields can use bracket notation.
list_clients
nameOPTIONAL- Filter clients by partial name.
fieldsOPTIONAL- Comma-separated top-level AroFlo fields to include. Sub-entity fields can use bracket notation.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Client
Retrieve a specific AroFlo client by encoded client ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_clientVerify with Get Health Status
Retrieve the public health status for the AroFlo API. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_health_statusSAFETY BOUNDARY
Operate AroFlo with explicit limits
- Authorize AroFlo with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned AroFlo data may still be sensitive and should be minimized before it enters model context.
- 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 AroFlo rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the AroFlo task completed successfully.
CONNECTION MODEL
API key
AroFlo API token sent as a Bearer credential. Generate it from Site Admin > AroFlo API: https://docs.api.aroflo.com/guides/authentication/.
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
- 0
- 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 AroFlo.