Elorus MCP integration for AI agents.
Connect AI agents to Elorus through 12 structured actions, including get contact, create contact, and create invoice. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 12
- 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 Elorus integration exposes
The Elorus Agent App exposes 12 provider-backed actions for finance and productivity work. Its current contract lets an authorized agent get one elorus contact by id, create one elorus contact in the selected organization, and create one elorus invoice in the selected organization. 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 Elorus account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Elorus capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_contactREADGet one Elorus contact by ID.
INPUTS: id
create_contactWRITECreate one Elorus contact in the selected organization.
INPUTS: data
create_invoiceWRITECreate one Elorus invoice in the selected organization.
INPUTS: data
create_productWRITECreate one Elorus product or service in the selected organization.
INPUTS: data
get_invoiceREADGet one Elorus invoice by ID.
INPUTS: id
get_productREADGet one Elorus product or service by ID.
INPUTS: id
list_contactsREADList Elorus contacts with optional search, filters, and pagination.
INPUTS: ordering / search / search_fields / custom_id / created_after
list_invoicesREADList Elorus invoices with optional filters and pagination.
INPUTS: ordering / search / search_fields / custom_id / created_after
list_productsREADList Elorus products or services with optional filters and pagination.
INPUTS: ordering / search / search_fields / custom_id / created_after
update_contactWRITEUpdate one Elorus contact by ID.
INPUTS: id / data
update_invoiceWRITEUpdate one Elorus invoice by ID using the official full-update endpoint.
INPUTS: id / data
update_productWRITEUpdate one Elorus product or service by ID.
INPUTS: id / data
INPUT CONTRACTS
Know what the action needs before it runs.
get_contact
idREQUIRED- The Elorus object identifier.
create_contact
dataREQUIRED- A raw Elorus object payload.
create_invoice
dataREQUIRED- A raw Elorus object payload.
create_product
dataREQUIRED- A raw Elorus object payload.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Contact
Get one Elorus contact 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_contactControl Create Contact
Create one Elorus contact in the selected organization. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Get Invoice
Get one Elorus invoice by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_invoiceSAFETY BOUNDARY
Operate Elorus with explicit limits
- Authorize Elorus with API key and grant only the provider access required by the selected actions.
- 6 actions are 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 Elorus rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Elorus task completed successfully.
CONNECTION MODEL
API key
Elorus API key sent as Authorization: Token <token>. Find it in the Elorus web application under User Profile.
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
- 6
- WRITE SIGNALS
- 6
- 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 Elorus.