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 allows users to create a Ticket Note in the Autotask system via its REST API. It is useful for adding notes or comments to support tickets programmatically within an automation workflow. For example, after processing a customer support request, the node can add a detailed note to the related ticket to document the interaction or resolution steps.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the fields and their values to be mapped and sent when creating the Ticket Note. This property supports selecting and mapping specific fields relevant to the ticket note creation. |
Output
JSON
id- The unique identifier of the created Ticket Note.content- The content or text of the created Ticket Note.ticketID- The identifier of the ticket to which the note was added.createdDate- The date and time when the Ticket Note was created.
Dependencies
- Requires an Autotask API credential for authentication to the Autotask REST API.
Troubleshooting
- Ensure the Autotask API credentials are correctly configured and have sufficient permissions to create ticket notes.
- Verify that all required fields for creating a ticket note are provided in the 'Fields' property; missing mandatory fields may cause errors.
- If the API returns an error about invalid field values, check the field mappings and data types to ensure they conform to Autotask's API specifications.
- Network connectivity issues or API rate limits may cause failures; verify network access and consider retry logic if needed.