LeadMagic icon

LeadMagic

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

Actions16

Overview

This node integrates with the LeadMagic API to enrich B2B data, focusing on professional profile enrichment and social data retrieval. Specifically, the "Email to Profile" operation under the "Profile" resource allows users to input a work email address and retrieve detailed profile information associated with that email. This is useful for sales, marketing, or recruitment professionals who want to gather enriched contact and professional details from an email address.

Practical examples:

  • A sales team inputs a lead’s work email to get their professional profile, including job title, company, and social links.
  • A recruiter uses a candidate’s work email to fetch their updated professional profile for screening.
  • Marketing teams enrich their CRM contacts by converting emails into detailed profiles.

Properties

Name Meaning
Work Email The work email address used to find the corresponding professional profile.

Output

The node outputs JSON data representing the enriched professional profile linked to the provided work email. The structure typically includes fields such as name, job title, company details, social media links, and other relevant professional information returned by the LeadMagic API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active LeadMagic API key credential configured in n8n.
  • The node makes authenticated HTTP POST requests to the LeadMagic API endpoint https://api.leadmagic.io/b2b-profile.
  • Proper network connectivity to the LeadMagic API service is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing an invalid or non-existent work email may result in empty or error responses.
    • Network issues can prevent successful API calls.

  • Error messages:

    • Errors from the API are caught and returned in the output JSON under an error field if "Continue On Fail" is enabled.
    • If too many emails are provided in bulk operations (not applicable here but related), an error about exceeding maximum allowed emails may occur.

  • Resolutions:

    • Verify the API key credential is correctly set up.
    • Ensure the work email is valid and correctly formatted.
    • Check internet connectivity and API service status.
    • Enable "Continue On Fail" to handle errors gracefully within workflows.

Links and References

Discussion