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 → Get Many
AI-generatedOverview
This node operation retrieves multiple contract records from the Autotask PSA system. It supports fetching all contracts or a limited number based on user input, with options to customize the output fields and include human-readable labels for picklist and reference fields. This operation is useful for scenarios where users need to list or analyze multiple contracts, such as generating reports, syncing contract data with other systems, or performing bulk updates.
Use Case Examples
- Fetch all contracts to synchronize with an external CRM system.
- Retrieve a limited number of contracts for review or reporting purposes.
- Get contracts with specific fields selected to optimize data transfer and processing.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all contract records or only up to a specified limit. |
| Max Records | Maximum number of contract records to return when not returning all. Range is 1 to 500. |
| Add Picklist Labels | Whether to automatically add human-readable '_label' fields for picklist fields in the contract data. |
| Add Reference Labels | Whether to automatically add human-readable '_label' fields for reference fields in the contract data. |
| Select Columns Names or IDs. | Choose specific contract fields to include in the response. If none are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | Whether to bring user-defined fields (UDFs) up to the top level of each contract object instead of nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the contract record.contractNumber- Contract number or identifier.contractName- Name or title of the contract.startDate- Start date of the contract.endDate- End date of the contract.status- Current status of the contract.billingType- Billing type associated with the contract.userDefinedFields- Array of user-defined fields related to the contract, unless flattened._label- Human-readable labels for picklist and reference fields if enabled.
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 data.
- If the node returns no data, verify that contracts exist in the Autotask system and that filters or limits are set appropriately.
- Errors related to rate limits may occur; the node attempts to initialize a rate tracker but falls back to local counting if it fails.
Links
- Autotask PSA REST API Documentation - Official documentation for the Autotask PSA REST API used by this node.