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 a specific Configuration Item Note from the Autotask system by its Note ID. It is useful for fetching detailed information about a particular note attached to a configuration item, such as comments or updates related to IT assets or services. For example, a user can get the content and metadata of a note to display it in a dashboard or use it in further automation workflows.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the configuration item note to retrieve. This is required to specify which note to get. |
| Add Picklist Labels | Whether to automatically add human-readable label fields for picklist fields in the response, enhancing readability by including descriptive labels alongside raw values. |
| Add Reference Labels | Whether to automatically add human-readable label fields for reference fields in the response, providing descriptive labels for referenced entities. |
| Select Columns Names or IDs. | Specifies which fields to include in the response. If none are selected, all fields are returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Whether to bring user-defined fields (UDFs) up to the top level of the returned object instead of nested inside a userDefinedFields array, simplifying access to these custom fields. |
Output
JSON
id- The unique identifier of the configuration item note.content- The textual content or body of the note.createdDate- The date and time when the note was created.createdBy- Information about the user who created the note.userDefinedFields- An array of user-defined fields associated with the note, if any.
_label - Human-readable labels for picklist or reference fields, added if the corresponding options are enabled.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
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 key credential is correctly configured and has sufficient permissions.
- If no fields are returned or the output is empty, check the 'Select Columns' property to ensure desired fields are selected or leave it empty to retrieve all fields.