Actions524
- AI Helper Actions
- Tool Actions
- API Threshold Actions
- Appointment Actions
- Billing Code Actions
- Billing Items Actions
- Change Request Link Actions
- Checklist Library Actions
- Checklist Library Item Actions
- Classification Icon Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Company Site Configuration Actions
- Configuration Item Actions
- Configuration Item Billing Product Association 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
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Contract Exclusion Billing Code 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 Rate Actions
- Contract Role Costs Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Department Actions
- Project Phase Actions
- Quote Item Actions
- Quote Location Actions
- Quote Template Actions
- Resource Actions
- Resource Role Actions
- Resource Role Queue Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Subscription Actions
- Subscription Period Actions
- Ticket Category Actions
- Ticket Category Field Default Actions
- Ticket History Actions
- Ticket Note Actions
Service → Get Many
AI-generatedOverview
This node operation retrieves multiple records of the 'Service' resource from the Kaseya Autotask PSA REST API. It supports fetching either all available service records or a limited number based on user input. This operation is useful for scenarios where users need to list or analyze multiple service entries, such as generating reports, syncing data, or bulk processing service information.
Use Case Examples
- Fetch all service records to synchronize with an external system.
- Retrieve a limited number of service records for display in a dashboard or report.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all service records or only up to a specified limit. |
| Max Records | Maximum number of service records to return when 'Get All' is false. The value ranges from 1 to 500. |
| Add Picklist Labels | Whether to automatically add '_label' fields for picklist fields with human-readable values in the service records. |
| Add Reference Labels | Whether to automatically add '_label' fields for reference fields with human-readable values in the service records. |
| Select Columns Names or IDs. | Choose which fields of the service records to include in the response. If no fields are selected, all fields will be returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Whether to bring user-defined fields up to the top level of each service record object, making them accessible as top-level properties instead of nested in the userDefinedFields array. |
Output
JSON
id- Unique identifier of the service record.name- Name of the service.description- Description of the service.status- Status of the service, possibly including a human-readable label if enabled.otherFields- Additional fields of the service record as specified by the selected columns or all fields if none selected.
Dependencies
- An API key credential for Kaseya Autotask PSA REST API authentication
Troubleshooting
- Ensure the API credentials are correctly configured and have sufficient permissions to access service records.
- If the node returns an error about unsupported resource, verify that 'Service' is correctly spelled and supported by the node version.
- If no records are returned, check the filter and limit settings to ensure they match expected data availability.
- Network or API rate limit errors may occur; verify network connectivity and API usage limits.
Links
- Kaseya Autotask PSA REST API Documentation - Official API documentation for interacting with Autotask resources including Service.