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 Note → Get Many (Advanced)
AI-generatedOverview
This node operation retrieves multiple Contract Note records from the Autotask PSA system using advanced filtering criteria. It is useful for scenarios where users need to query contract notes with specific conditions, such as filtering by date, status, or other custom fields, and control the number of records returned. For example, a user might want to fetch all contract notes related to a particular contract within a date range or with certain keywords in the note content.
Use Case Examples
- Retrieve all contract notes for a specific contract ID with a custom filter.
- Fetch up to 100 contract notes that match advanced JSON filter criteria.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all results or only up to a given limit. |
| Max Records | Maximum number of contract note records to return when 'Get All' is false. |
| Advanced Filter | A JSON string containing a 'filter' array with Autotask API query criteria to filter contract notes. |
| Add Picklist Labels | Whether to automatically add '_label' fields for picklist fields with human-readable values. |
| Add Reference Labels | Whether to automatically add '_label' fields for reference fields with human-readable values. |
| Select Columns Names or IDs | Choose which fields to include in the response. If no fields are selected, all fields will be returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Whether to bring user-defined fields up to the top level of each object for easier access. |
Output
JSON
id- Unique identifier of the contract note.content- Content or text of the contract note.createdDate- Date when the contract note was created.modifiedDate- Date when the contract note was last modified.contractId- Identifier of the contract associated with the note.userDefinedFields- Array of user-defined fields related to the contract note, if not flattened._label- Additional human-readable labels for picklist or reference fields if enabled.
Dependencies
- Autotask PSA REST API
- API key credential for authentication
Troubleshooting
- Ensure the advanced filter JSON is correctly formatted and matches Autotask API query criteria to avoid errors.
- If no records are returned, verify the filter criteria and the selected columns to ensure they exist and are accessible.
- Authentication errors may occur if API credentials are invalid or expired; verify and update credentials as needed.
- Rate limiting by the Autotask API may cause request failures; monitor usage and apply retries or backoff as necessary.
Links
- Autotask API Basic Query Calls - Official documentation for constructing advanced filter queries for Autotask API.
- n8n Autotask Node GitHub Repository - Source code and documentation for the Autotask node in n8n.