Autotask icon

Autotask

Consume Autotask REST API

Actions389

Contact → Get

AI-generated

Overview

This node retrieves detailed information about a specific contact from the Autotask system using the contact's unique ID. It is useful for workflows that need to fetch and utilize contact data, such as customer support automation, CRM integrations, or data synchronization tasks. For example, you can use it to get a contact's details before sending a personalized email or updating records in another system.

Properties

Name Meaning
Contact ID The unique identifier of the contact to retrieve. This is required to specify which contact's information to fetch.
Add Picklist Labels Determines whether to automatically add additional fields with human-readable labels for picklist fields in the contact data. This helps interpret picklist values more easily.
Add Reference Labels Determines whether to automatically add additional fields with human-readable labels for reference fields in the contact data. This clarifies referenced entities.
Select Columns Names or IDs. Allows selection of specific fields to include in the response. If none are selected, all fields are returned. The contact ID field is always included.
Flatten User-Defined Fields Determines whether user-defined fields (UDFs) are brought to the top level of the returned object instead of being nested inside an array. This simplifies access to UDFs.

Output

JSON

  • id - The unique identifier of the contact.
  • fields
    • * - Various contact fields returned based on selected columns or all fields if none selected.
  • *_label - Additional fields appended for picklist and reference fields containing human-readable labels, if enabled.
  • userDefinedFields - Array of user-defined fields unless flattened, in which case these fields appear at the top level.

Dependencies

  • Requires an API key credential for Autotask REST API authentication.

Troubleshooting

  • If the Contact ID is missing or invalid, the node will throw an error indicating the contact could not be found. Ensure the ID is correct and exists in Autotask.
  • If API authentication fails, verify that the API key credential is correctly configured and has sufficient permissions.
  • Selecting specific columns that do not exist may result in incomplete data or errors; verify field names or IDs.
  • Enabling picklist or reference labels when the fields are empty will not add label fields; this is expected behavior.

Discussion