Provides integration with Autotask using the REST API.
0.0.0.10 - Initial release.
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. The default value matches the embedded Swagger document. |
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. |
- 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.
- Leave
Base URL at the default value unless your tenant requires a different Autotask host.
- Make sure
Base URL is a valid http or https 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.
This Node exposes template-driven Query, Create, Update, and Delete methods for supported Autotask REST operations.
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. |
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. |
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. |
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. |
- Templates populate
OperationId and the expected Options values for the selected operation.
- The Node adds the standard Flowgear response fields
status, statusMessage, and errorMessage to every emitted response item.
- Query paging is handled internally when Autotask returns
pageDetails.nextPageUrl, so you do not manage paging URLs in your Workflow.
- Authentication headers come from the
Connection, not from the request template.
- 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.