Actions389
- Contract Actions
- Ticket History Actions
- Ticket Note Webhook Actions
- Ticket Note Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Role Actions
- Resource Role Actions
- Search Filter Actions
- Service Actions
- Skill Actions
- Service Call Actions
- Survey Results Actions
- Survey Actions
- Ticket Actions
- Opportunity Actions
- Notification History Actions
- Invoice Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Phase Actions
- Project Task Actions
- Project Note Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Service Bundle Adjustment Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code Actions
- Contract Rate Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Role Costs Actions
- Contact Groups Actions
- Contact Actions
- Contact Webhook Actions
- Contact Group Contacts Actions
- Contract Block Hour Factor Actions
- Contract Block Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Company Alert Actions
- Company Actions
- Billing Code Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Overview
This node interacts with the Autotask REST API to perform operations on the 'Resource' entity, specifically supporting the 'Get' operation. It allows users to retrieve detailed information about a specific resource by its ID. The node supports additional options to customize the output, such as including human-readable labels for picklist and reference fields, selecting specific columns to return, and flattening user-defined fields for easier access. This is useful in scenarios where you need to fetch and process resource data from Autotask within an automation workflow, for example, to integrate resource details into reports or trigger actions based on resource attributes.
Properties
| Name | Meaning |
|---|---|
| Resource ID | The unique identifier of the resource to retrieve. This is required to specify which resource's data to fetch. |
| Add Picklist Labels | Whether to automatically add '_label' fields for picklist fields, providing human-readable values alongside the raw data. No labels are added for empty values. |
| Add Reference Labels | Whether to automatically add '_label' fields for reference fields, providing human-readable values alongside the raw data. No labels are added for empty values. |
| Select Columns Names or IDs. | Allows choosing specific fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | When enabled, user-defined fields (UDFs) are brought up to the top level of each object instead of being nested inside a 'userDefinedFields' array, simplifying access to these fields. |
Output
JSON
id- The unique identifier of the resource.fields*- Various fields of the resource as returned by the Autotask API, including standard and user-defined fields.
_label - Human-readable labels for picklist or reference fields, if enabled.userDefinedFields- Array of user-defined fields associated with the resource, unless flattened.
Dependencies
- Requires an Autotask API credential (API key or token) configured in n8n to authenticate requests to the Autotask REST API.
Troubleshooting
- If the node throws an error indicating the resource ID is missing or invalid, ensure that the 'Resource ID' property is correctly set and corresponds to an existing resource in Autotask.
- Errors related to authentication usually mean the Autotask API credentials are missing, expired, or incorrect. Verify and update the credentials in n8n.
- If the response does not include expected fields, check the 'Select Columns' property to ensure the desired fields are selected or leave it empty to retrieve all fields.
- When enabling 'Add Picklist Labels' or 'Add Reference Labels', if labels are missing, it may be due to empty or null values in those fields for the resource.
- Flattening user-defined fields may cause naming conflicts if UDF names overlap with standard fields; disable flattening if unexpected data structure issues occur.