Magnet Customer icon

Magnet Customer

Consume Magnet Customer API

Actions104

Customer → Get

AI-generated

Overview

This node interacts with the Magnet Customer API to retrieve detailed information about a specific customer by their ID. It supports authentication via API Token or OAuth2. The node is useful for scenarios where you need to fetch customer data for further processing, reporting, or integration with other systems. For example, you can use it to get customer details in a CRM workflow or to synchronize customer data with another platform.

Use Case Examples

  1. Retrieve a customer's full profile by their unique Contact ID to display in a dashboard.
  2. Fetch customer data to update records in an external database or CRM system.

Properties

Name Meaning
Authentication Select the authentication method to use for the API request (API Token or OAuth2).
Contact ID The unique identifier of the customer to retrieve. This is a required field for the 'Get' operation on the 'Customer' resource.
Resolve Custom Fields If enabled, custom fields returned as IDs will be resolved to their actual names and option fields will show their actual values instead of IDs. This applies to 'get' and 'getAll' operations for customer and related resources.

Output

JSON

  • _id - The unique identifier of the customer.
  • fullname - The full name of the customer.
  • email - The email address of the customer.
  • phone - The phone number of the customer.
  • customFields - Custom fields associated with the customer, which can be resolved to actual names and values if the 'Resolve Custom Fields' option is enabled.
  • createdAt - The date and time when the customer record was created.
  • updatedAt - The date and time when the customer record was last updated.

Dependencies

  • Magnet Customer API

Troubleshooting

  • Ensure the Contact ID is correctly provided and exists in the Magnet Customer system; otherwise, the API will return an error indicating the customer was not found.
  • If using OAuth2 authentication, verify that the OAuth2 token is valid and has not expired.
  • If the 'Resolve Custom Fields' option is enabled but custom fields do not resolve correctly, check that the API user has permissions to access custom field metadata.
  • Common error messages include authentication failures (invalid token), resource not found (invalid Contact ID), and permission denied errors. Resolving these typically involves verifying credentials, input parameters, and API permissions.

Links

Discussion