ChartMogul MCP integration for AI agents.
Connect AI agents to ChartMogul through 5 structured actions, including get account, get customer, and list contacts. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 5
- 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 ChartMogul integration exposes
The ChartMogul Agent App exposes 5 provider-backed actions for finance and data work. Its current contract lets an authorized agent retrieve basic chartmogul account settings for the authenticated api key, retrieve a single chartmogul customer by customer uuid, and list chartmogul contacts with cursor pagination and common contact filters. 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 ChartMogul account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ChartMogul capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADRetrieve basic ChartMogul account settings for the authenticated API key.
INPUTS: include
get_customerREADRetrieve a single ChartMogul customer by customer UUID.
INPUTS: customerUuid
list_contactsREADList ChartMogul contacts with cursor pagination and common contact filters.
INPUTS: email / customerExternalId / customerUuid / dataSourceUuid / cursor
list_customersREADList ChartMogul customers with cursor pagination and common customer filters.
INPUTS: dataSourceUuid / externalId / email / withAssociatedEmails / status
list_sourcesREADList ChartMogul data sources with optional source name or billing system filters.
INPUTS: name / system
INPUT CONTRACTS
Know what the action needs before it runs.
get_account
includeOPTIONAL- Additional account settings to include in the response.
get_customer
customerUuidOPTIONAL- The ChartMogul UUID of the customer.
list_contacts
emailOPTIONAL- The contact email address to filter by.
customerExternalIdOPTIONAL- The customer external identifier whose contacts should be returned.
customerUuidOPTIONAL- The ChartMogul UUID of the customer.
dataSourceUuidOPTIONAL- The source UUID whose contacts should be returned.
cursorOPTIONAL- The cursor returned by ChartMogul for fetching the next page.
list_customers
dataSourceUuidOPTIONAL- The ChartMogul source UUID used to filter customers.
externalIdOPTIONAL- The external customer identifier to filter by.
emailOPTIONAL- The customer email address to search for.
withAssociatedEmailsOPTIONAL- Whether email search should also match associated contact email addresses.
statusOPTIONAL- The lead or subscription status to filter by.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Retrieve basic ChartMogul account settings for the authenticated API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountVerify with Get Customer
Retrieve a single ChartMogul customer by customer UUID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_customerSAFETY BOUNDARY
Operate ChartMogul with explicit limits
- Authorize ChartMogul with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned ChartMogul 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 ChartMogul rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ChartMogul task completed successfully.
CONNECTION MODEL
API key
ChartMogul API key used as the HTTP Basic Auth username with an empty password. Create or view API keys from Profile > View Profile > API Keys: https://help.chartmogul.com/article/95-creating-and-managing-api-keys.
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
- 5
- 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 ChartMogul.