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
This node operation retrieves multiple Contract Note records from the Autotask REST API using advanced filtering criteria. It is useful for users who need to query contract notes with complex conditions beyond simple filters, allowing precise data extraction for reporting, analysis, or integration purposes. For example, a user can fetch all contract notes related to specific contracts within a date range or matching particular custom fields.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching contract note records or limit the number of results. |
| Max Records | Specifies the maximum number of contract note 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 with Autotask API query criteria to perform advanced filtering of contract notes. |
| Add Picklist Labels | Indicates whether to automatically add human-readable '_label' fields for picklist fields in the returned contract note data. |
| Add Reference Labels | Indicates whether to automatically add human-readable '_label' fields for reference fields in the returned contract note data. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | Determines whether user-defined fields (UDFs) are brought up to the top level of each returned object instead of being nested. |
Output
JSON
id- Unique identifier of the contract note record.fieldName- Various contract note fields as specified by the selected columns or all fields if none selected.fieldName_label- Human-readable labels for picklist or reference fields if enabled.userDefinedFields- Array of user-defined fields unless flattened to top-level properties.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in the 'Advanced Filter' property will cause errors. Ensure the JSON string is well-formed and follows Autotask API filter syntax.
- Requesting too many records without pagination or 'Get All' enabled may lead to timeouts or API limits.
- Selecting invalid or non-existent fields in 'Select Columns' may result in incomplete data or errors.
- If picklist or reference labels are not appearing, verify that 'Add Picklist Labels' and 'Add Reference Labels' are enabled and that the fields have valid values.
- API authentication errors may occur if the API key credential is missing, expired, or invalid.
Links
- Autotask API Basic Query Calls - Official Autotask documentation describing how to construct advanced filter queries for API calls.