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 multiple Contact Webhook records from the Autotask system. It is useful for scenarios where you need to fetch a list of contact webhook configurations, for example, to synchronize webhook settings, audit webhook usage, or integrate webhook data into other workflows. Users can specify which fields to retrieve, limit the number of records, and control how picklist and reference fields are labeled for easier interpretation.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Contact Webhook resource to retrieve and map in the output. Supports custom mapping and selection of specific fields. |
| Get All | Determines whether to return all available Contact Webhook records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of Contact Webhook records to return when 'Get All' is false. Value range is 1 to 500. |
| Add Picklist Labels | If enabled, adds human-readable label fields for picklist fields in the output, making it easier to understand picklist values. |
| Add Reference Labels | If enabled, adds human-readable label fields for reference fields in the output, improving readability of referenced data. |
| Select Columns Names or IDs. | Allows selection of specific columns (fields) to include in the response. If none are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | When enabled, user-defined fields (UDFs) are promoted to top-level properties in each returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the Contact Webhook record.fieldName_label- Human-readable labels for picklist or reference fields if Add Picklist Labels or Add Reference Labels is enabled.
userDefinedFieldsudfName- User-defined fields nested or flattened depending on Flatten User-Defined Fields setting.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the Contact Webhook resource exists and that the API credentials have sufficient permissions.
- Errors related to field mapping may occur if specified fields do not exist; ensure correct field names or IDs are used.
- If the node returns partial data, check the Max Records setting and the Get All flag to ensure the desired number of records is fetched.