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 Project Note records from the Autotask REST API using advanced filtering criteria. It is useful for users who need to query project notes with complex conditions, such as filtering by specific fields or values, and control the number of records returned. For example, a project manager can use this operation to fetch all notes related to a particular project phase or notes created within a certain date range.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching project note records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of project 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 that defines the query criteria according to the Autotask API's advanced query syntax. This allows complex filtering of project notes based on various fields. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix to the output for picklist fields, providing human-readable labels instead of raw values. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix to the output for reference fields, providing human-readable labels instead of raw IDs. |
| 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 | If enabled, user-defined fields (UDFs) are moved to the top level of each returned object instead of being nested inside a 'userDefinedFields' array. |
Output
JSON
id- Unique identifier of the project note record.content- The textual content of the project note.createdDate- Date and time when the project note was created.modifiedDate- Date and time when the project note was last modified.userDefinedFields- Array of user-defined fields associated with the project note, unless flattened.
_label - Human-readable label for picklist or reference fields if 'Add Picklist Labels' or 'Add Reference Labels' is enabled.
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 filter syntax.
- Requesting too many records without pagination or 'Get All' enabled may lead to timeouts or API limits. Use 'Max Records' to limit results.
- If picklist or reference labels are not appearing, verify that 'Add Picklist Labels' and 'Add Reference Labels' are enabled and that the fields support labels.
- Errors related to unsupported fields in 'Select Columns' may occur if field names or IDs are incorrect. Use 'Get Field Info' to confirm valid fields.
Links
- Autotask API Basic Query Calls - Official documentation for constructing advanced filter queries for Autotask API.