Magnet Customer icon

Magnet Customer

Consume Magnet Customer API

Actions68

Overview

The "Lead - Get Many" operation in this node allows users to retrieve multiple lead records from the Magnet Customer API. This is useful for scenarios where you want to fetch a list of leads, for example, to analyze potential customers, sync lead data with other systems, or trigger workflows based on lead information.

Practical examples include:

  • Fetching all leads created within a certain timeframe to update a CRM.
  • Retrieving a paginated list of leads for reporting purposes.
  • Automatically processing new leads by pulling them into an automation workflow.

Properties

Name Meaning
Authentication Method used to authenticate API requests. Options: "API Token", "OAuth2".
Page The page number of results to retrieve (for pagination).
Limit Maximum number of lead records to return. Minimum value is 15.
Life Cycle The life cycle stage of the contact. For leads, this is set internally and hidden from the user.
Source The source identifier of the contact, defaulted to "n8n" and hidden from the user.
Resolve Custom Fields When enabled, custom fields that normally return only IDs will be resolved to their actual names/values automatically. Default is false.

Output

The output consists of JSON objects representing lead records retrieved from the Magnet Customer API. Each object contains the lead's data fields as returned by the API.

If "Resolve Custom Fields" is enabled, custom field IDs and option IDs are replaced with their corresponding names and values for easier readability.

No binary data output is produced by this operation.

Dependencies

  • Requires access to the Magnet Customer API.
  • Requires either an API token or OAuth2 credentials configured in n8n for authentication.
  • Pagination support depends on the API's paging mechanism via page and limit parameters.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Requesting a limit below the minimum (15) may result in errors or unexpected behavior.
    • Pagination parameters (page, limit) must be valid numbers; invalid inputs can cause request failures.
    • If custom fields are not resolving correctly, ensure the "Resolve Custom Fields" option is enabled.

  • Error messages:

    • Authentication errors typically indicate invalid or expired credentials; reconfigure your API key or OAuth2 token.
    • API rate limits or network errors may cause request failures; retry after some time or check connectivity.
    • Validation errors on input parameters will specify which parameter is incorrect; adjust accordingly.

Links and References

Discussion