mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

The "Leadfyndr List Leads" operation in the Lead Fyndr node allows users to retrieve a filtered list of leads based on various criteria such as potential value, employee count, sales volume, technologies used, business fields, location, and performance metrics. This node is useful for sales and marketing teams who want to target specific companies or leads that match detailed parameters, enabling more focused outreach and lead qualification.

Practical examples include:

  • Listing leads with a potential value between certain minimum and maximum thresholds.
  • Filtering companies by employee count or sales volume ranges.
  • Searching for leads using specific technologies or business fields.
  • Narrowing down leads within a geographic radius around a city or postal code.
  • Sorting results by relevance or potential, and controlling pagination through limit and skip/page parameters.

Properties

Name Meaning
Customer Id Identifier for the customer; required to specify which customer's leads to list.
Potential Range Min Minimum inclusive value of the lead's potential.
Potential Range Max Maximum inclusive value of the lead's potential.
Employee Count Min Minimum inclusive number of employees in the lead's company.
Employee Count Max Maximum inclusive number of employees in 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., ["React", "Node.js"]).
Business Fields JSON array of business fields to filter leads by (e.g., ["Finance", "Healthcare"]).
Location City City name to filter leads located in or near this city.
Location Post Code Postal code to filter leads located in or near this area.
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 for the time to first byte metric (performance indicator).
Basic Time To First Byte Ms Max Maximum inclusive value for the time to first byte metric.
Basic Desktop Performance Min Minimum inclusive desktop performance score (Lighthouse metric).
Basic Desktop Performance Max Maximum inclusive desktop performance score.
Basic Mobile Performance Min Minimum inclusive mobile performance score (Lighthouse metric).
Basic Mobile Performance Max Maximum inclusive mobile performance score.
Limit Maximum number of leads to return in the response (pagination control).
Skip Number of items to skip before starting to collect the result set (should be multiple of limit).
Page Page number to display; if both page and skip are set, skip takes precedence.
Sort Field to sort the results by: "Potential" or "Relevance".
Order Sort order direction: ascending ("asc") or descending ("desc").

Output

The node outputs a JSON array containing the list of leads matching the specified filters. Each item in the output array represents a lead with its associated data fields as returned by the Lead Fyndr API. The exact structure depends on the API response but typically includes details like company information, potential value, employee count, technologies, location, and performance metrics.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Lead Fyndr API.
  • An API key or authentication token credential must be configured in n8n to authorize requests.
  • Network access to the Lead Fyndr service endpoint is necessary.

Troubleshooting

  • Missing or invalid Customer Id: Since Customer Id is required, omitting it or providing an incorrect value will likely cause errors or empty responses.
  • Invalid filter values: Providing non-numeric values where numbers are expected (e.g., for min/max ranges) may cause request failures.
  • Pagination issues: Setting skip to a value not multiple of limit might lead to unexpected results or API errors.
  • API rate limits or authentication errors: Ensure the API key is valid and has sufficient permissions; check for error messages indicating authentication failure.
  • Empty results: If filters are too restrictive, no leads may be returned. Try broadening filter criteria.

Links and References

Discussion