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 retrieve multiple Service records. It supports fetching either all available services or a limited number based on user-defined constraints. The node allows users to specify which fields to include in the output, map fields for custom processing, and optionally add human-readable labels for picklist and reference fields. It also supports flattening user-defined fields for easier access. This is useful for automating service data retrieval in IT service management workflows, such as generating reports, syncing service data with other systems, or triggering actions based on service attributes.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Service resource to map and include in the output. Supports custom mapping and auto-mapping of fields. |
| Get All | Determines whether to return all Service records or limit the number of records returned. |
| Max Records | Specifies the maximum number of Service records to return when 'Get All' is false. Valid range is 1 to 500. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields. |
| Select Columns Names or IDs. | Allows selection of specific 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 moved to the top level of each Service object instead of being nested. |
Output
JSON
serviceRecords- An array of Service objects retrieved from Autotask, each containing the selected fields and optionally added labels and flattened user-defined fields.
Dependencies
- Requires an Autotask API 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 'service'.
- If no records are returned, check the 'Get All' and 'Max Records' settings to ensure they allow fetching the desired number of records.
- Errors related to field mapping may occur if the specified fields do not exist or are misspelled; verify field names in the 'Fields' property.
- Authentication errors indicate issues with the Autotask API credentials; ensure the API key or token is valid and has sufficient permissions.
- If picklist or reference labels are missing, confirm that 'Add Picklist Labels' and 'Add Reference Labels' options are enabled and that the fields have non-empty values.