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 system. It is useful for scenarios where users need to fetch a list of contract notes for reporting, analysis, or integration purposes. For example, a user might want to extract all contract notes related to a specific contract or within a certain date range to synchronize with another system or generate summaries.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Contract Note resource to map and include in the output. This allows users to specify exactly which data points they want to retrieve. |
| Get All | Determines whether to return all available Contract Note records or limit the number of records returned. |
| Max Records | Specifies the maximum number of Contract Note records to return when 'Get All' is set to false. The value can range from 1 to 500. |
| Add Picklist Labels | Indicates whether to add human-readable labels for picklist fields in the output, enhancing readability by including '_label' fields. |
| Add Reference Labels | Indicates whether to add human-readable labels for reference fields in the output, adding '_label' fields for better clarity. |
| 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) should be promoted to top-level properties in the output objects instead of being nested within an array. |
Output
JSON
id- Unique identifier of the Contract Note record.fieldName- Various fields of the Contract Note as specified by the selected fields mapping.picklistField_label- Human-readable label for picklist fields if 'Add Picklist Labels' is enabled.
referenceField_label- Human-readable label for reference fields if 'Add Reference Labels' is enabled.
userDefinedFields- Array of user-defined fields unless 'Flatten User-Defined Fields' is enabled, in which case UDFs appear as top-level properties.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If no records are returned, verify that the query parameters and field mappings are correct and that the user has access to the Contract Note data.
- If the node fails with authentication errors, ensure that the API key credential is valid and has sufficient permissions.
- When selecting fields, if unexpected data is missing, check if 'Select Columns' is restricting the output fields.
- Large data requests may time out or be limited; use 'Max Records' to limit the number of records or enable 'Get All' cautiously.