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
The node retrieves multiple Project Note records from the Autotask system. It is useful for workflows that need to fetch and process lists of project notes, such as generating reports, syncing data, or analyzing project communications. For example, a user can fetch all project notes related to a specific project or within a date range to monitor project progress or audit notes.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Project Note resource to retrieve and map in the output. Supports custom mapping and selection of specific fields. |
| Get All | Determines whether to return all matching project notes or limit the number of records returned. |
| Max Records | Specifies the maximum number of project note records to return when 'Get All' is false. Value range is 1 to 500. |
| Add Picklist Labels | If enabled, adds human-readable label fields for picklist fields in the output, enhancing readability. |
| Add Reference Labels | If enabled, adds human-readable label fields for reference fields in the output. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If none selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are promoted to top-level properties in each returned object instead of being nested. |
Output
JSON
id- Unique identifier of the project note.subject- Subject or title of the project note.noteText- Content text of the project note.createdDate- Date and time when the note was created.createdByResourceID- Identifier of the resource (user) who created the note.projectID- Identifier of the project to which the note belongs._label fields- Additional human-readable labels for picklist and reference fields if enabled in the node properties.userDefinedFields- Array of user-defined fields associated with the project note, or flattened to top-level properties if enabled.
Dependencies
- Autotask REST API
Troubleshooting
- Ensure the API credentials are correctly configured and have permissions to access Project Notes.
- If no records are returned, verify the filters and field selections are correct and that matching project notes exist.
- Errors related to field mapping may occur if selected fields do not exist or are misspelled; verify field names.
- API rate limits may cause failures; consider enabling 'Get All' cautiously or limiting max records.