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
The 'Contact Webhook - Get Many (Advanced)' operation in the Autotask node allows users to retrieve multiple contact webhook records from the Autotask REST API using advanced filtering criteria. This operation is beneficial when you need to query contact webhook data with complex conditions beyond simple filters, such as combining multiple criteria in a JSON-based filter. For example, you can fetch all contact webhooks created after a certain date or those matching specific status codes. It supports returning all matching records or limiting the number of results, and can enhance the output by adding human-readable labels for picklist and reference fields, as well as flattening user-defined fields for easier access.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching 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. The value must be between 1 and 500. |
| Advanced Filter | A required JSON string containing a 'filter' array that defines the Autotask API query criteria for filtering contact webhook records. This allows complex queries using Autotask's REST API filtering syntax. |
| Add Picklist Labels | If enabled, adds additional '_label' fields to the output for picklist fields, providing human-readable values instead of raw codes. |
| Add Reference Labels | If enabled, adds additional '_label' fields to the output for reference fields, providing human-readable 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. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are moved to the top level of each returned object instead of being nested inside a 'userDefinedFields' array, simplifying access. |
Output
JSON
id- Unique identifier of the contact webhook record.fieldName- Various fields of the contact webhook record as returned by the Autotask API, including standard and user-defined fields._label- Additional fields with '_label' suffix provide human-readable labels for picklist and reference fields if enabled.userDefinedFields- Array of user-defined fields associated with the contact webhook, unless flattened to top-level properties.
Dependencies
- Requires an Autotask API credential with appropriate permissions to access contact webhook data.
- Relies on the Autotask REST API endpoint for contact webhooks.
Troubleshooting
- Invalid JSON in 'Advanced Filter' property can cause query failures. Ensure the JSON string is correctly formatted and follows Autotask API filter syntax.
- Requesting too many records without proper limits may lead to timeouts or API rate limiting. Use 'Get All' judiciously or set reasonable 'Max Records'.
- If picklist or reference labels are not appearing, verify that the corresponding fields have valid values and that label addition options are enabled.
- Errors related to authentication indicate issues with the provided Autotask API credentials; verify and update credentials as needed.
Links
- Autotask API Basic Query Calls - Official Autotask documentation describing how to construct advanced filter queries for API calls.