Amilia MCP integration for AI agents.
Connect AI agents to Amilia through 4 structured actions, including get activity, get program, and list program activities. Review authentication, inputs, wo…
- 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 Amilia integration exposes
The Amilia Agent App exposes 4 provider-backed actions for productivity work. Its current contract lets an authorized agent retrieve one activity from the connected amilia organization, retrieve one program from the connected amilia organization, and list activities in one amilia program with visibility, cancellation, occurrence, tax, and pagination options. 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 Amilia account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Amilia capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_activityREADRetrieve one activity from the connected Amilia organization.
INPUTS: activityId / showTaxes
get_programREADRetrieve one program from the connected Amilia organization.
INPUTS: programId
list_program_activitiesREADList activities in one Amilia program with visibility, cancellation, occurrence, tax, and pagination options.
INPUTS: programId / showHidden / showCancelled / showOccurrences / showTaxes
list_programsREADList programs for the connected Amilia organization with visibility, archive, and pagination filters.
INPUTS: showHidden / showArchived / page / perPage
INPUT CONTRACTS
Know what the action needs before it runs.
get_activity
activityIdREQUIRED- The Amilia activity identifier.
showTaxesOPTIONAL- Whether activity tax details should be included.
get_program
programIdREQUIRED- The Amilia program identifier.
list_program_activities
programIdREQUIRED- The Amilia program identifier.
showHiddenOPTIONAL- Whether hidden activities should be included.
showCancelledOPTIONAL- Whether cancelled activities should be included.
showOccurrencesOPTIONAL- Whether each activity should include its full occurrence list.
showTaxesOPTIONAL- Whether activity tax details should be included.
list_programs
showHiddenOPTIONAL- Whether hidden programs should be included.
showArchivedOPTIONAL- Whether archived programs should be included.
pageOPTIONAL- The Amilia result page number to request.
perPageOPTIONAL- The number of Amilia records to request per page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Activity
Retrieve one activity from the connected Amilia organization. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_activityVerify with Get Program
Retrieve one program from the connected Amilia organization. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_programSAFETY BOUNDARY
Operate Amilia with explicit limits
- Authorize Amilia with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Amilia 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 Amilia rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Amilia task completed successfully.
CONNECTION MODEL
API key
One-year Amilia JWT sent as a Bearer token. Obtain it by calling POST https://app.amilia.com/api/V3/authenticate with Basic authentication for a dedicated Amilia API user: https://app.amilia.com/apidocs/Index.html#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
- 4
- 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 Amilia.