Autotask MCP integration for AI agents.
Connect AI agents to Autotask through 4 structured actions, including get entity information, get record, and get zone information. Review authentication, in…
- 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 Autotask integration exposes
The Autotask Agent App exposes 4 provider-backed actions for productivity and data work. Its current contract lets an authorized agent get autotask entityinformation metadata for companies, contacts, or tickets, get one autotask company, contact, or ticket by numeric id, and return the autotask rest api zone url for the connected api user. 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 Autotask account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Autotask capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_entity_informationREADGet Autotask entityInformation metadata for Companies, Contacts, or Tickets.
INPUTS: entity / section
get_recordREADGet one Autotask Company, Contact, or Ticket by numeric ID.
INPUTS: entity / id
get_zone_informationREADReturn the Autotask REST API zone URL for the connected API user.
query_recordsREADQuery Autotask Companies, Contacts, or Tickets with optional filter, IncludeFields, and MaxRecords parameters.
INPUTS: entity / filter / includeFields / maxRecords
INPUT CONTRACTS
Know what the action needs before it runs.
get_entity_information
entityREQUIRED- Autotask entity to query.
sectionOPTIONAL- Autotask entityInformation section to retrieve.
get_record
entityOPTIONAL- Autotask entity to query.
idOPTIONAL- Numeric Autotask record ID.
query_records
entityREQUIRED- Autotask entity to query.
filterOPTIONAL- Autotask filter expressions.
includeFieldsOPTIONAL- Autotask field names to include in the response.
maxRecordsOPTIONAL- Maximum records to return. Autotask allows 1 to 500 per page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Entity Information
Get Autotask entityInformation metadata for Companies, Contacts, or Tickets. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_entity_informationVerify with Get Record
Get one Autotask Company, Contact, or Ticket by numeric ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_recordSAFETY BOUNDARY
Operate Autotask with explicit limits
- Authorize Autotask with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Autotask 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 Autotask rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Autotask task completed successfully.
CONNECTION MODEL
API key
Autotask API-only user name sent with the Username header. Create an API user and tracking identifier in Autotask security settings as described in the official REST authentication docs: https://www.autotask.net/help/developerhelp/Content/APIs/REST/General_Topics/REST_Security_Auth.htm
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 Autotask.