V2NodesAutotask
Autotask
V2

Autotask

Autotask is a professional services automation platform used to manage companies, tickets, projects, contracts, and related service data.

The Flowgear Autotask Node lets you query, create, update, and delete supported Autotask records through its REST API.

Revision History

0.0.0.17 - Preserved inherited fields in designer templates when OpenAPI schemas use constraints-only allOf overlays.
0.0.0.10 - Initial release.
0.0.0.13 - Automatically populate Connection Base URL.
0.0.0.16 - Move Base URL discovery to metadata acquisition.

Connection

The Connection stores the Autotask REST endpoint and authentication headers used by all methods.

Property Type Description
Base URL String The Autotask API base URL. Click Acquire Metadata to populate this from Autotask zone information.
API Integration Code Masked The Autotask API integration code sent in the ApiIntegrationCode header.
Username String The Autotask username sent in the UserName header.
Secret Masked The Autotask secret sent in the Secret header.
Impersonation Resource ID String An optional impersonation resource identifier sent in the ImpersonationResourceId header.
Timeout (seconds) Integer The timeout used for Autotask API validation and runtime calls.

Setup Notes

  • Enter the Autotask credentials supplied for your tenant in Username and Secret.
  • Enter your Autotask integration code in API Integration Code. If you do not have one, leave it blank and the Node will default to Flowgear's integration code.
  • Click Acquire Metadata to populate Base URL from Autotask zone information. Provide Base URL manually only when your tenant requires a different Autotask host.
  • Make sure Base URL is a valid HTTP/S address and does not include leading or trailing spaces.
  • Use Impersonation Resource ID only when your Autotask setup requires impersonation.
  • Set Timeout (seconds) to a value greater than zero.
  • You can generate and expand templates without live credentials because the Node uses an embedded Swagger document for template discovery.
  • Runtime API calls still require a valid Autotask Connection.

Methods

This Node exposes template-driven Query, Create, Update, and Delete methods for supported Autotask REST operations.

Query

Use Query for supported GET operations and for read-style POST .../query operations.

Parameter Type Description
Connection Connection The Autotask Connection profile.
OperationId String The template-selected identifier for the operation to run.
Options Object The route and query values required by the selected operation.
Items Array An optional request body for POST .../query operations, e.g. query properties such as filter, includeFields, and maxRecords when the selected template requires them.
Return Type Description
Response Array The results returned by the selected operation. Autotask items envelopes are unwrapped so the Node emits one response item per business record.

Create

Use Create for supported POST operations that create Autotask records.

Parameter Type Description
Connection Connection The Autotask Connection profile.
OperationId String The template-selected identifier for the operation to run.
Options Object The route and query values required by the selected operation.
Items Array An optional request body for the selected create operation.
Return Type Description
Response Array The results returned by the selected operation. Single-item and scalar create envelopes are normalized into response items.

Update

Use Update for supported PUT and PATCH operations that update Autotask records.

Parameter Type Description
Connection Connection The Autotask Connection profile.
OperationId String The template-selected identifier for the operation to run.
Options Object The route and query values required by the selected operation.
Items Array An optional request body for the selected update operation.
Return Type Description
Response Array The results returned by the selected operation. Single-item and scalar update envelopes are normalized into response items.

Delete

Use Delete for supported DELETE operations.

Parameter Type Description
Connection Connection The Autotask Connection profile.
OperationId String The template-selected identifier for the operation to run.
Options Object The route and query values required by the selected operation.
Return Type Description
Response Array The results returned by the selected operation. Empty successful responses are still normalized into a response item.

Usage Notes

  • Templates populate OperationId and the expected Options values for the selected operation.
  • Query paging is handled internally when Autotask returns pageDetails.nextPageUrl, so you do not manage paging URLs in your Workflow.
  • Autotask item, items, and itemId response envelopes are unwrapped so the Response output contains the business record or result value.
  • Authentication headers come from the Connection, not from the request template.

Known Issues

  • Attachment and other file-style routes are not exposed because this version supports JSON request and response flows only.
  • Metadata helper routes such as /entityInformation* and count helper routes such as /query/count are intentionally not exposed in this version.