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 interacts with the Autotask REST API to retrieve multiple Contact records based on user-defined criteria. It is useful for workflows that need to fetch lists of contacts from Autotask, such as syncing contact data, generating reports, or integrating contact information with other systems. For example, a user can retrieve all contacts or limit the number of contacts returned, select specific fields to include, and optionally add human-readable labels for picklist and reference fields.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Contact resource to retrieve and map in the output. Supports custom mapping and auto-mapping of fields. |
| Get All | Determines whether to return all matching Contact records or limit the results to a 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. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields in the Contact data. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields in the Contact data. |
| 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 | If enabled, user-defined fields (UDFs) are moved 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.fields- Values of the selected Contact fields as defined by the user mapping._label - Human-readable labels for picklist or reference fields if 'Add Picklist Labels' or 'Add Reference Labels' is enabled.userDefinedFields- Array of user-defined fields for the Contact, unless flattened to top-level properties.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If no contacts are returned, verify that the resource is set to 'contact' and the operation is 'getMany'.
- Ensure the API credentials are valid and have sufficient permissions to read Contact data.
- If the node returns an error about unsupported resource, confirm that the resource parameter is correctly set to 'contact'.
- When selecting specific fields, ensure the field names or IDs are valid and exist in the Autotask Contact schema.
- If the maximum records limit is exceeded, reduce the 'Max Records' value or enable 'Get All' to retrieve all records.