Magnet Customer icon

Magnet Customer

Consume Magnet Customer API

Actions68

Overview

This node integrates with the Magnet Customer API to retrieve detailed information about a specific lead. The "Get Lead" operation fetches data for a single lead identified by its unique ID. This is useful in scenarios where you want to enrich your workflow with up-to-date lead details, such as contact information, status, or custom fields.

Practical examples include:

  • Fetching lead details after a form submission to trigger personalized follow-ups.
  • Retrieving lead information to update CRM records or synchronize data across platforms.
  • Using lead data to segment marketing campaigns or sales pipelines dynamically.

Properties

Name Meaning
Authentication Method of authentication to use: either "API Token" or "OAuth2".
Contact ID (leadId) The unique identifier of the lead to retrieve. This is required to specify which lead's data to get.
Resolve Custom Fields When enabled, custom fields and option fields are returned with their actual names/values instead of IDs.

Note: Several hidden properties related to "Life Cycle" and "Source" exist but are preset internally and not exposed for user input.

Output

The output is a JSON object representing the full details of the requested lead. This includes standard lead attributes such as name, contact info, status, and any associated custom fields.

If the "Resolve Custom Fields" option is enabled, custom field IDs and option IDs are automatically replaced with their corresponding human-readable names and values, making the output easier to interpret.

The node does not output binary data.

Dependencies

  • Requires access to the Magnet Customer API.
  • Requires an API key credential or OAuth2 authentication configured in n8n.
  • No additional environment variables are needed beyond the configured credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing lead ID will cause the request to fail.
    • Incorrect or expired API credentials will result in authentication errors.
    • If custom fields are not resolving correctly, ensure the "Resolve Custom Fields" option is enabled.

  • Error messages:

    • "Lead not found": The specified lead ID does not exist; verify the ID.
    • "Authentication failed": Check that the API token or OAuth2 credentials are valid and have necessary permissions.
    • Network or timeout errors: Verify network connectivity and API availability.

Links and References

Discussion