Autom MCP integration for AI agents.
Connect AI agents to Autom through 4 structured actions, including find google countries, find google languages, and find google locations. Review authentica…
- 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 Autom integration exposes
The Autom Agent App exposes 4 provider-backed actions for data, developer tools, and marketing work. Its current contract lets an authorized agent search supported google countries in autom and return matching country codes, search supported google languages in autom and return matching language codes, and search supported google locations in autom and return matching location ids. 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 Autom account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Autom capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
find_google_countriesREADSearch supported Google countries in Autom and return matching country codes.
INPUTS: query
find_google_languagesREADSearch supported Google languages in Autom and return matching language codes.
INPUTS: query
find_google_locationsREADSearch supported Google locations in Autom and return matching location IDs.
INPUTS: query
get_usageREADGet current Autom credit usage, subscription quota, rate limits, account metadata, and API key metadata.
INPUT CONTRACTS
Know what the action needs before it runs.
find_google_countries
queryREQUIRED- Search text used to filter Autom finder results.
find_google_languages
queryREQUIRED- Search text used to filter Autom finder results.
find_google_locations
queryREQUIRED- Search text used to filter Autom finder results.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Find Google Countries
Search supported Google countries in Autom and return matching country codes. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
find_google_countriesVerify with Find Google Languages
Search supported Google languages in Autom and return matching language codes. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
find_google_languagesSAFETY BOUNDARY
Operate Autom with explicit limits
- Authorize Autom with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Autom 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 Autom rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Autom task completed successfully.
CONNECTION MODEL
API key
Autom API key sent with the x-api-key header. Create or copy it from the Autom dashboard API Keys page: https://app.autom.dev/
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 Autom.