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
The node interacts with the Autotask REST API to retrieve multiple Skill records. It supports fetching either all available skills or a limited number, with options to customize the fields returned and enhance the data with human-readable labels for picklist and reference fields. This is useful for workflows that need to process or analyze skill data from Autotask, such as reporting, synchronization with other systems, or automation based on skill attributes.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Skill resource to retrieve and map in the output. Supports custom mapping and auto-mapping of fields. |
| Get All | Determines whether to return all Skill records or limit the number of records returned. |
| Max Records | Specifies the maximum number of Skill records to return when 'Get All' is false. Range is 1 to 500. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields in the Skill data. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields in the Skill data. |
| Select Columns Names or IDs. | Allows selection of specific Skill fields to include in the response. If none selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are promoted to top-level properties in each Skill object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the Skill record.
- Standard or user-defined fields of the Skill resource as specified by the Fields property._label - Human-readable labels for picklist or reference fields if Add Picklist Labels or Add Reference Labels is enabled.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the node returns an error about unsupported resource, verify that the Resource parameter is set to 'Skill'.
- If no records are returned, check the 'Get All' and 'Max Records' settings to ensure they match the expected data volume.
- Errors related to authentication usually indicate missing or invalid API credentials; verify the Autotask API key is correctly configured.
- If custom fields do not appear, ensure that the Fields property mapping includes those user-defined fields and that 'Flatten User-Defined Fields' is enabled if top-level access is desired.