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 operation retrieves multiple Holiday Set records from the Autotask system. It is useful for scenarios where users need to fetch a list of holiday sets, for example, to synchronize holiday data, generate reports, or automate scheduling processes based on company holidays. The operation supports fetching all records or limiting the number of records returned, and allows customization of the fields included in the output.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Holiday Set resource to retrieve and map in the output. Supports defining fields explicitly and auto-mapping capabilities. |
| Get All | Boolean flag to determine whether to return all Holiday Set records or limit the results. |
| Max Records | Specifies the maximum number of Holiday Set records to return when 'Get All' is false. The value must be between 1 and 500. |
| Add Picklist Labels | Determines whether to add human-readable label fields for picklist fields in the output. Labels are added as additional fields with a '_label' suffix. |
| Add Reference Labels | Determines whether to add human-readable label fields for reference fields in the output. Labels are added as additional fields with a '_label' suffix. |
| Select Columns Names or IDs. | Allows selection of specific fields (columns) to include in the response. If no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are brought to the top level of each returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the Holiday Set record.name- Name of the Holiday Set.description- Description of the Holiday Set.userDefinedFields- Array of user-defined fields associated with the Holiday Set, unless flattened.
_label - Human-readable labels for picklist or reference fields, added if enabled.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the Holiday Sets exist in the Autotask system and that the API credentials have sufficient permissions.
- If the node returns an error about unsupported resource, ensure the resource parameter is set to 'holidaySet'.
- When selecting specific fields, ensure the field names or IDs are valid; invalid fields may cause errors or missing data.
- If the node times out or returns partial data, consider enabling 'Get All' to fetch all records or increasing the max records limit within allowed bounds.
- If user-defined fields are not appearing as expected, check the 'Flatten User-Defined Fields' option to control their structure.