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 Contract Note from the Autotask system by its unique Note ID. It is useful for workflows that need to fetch detailed information about a particular contract note, such as auditing contract changes, displaying contract note details in dashboards, or integrating contract note data with other systems.
Properties
| Name | Meaning |
|---|---|
| Note ID | The unique identifier of the contract note to retrieve. This is a required field 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 in understanding picklist values without needing to decode them manually. |
| Add Reference Labels | Determines whether to automatically add human-readable "_label" fields for reference fields in the response. This makes reference fields easier to interpret. |
| 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 Note 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 contract note.subject- The subject or title of the contract note.description- Detailed description or content of the contract note.createdDate- The date and time when the contract note was created.modifiedDate- The date and time when the contract note was last modified.userDefinedFields- An array of user-defined fields associated with the contract note, unless flattened.
_label - Human-readable labels for picklist or reference fields, if enabled.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the Note ID is missing or invalid, the node will throw an error indicating the note could not be found. Ensure the Note ID is correct and exists in Autotask.
- If API authentication fails, verify that the API key credential is correctly configured and has sufficient permissions.
- Selecting invalid or unsupported fields in 'Select Columns' may result in incomplete or error responses. Use the provided dropdown or valid field IDs.
- If picklist or reference labels are not appearing as expected, check that the corresponding options 'Add Picklist Labels' and 'Add Reference Labels' are enabled.