mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

The "Leadfyndr List Unlocked Leads" operation in the Lead Fyndr resource allows users to retrieve a filtered list of unlocked sales leads from the Lead Fyndr platform. This node is useful for sales and marketing teams who want to programmatically access potential customer leads based on various criteria such as company size, sales volume, technologies used, location, and performance metrics.

Typical use cases include:

  • Automatically fetching new leads that match specific business criteria.
  • Integrating lead data into CRM or marketing automation workflows.
  • Filtering leads by geographic location or technology stack to target niche markets.
  • Sorting and paginating large lead datasets for efficient processing.

Properties

Name Meaning
Customer Id The unique identifier of the customer requesting the leads (required).
Potential Range Min Minimum inclusive value of the lead's potential score.
Potential Range Max Maximum inclusive value of the lead's potential score.
Employee Count Min Minimum inclusive number of employees at the lead's company.
Employee Count Max Maximum inclusive number of employees at the lead's company.
Sales Volume Min Minimum inclusive sales volume of the lead's company.
Sales Volume Max Maximum inclusive sales volume of the lead's company.
Technologies JSON array of technologies to filter leads by (e.g., programming languages, platforms).
Business Fields JSON array of business fields or industries to filter leads by.
Location City City name to filter leads by geographic location.
Location Post Code Postal code to filter leads by geographic location.
Location Radius In Km Radius in kilometers around the specified city or postal code to include leads.
Basic Time To First Byte Ms Min Minimum inclusive value of website time to first byte metric (performance indicator).
Basic Time To First Byte Ms Max Maximum inclusive value of website time to first byte metric.
Basic Desktop Performance Min Minimum inclusive desktop performance score from Lighthouse metrics.
Basic Desktop Performance Max Maximum inclusive desktop performance score from Lighthouse metrics.
Basic Mobile Performance Min Minimum inclusive mobile performance score from Lighthouse metrics.
Basic Mobile Performance Max Maximum inclusive mobile performance score from Lighthouse metrics.
Reserved Boolean flag to filter only leads reserved for this customer (true or false).
Limit Maximum number of leads to return in the response (pagination limit).
Skip Number of items to skip before starting to collect results (for pagination).
Page Page number to display; overlaps with skip. If both set, skip takes precedence.
Sort Field to sort the results by: "Potential", "Relevance", or "Company".
Order Sort order direction: ascending ("asc") or descending ("desc").

Output

The node outputs a JSON array of lead objects matching the specified filters. Each lead object typically contains detailed information about the lead company, including but not limited to:

  • Company details (name, industry, size)
  • Potential score
  • Employee count
  • Sales volume
  • Technologies used
  • Location information
  • Website performance metrics (time to first byte, desktop/mobile performance scores)
  • Reservation status for the customer

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Lead Fyndr service.
  • The node sends HTTP requests to the Lead Fyndr API endpoint.
  • Proper configuration of the API authentication token in n8n credentials is necessary.
  • Network connectivity to the Lead Fyndr API server.

Troubleshooting

  • Missing or invalid Customer Id: The operation requires a valid customer ID; ensure it is provided and correct.
  • API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Invalid filter values: Numeric ranges should be logical (min ≤ max); otherwise, the API may return errors or empty results.
  • Pagination issues: Using incompatible values for skip and page can cause unexpected results; prefer using one consistently.
  • Empty results: If no leads are returned, check filter criteria for overly restrictive conditions.
  • Network or API downtime: Temporary failures connecting to the Lead Fyndr API will cause errors; retry after some time.

Links and References

Discussion