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 a specific Company Note by its ID. It is useful for workflows that need to fetch detailed information about a particular note associated with a company in Autotask, such as for auditing, reporting, or integration with other systems. For example, a user can automate the retrieval of a company note to include its content in a customer support ticket or to synchronize notes with a CRM system.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the company note to retrieve. This is a required input to specify which note to get. |
| Add Picklist Labels | Determines whether to automatically add human-readable "_label" fields for picklist fields in the response. This helps interpret picklist values more easily. |
| Add Reference Labels | Determines whether to automatically add human-readable "_label" fields for reference fields in the response, improving readability of referenced entities. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If none are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are brought to the top level of the output object instead of being nested, simplifying access to these fields. |
Output
JSON
id- The unique identifier of the company note.content- The textual content of the company note.createdDate- The date and time when the note was created.createdBy- Information about the user who created the note, possibly including a label if 'Add Reference Labels' is enabled.userDefinedFields- An array of user-defined fields associated with the note, or flattened to top-level properties if 'Flatten User-Defined Fields' is enabled.
- Additional fields selected via 'Select Columns' input, including picklist and reference labels if enabled.
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 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 or are not accessible may result in incomplete data or errors. Use the 'Select Columns' dropdown to choose valid fields.
- Enabling 'Add Picklist Labels' or 'Add Reference Labels' may increase response size and processing time; disable if performance is a concern.