Magnet Customer icon

Magnet Customer

Consume Magnet Customer API

Actions68

Overview

The "Magnet Customer" node integrates with the Magnet Customer API to manage various CRM-related resources such as customers, deals, leads, prospects, organizations, tasks, staff, pipelines, and custom fields. Specifically, for the Customer - Get operation, this node retrieves detailed information about a single customer by their unique Contact ID.

This node is beneficial in scenarios where you need to fetch up-to-date customer data from your CRM system within an automated workflow. For example, you might use it to:

  • Retrieve customer details before sending a personalized email.
  • Fetch customer info to update records in another system.
  • Use customer data to trigger conditional logic in your automation.

Properties

Name Meaning
Authentication Method of authentication to access the API: either API Token or OAuth2.
Contact ID The unique identifier of the customer to retrieve. This is required for the Get operation on Customer.
Resolve Custom Fields When enabled, custom fields returned by the API are resolved to their actual names and option values instead of just IDs. Defaults to false.

Note: Several hidden properties related to "Life Cycle" and "Source" exist but are not user-configurable and serve internal purposes.

Output

The output JSON contains the detailed data of the requested customer. This includes standard customer fields as well as any custom fields associated with that customer. If the "Resolve Custom Fields" option is enabled, custom fields will be presented with their human-readable names and values rather than raw IDs.

The node does not output binary data.

Example output structure (simplified):

{
  "_id": "customerId123",
  "fullname": "John Doe",
  "email": "john.doe@example.com",
  "phone": "+1234567890",
  "customFields": {
    "customFieldName1": "Value1",
    "customFieldName2": "Value2"
  },
  ...
}

Dependencies

  • Requires connection to the Magnet Customer API.
  • Needs either an API token or OAuth2 credentials configured in n8n.
  • No additional environment variables are necessary beyond credential setup.

Troubleshooting

  • Invalid Contact ID: If the provided Contact ID does not exist, the API may return an error or empty response. Verify the ID is correct.
  • Authentication Errors: Ensure the API token or OAuth2 credentials are valid and have sufficient permissions.
  • Custom Field Resolution Issues: If enabling "Resolve Custom Fields" causes errors, it may be due to missing or misconfigured custom field metadata in the CRM.
  • Network/Timeout Issues: Check network connectivity and API availability if requests fail repeatedly.

Links and References

Discussion