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
The node interacts with the Autotask REST API to retrieve multiple contract records based on user-defined criteria. It supports fetching either all available contracts or a limited number, with options to select specific fields, include human-readable labels for picklist and reference fields, and flatten user-defined fields for easier access. This node is useful for automating workflows that require bulk contract data retrieval, such as reporting, data synchronization, or integration with other systems.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which contract fields to retrieve and map in the output. Supports custom mapping and auto-mapping of fields. |
| Get All | Determines whether to return all matching contract records or limit the number of records returned. |
| Max Records | Specifies the maximum number of contract 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 contract 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 contract object instead of being nested. |
Output
JSON
contracts- An array of contract objects retrieved from Autotask, each containing the selected fields and optionally added labels and flattened user-defined fields.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If no contracts are returned, verify that the API credentials are correct and have sufficient permissions.
- Ensure that the 'Max Records' value is within the allowed range (1-500) when 'Get All' is false.
- If selected fields do not appear in the output, confirm that the field names or IDs are valid and available for the contract resource.
- Network or API errors may occur if the Autotask service is unreachable or if rate limits are exceeded; retry after some time or check API usage limits.