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 API to retrieve detailed information about a specific Ticket Note by its ID. It is useful for scenarios where you need to fetch and process notes attached to support tickets, such as for auditing, reporting, or integrating ticket note data into other workflows. For example, you can use this node to get the content and metadata of a ticket note to display in a dashboard or to trigger follow-up actions based on note content.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the ticket note to retrieve. This is required to specify which note to fetch. |
| Add Picklist Labels | Determines whether to automatically add human-readable "_label" fields for picklist fields in the response. This helps interpret picklist values by providing their labels alongside raw values. |
| Add Reference Labels | Determines whether to automatically add human-readable "_label" fields for reference fields in the response. This helps interpret reference IDs by providing their labels. |
| 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 regardless of selection. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are brought to the top level of the returned object instead of being nested inside a userDefinedFields array, simplifying access to these fields. |
Output
JSON
id- The unique identifier of the ticket note.content- The textual content of the ticket 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.userDefinedFields- An array of user-defined fields associated with the ticket note, unless flattened.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.
Dependencies
- Requires an API key credential for Autotask API authentication.
Troubleshooting
- If the Note ID is invalid or does not exist, the node will throw an error indicating the note was not found. Verify the Note ID is correct.
- If API authentication fails, ensure the Autotask API credentials are correctly configured and have sufficient permissions.
- Selecting fields that do not exist may result in incomplete data or errors; verify field names or IDs when using 'Select Columns'.
- Enabling 'Flatten User-Defined Fields' may cause naming conflicts if UDF names overlap with standard fields; use with caution.