LeadMagic icon

LeadMagic

B2B data enrichment and lead generation with email finding, company intelligence, and profile enrichment

Overview

The node integrates with a B2B data enrichment and lead generation service, focusing on professional profile enrichment and social data under the "Profile" resource. Specifically, the "Search Profile" operation allows users to input a full URL of a B2B professional profile (e.g., LinkedIn) and retrieve enriched profile information from the external service.

This node is beneficial in scenarios such as:

  • Enriching CRM or marketing databases with detailed professional profile data.
  • Verifying or augmenting contact information for sales prospecting.
  • Automating lead qualification by gathering social and professional insights.

Example use case:
A user provides a LinkedIn profile URL of a potential client, and the node returns detailed information about that person's professional background, enabling personalized outreach.

Properties

Name Meaning
Profile URL Full URL of the B2B profile to search. Example: https://www.example.com/in/williamhgates/

Output

The node outputs JSON data containing the enriched profile information returned by the external API. The structure typically includes various fields describing the professional profile details such as name, job title, company, social links, and other relevant enrichment data.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the external B2B data enrichment service.
  • The node makes HTTP POST requests to the endpoint: https://api.leadmagic.io/profile-search.
  • Proper configuration of the API authentication credential within n8n is necessary.

Troubleshooting

  • Common issues:

    • Providing an invalid or malformed profile URL may result in errors or empty responses.
    • Network connectivity problems or incorrect API credentials will cause request failures.
    • Rate limiting or quota exceeded errors if the API usage limits are surpassed.
  • Error messages:

    • Errors from the external API will be captured and returned in the output JSON under an error field if "Continue On Fail" is enabled.
    • If too many inputs or invalid parameters are provided, the node may throw descriptive errors indicating the problem.
  • Resolution tips:

    • Verify the profile URL format before input.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Check network access and proxy settings if applicable.
    • Use the "Continue On Fail" option to handle partial failures gracefully.

Links and References

Discussion