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, focusing on competitive advertisement intelligence across platforms. Specifically, the Search B2B Ads operation allows users to search for business-to-business advertisements related to a company by either its domain or name. This is useful for marketing teams, sales professionals, and competitive analysts who want to gather insights about a company's advertising strategies and campaigns.

Practical examples include:

  • Finding all B2B ads run by a competitor using their company domain.
  • Searching for ads associated with a company by its name when the domain is unknown.
  • Analyzing ad content and targeting to optimize your own campaigns.

Properties

Name Meaning
Search Method How to search for the company. Options: "By Company Domain" or "By Company Name".
Company Domain The domain of the company to search ads for (required if Search Method is "By Company Domain"). Example: microsoft.com
Company Name The name of the company to search ads for (required if Search Method is "By Company Name"). Example: Microsoft

Output

The node outputs JSON data representing the search results of B2B advertisements related to the specified company. Each item in the output array corresponds to an individual ad or a set of ads returned by the API.

The exact structure depends on the external API response but typically includes details such as:

  • Ad identifiers
  • Ad content and creatives
  • Platforms where ads are running
  • Targeting information
  • Dates and performance metrics (if available)

No binary data output is produced by this operation.

Dependencies

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

Troubleshooting

  • Common issues:

    • Missing or invalid API key credential will cause authentication failures.
    • Providing both company domain and company name incorrectly (only one should be provided based on the selected search method).
    • Network connectivity issues may prevent reaching the external API.

  • Error messages:

    • "Too many emails provided" — Not applicable here but indicates input limits in other operations.
    • Generic API errors may return messages from the external service; ensure the company domain or name is valid and correctly formatted.
    • If the node throws errors related to missing parameters, verify that required fields (company_domain or company_name) are filled according to the chosen search method.

  • Resolution tips:

    • Double-check the API key credential setup.
    • Confirm the input values match the expected format.
    • Use the "Continue On Fail" option in n8n to handle partial failures gracefully.

Links and References

Discussion