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 records from the Autotask system using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter contacts precisely. Users can choose to return all matching contacts or limit the number of records returned. Additionally, it supports options to include human-readable labels for picklist and reference fields, select specific columns to return, and flatten user-defined fields for easier access. This operation is beneficial for scenarios where detailed and customized contact data retrieval is needed, such as generating reports, syncing contacts with other systems, or performing bulk data analysis.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching contact records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of contact 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 to filter contacts. This allows complex and precise filtering based on contact fields. |
| Add Picklist Labels | Indicates whether to automatically add additional fields with '_label' suffix for picklist fields, providing human-readable values instead of raw codes. |
| Add Reference Labels | Indicates whether to automatically add additional fields with '_label' suffix for reference fields, providing human-readable values. |
| Select Columns Names or IDs. | Allows selection of specific contact 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 | Determines whether user-defined fields (UDFs) are brought up to the top level of each contact object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the contact record.fieldName- Various contact fields as specified or all fields if none selected.fieldName_label- Human-readable label for picklist or reference fields if enabled.userDefinedFields- Array of user-defined fields associated with the contact, unless flattened.userDefinedFieldName- User-defined fields brought to top-level properties if flattenUdfs is enabled.
Dependencies
- Requires an Autotask API key credential for authentication.
- Relies on the Autotask REST API to perform advanced filtered queries on Contact resources.
Troubleshooting
- Invalid JSON in the 'Advanced Filter' property will cause query errors. Ensure the JSON string is well-formed and follows Autotask API filter syntax.
- Requesting too many records without pagination or limits may lead to timeouts or API rate limiting.
- Selecting non-existent fields in 'Select Columns' may result in empty or error responses.
- If picklist or reference labels are enabled but no labels appear, verify that the fields contain valid values.
- Ensure the API credentials have sufficient permissions to read Contact data.
Links
- Autotask API Basic Query Calls - Official documentation for constructing advanced filter queries for Autotask REST API.