Actions389
- Ticket History Actions
- Ticket Note Actions
- Ticket Note Webhook Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Resource Role Actions
- Role Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Skill Actions
- Survey Actions
- Survey Results Actions
- Ticket Actions
- Invoice Actions
- Notification History Actions
- Opportunity Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Note Actions
- Project Phase Actions
- Project Task 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
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set 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
- 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
- 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
- Billing Code Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Contract → Get Many (Advanced)
AI-generatedOverview
This node operation retrieves multiple Contract records from the Autotask system using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter contracts, control the number of records returned, and customize the output fields. This is useful for scenarios where precise contract data extraction is needed, such as generating reports, syncing contract data with other systems, or performing bulk data analysis.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching contract records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of contract records to return when 'Get All' is false. The value must be between 1 and 500. |
| Advanced Filter | A required JSON string containing a 'filter' array that defines the Autotask API query criteria to filter contracts. Users should construct this JSON using the Autotask API documentation and helper tools. |
| Add Picklist Labels | Indicates whether to automatically add human-readable '_label' fields for picklist fields in the contract data. Labels are not added for empty values. |
| Add Reference Labels | Indicates whether to automatically add human-readable '_label' fields for reference fields in the contract data. Labels are not added for empty values. |
| Select Columns Names or IDs. | Allows selection of specific contract fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Determines whether user-defined fields (UDFs) are brought up to the top level of each contract object instead of being nested inside a 'userDefinedFields' array. |
Output
JSON
contracts- ``
*id- The unique identifier of the contract.
*userDefinedFields- Array of user-defined fields if 'Flatten User-Defined Fields' is false. _label- Optional human-readable labels for picklist or reference fields, appended as '_label' fields.
- ``
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in 'Advanced Filter' property can cause query failures. Ensure the JSON string is well-formed and follows Autotask API query syntax.
- Requesting too many records without pagination or 'Get All' enabled may lead to timeouts or API rate limiting.
- Selecting fields that do not exist or are misspelled in 'Select Columns' may result in incomplete data or errors.
- If labels are not appearing as expected, verify that 'Add Picklist Labels' and 'Add Reference Labels' are enabled and that the fields have valid values.
- Flattening user-defined fields may cause naming conflicts if UDF names overlap with standard fields.
Links
- Autotask API Basic Query Calls - Official Autotask documentation for constructing advanced filter queries.
- n8n Expressions Documentation - Guide on using expressions to specify dynamic values such as field IDs in 'Select Columns'.