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
Contract Service → Get Many
AI-generatedOverview
This node operation retrieves multiple records of Contract Services from the Autotask PSA system. It supports fetching all records or a limited number based on user input, and can include additional options such as adding human-readable labels for picklist and reference fields, selecting specific columns, and flattening user-defined fields for easier access. This operation is useful for scenarios where users need to list or analyze multiple contract service entries, such as generating reports, syncing data with other systems, or performing bulk updates.
Use Case Examples
- Retrieve all contract services to generate a comprehensive report on service usage.
- Fetch a limited number of contract services to display in a dashboard or UI component.
- Get contract services with specific fields selected to optimize data transfer and processing.
Properties
| Name | Meaning |
|---|---|
| returnAll | Whether to return all contract service records or only up to a specified limit. |
| maxRecords | Maximum number of contract service records to return when returnAll is false. Range is 1 to 500. |
| addPicklistLabels | Whether to automatically add human-readable "_label" fields for picklist fields in the response. |
| addReferenceLabels | Whether to automatically add human-readable "_label" fields for reference fields in the response. |
| selectColumns | Specify which fields (columns) to include in the response. If none are selected, all fields are returned. The ID field is always included. |
| flattenUdfs | Whether to bring user-defined fields (UDFs) up to the top level of each object instead of nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the contract service record.name- Name of the contract service.description- Description of the contract service.status- Status of the contract service, possibly including a human-readable label if addPicklistLabels or addReferenceLabels is enabled.userDefinedFields- User-defined fields related to the contract service, either nested or flattened based on flattenUdfs setting._label- Additional human-readable labels for picklist or reference fields, appended with '_label' suffix.
Dependencies
- An API key credential for Autotask PSA REST API
Troubleshooting
- Ensure the API credentials are correctly configured and have sufficient permissions to access contract service data.
- If the node returns no data, verify that contract services exist in the Autotask system and that any filters or limits are set appropriately.
- Errors related to rate limits may occur; ensure the API usage complies with Autotask's rate limiting policies.
Links
- Autotask PSA REST API Documentation - Official documentation for the Autotask PSA REST API, useful for understanding available endpoints and data structures related to contract services.