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 Ticket Note Webhook from the Autotask system by its unique Webhook ID. It is useful for workflows that need to fetch detailed information about a particular webhook related to ticket notes, such as monitoring webhook configurations or integrating webhook data into other systems.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The unique identifier of the ticket note webhook to retrieve. This is a required field to specify which webhook to get. |
| Add Picklist Labels | Determines whether to automatically add human-readable "_label" fields for picklist fields in the response. Labels are only added for non-empty values. |
| Add Reference Labels | Determines whether to automatically add human-readable "_label" fields for reference fields in the response. Labels are only added for non-empty values. |
| 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 | Determines whether user-defined fields (UDFs) are brought up to the top level of each object instead of being nested inside the userDefinedFields array. |
Output
JSON
id- The unique identifier of the ticket note webhook.name- The name of the ticket note webhook.url- The URL endpoint configured for the webhook.eventTypes- The types of ticket note events that trigger the webhook.isActive- Indicates whether the webhook is currently active.createdDate- The date and time when the webhook was created.modifiedDate- The date and time when the webhook was last modified.userDefinedFields- An array of user-defined fields associated with the webhook, unless flattened to top-level properties.
_label - Human-readable labels for picklist or reference fields, added if enabled in the input properties.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the Webhook ID is invalid or not found, the node will throw an error indicating the webhook does not exist. Verify the ID is correct and the webhook exists in Autotask.
- If API authentication fails, ensure the API key credential is correctly configured and has sufficient permissions to access ticket note webhooks.
- If no fields appear in the output, check the 'Select Columns' property to ensure desired fields are selected or left empty to return all fields.
- Enabling 'Add Picklist Labels' or 'Add Reference Labels' may increase response size; disable if not needed to optimize performance.