Helcim MCP integration for AI agents.
Connect AI agents to Helcim through 4 structured actions, including get customer, create customer, and list customers. Review authentication, inputs, workflo…
- 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 Helcim integration exposes
The Helcim Agent App exposes 4 provider-backed actions for finance and productivity work. Its current contract lets an authorized agent retrieve one helcim customer by id, create a helcim customer using a contact name, business name, or both, and list or search helcim customers with page-based pagination. 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 Helcim account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Helcim capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_customerREADRetrieve one Helcim customer by ID.
INPUTS: customerId
create_customerWRITECreate a Helcim customer using a contact name, business name, or both.
INPUTS: customerCode / contactName / businessName / cellPhone / billingAddress
list_customersREADList or search Helcim customers with page-based pagination.
INPUTS: search / customerCode / limit / page / includeCards
update_customerWRITEUpdate an existing Helcim customer.
INPUTS: customerId / customerCode / contactName / businessName / cellPhone
INPUT CONTRACTS
Know what the action needs before it runs.
get_customer
customerIdOPTIONAL- The Helcim customer ID.
create_customer
customerCodeOPTIONAL- The unique customer code, or omit it to let Helcim generate one.
contactNameOPTIONAL- The customer's primary contact name.
businessNameOPTIONAL- The customer's business name.
cellPhoneOPTIONAL- The customer's cell phone number.
billingAddressOPTIONAL- A billing or shipping address for a Helcim customer.
list_customers
searchOPTIONAL- A partial match across customer names, code, city, phone, or email.
customerCodeOPTIONAL- An exact customer code filter.
limitOPTIONAL- The maximum number of customers to return, up to 100.
pageOPTIONAL- The one-based result page to return.
includeCardsOPTIONAL- Whether to include stored card metadata for each customer.
update_customer
customerIdREQUIRED- The Helcim customer ID.
customerCodeOPTIONAL- The unique customer code, or omit it to let Helcim generate one.
contactNameOPTIONAL- The customer's primary contact name.
businessNameOPTIONAL- The customer's business name.
cellPhoneOPTIONAL- The customer's cell phone number.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Customer
Retrieve one Helcim customer 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_customerControl Create Customer
Create a Helcim customer using a contact name, business name, or both. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_customerVerify with List Customers
List or search Helcim customers with page-based pagination. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_customersSAFETY BOUNDARY
Operate Helcim with explicit limits
- Authorize Helcim with API key and grant only the provider access required by the selected actions.
- 2 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 Helcim rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Helcim task completed successfully.
CONNECTION MODEL
API key
Helcim API token sent in the api-token header. Create one under All Tools > Integrations > API Access Configurations: https://devdocs.helcim.com/docs/authentication-with-the-helcim-api-and-helcimpayjs
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
- 2
- WRITE SIGNALS
- 2
- 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 Helcim.