LeadMagic icon

LeadMagic

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

Actions16

Overview

This node integrates with a B2B data enrichment and lead generation service to find mobile phone numbers associated with professional profiles. Specifically, the "Find Mobile" operation under the "Profile" resource allows users to retrieve a mobile number by searching through one of three methods: profile URL, work email, or personal email.

Common scenarios where this node is beneficial include:

  • Sales and marketing teams looking to enrich their contact lists with direct mobile numbers.
  • Recruiters seeking additional contact details for candidates.
  • Customer success teams aiming to reach out via mobile for personalized communication.

Practical example:

  • Given a LinkedIn profile URL, the node can return the mobile phone number linked to that profile.
  • Alternatively, if only an email address (work or personal) is known, the node attempts to find the corresponding mobile number.

Properties

Name Meaning
Search Method How to search for the mobile number. Options:
• By Profile URL (most accurate)
• By Work Email
• By Personal Email
Profile URL The B2B profile URL to search by (required if Search Method is "By Profile URL"). Example: https://www.example.com/in/williamhgates/
Work Email The work email address to search by (required if Search Method is "By Work Email"). Example: [email protected]
Personal Email The personal email address to search by (required if Search Method is "By Personal Email"). Example: [email protected]

Output

The node outputs JSON data containing the results returned from the external API call to the mobile finder endpoint. The structure typically includes fields related to the found mobile number and possibly additional metadata about the profile or contact.

If the mobile number is found, it will be included in the JSON output. If no number is found or an error occurs, the output may contain an error message describing the issue.

The node does not output binary data.

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/mobile-finder.
  • Proper configuration of the API key credential within n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Providing an invalid or malformed profile URL or email address may result in no data found or errors.
    • Exceeding rate limits or quota on the external API could cause request failures.
    • Missing or incorrect API authentication credentials will prevent successful API calls.

  • Error messages:

    • Errors returned from the API are passed through in the output JSON under an error field.
    • If too many emails are provided in bulk operations (not applicable here but relevant for other operations), an error about maximum allowed inputs will appear.

  • Resolution tips:

    • Verify that the input values (profile URL or emails) are correct and properly formatted.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Use the "Continue On Fail" option in n8n to handle errors gracefully without stopping the workflow.

Links and References

Discussion