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 interacts with the Autotask REST API to retrieve detailed information about a specific Project Note by its ID. It is useful for workflows that need to fetch and process notes associated with projects, such as project documentation, updates, or comments. For example, it can be used to automatically pull the latest note content for reporting or integration with other systems.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the project note to retrieve. |
| Add Picklist Labels | Determines whether to add additional fields with human-readable labels for picklist fields in the response. Labels are only added if the picklist value is not empty. |
| Add Reference Labels | Determines whether to add additional fields with human-readable labels for reference fields in the response. Labels are only added if the reference value is not empty. |
| Select Columns Names or IDs. | Specifies which fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Determines whether user-defined fields (UDFs) should be moved to the top level of the returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- The unique identifier of the project note.content- The main content or text of the project note.createdDate- The date and time when the note was created.createdBy- Information about the user who created the note, possibly including user ID and name.picklistField_label- Human-readable labels for picklist fields, added if 'Add Picklist Labels' is enabled.referenceField_label- Human-readable labels for reference fields, added if 'Add Reference Labels' is enabled.userDefinedFields- An array of user-defined fields associated with the note, unless flattened to top-level properties.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the Note ID is invalid or does not exist, the node will throw an error indicating the note could not be found. Verify the Note ID is correct.
- If API authentication fails, ensure the Autotask API credentials are correctly configured and have sufficient permissions.
- Selecting specific columns that do not exist or are misspelled may result in incomplete or empty data. Use the 'Select Columns' dropdown or expressions carefully.
- Enabling 'Flatten User-Defined Fields' may cause naming conflicts if UDF names overlap with standard fields; disable if unexpected data structure issues occur.