Notificações Inteligentes

Overview

This node is designed to interact with a leads list resource, specifically to list leads within a given list. It allows users to retrieve leads from a specified list by providing the unique identifier of that list. Additionally, it supports filtering the leads by name, phone number, or email address, and optionally including related data such as associated lists or the source of the lists.

Common scenarios where this node would be beneficial include:

• Extracting all leads from a marketing or sales list for further processing or analysis.
• Filtering leads within a list based on specific criteria like name or contact information.
• Enriching lead data by including related entities such as the lists they belong to or their sources.

Practical example:

• A marketing automation workflow that fetches all leads from a particular campaign list, filters them by email domain, and then sends targeted emails only to those filtered leads.

Properties

Name	Meaning
ID Da Lista	The unique identifier of the list from which to retrieve leads.
Incluir Relacionamentos	Additional parameters to include relationships of the leads in the list. Options: "Listas", "Fonte Das Listas".
Filtrar Leads Da Lista Por:	Filters to search for specific leads within the list. Includes: "Nome Do Lead" (filter by lead name), "Telefone Do Lead" (filter by phone number), "Email Do Lead" (filter by email address).

Output

The output JSON contains the list of leads retrieved from the specified list. Each lead object may include standard lead properties such as name, phone, and email, depending on the data available and any applied filters.

If the option to include relationships is selected, the output may also contain nested objects representing related lists or the source of the lists associated with each lead.

No binary data output is indicated.

Dependencies

• Requires access to an external service or API that manages leads and lists.
• An API key or authentication token is necessary to authorize requests to this service.
• Proper configuration of credentials within n8n is required to enable communication with the external leads management system.

Troubleshooting

• Common issues:

  • Providing an invalid or empty list ID will result in failure to retrieve leads.
  • Incorrect filter values might return no results if no leads match the criteria.
  • Missing or invalid API credentials will cause authentication errors.

• Error messages and resolutions:

  • "List not found" — Verify that the provided list ID is correct and exists in the external system.
  • "Authentication failed" — Check that the API key or authentication token is correctly configured and valid.
  • "No leads found" — Adjust or remove filters to ensure there are matching leads in the list.

Links and References

• Refer to the external leads management system's API documentation for details on list and lead retrieval endpoints.
• n8n documentation on setting up API credentials and using HTTP request nodes for custom integrations.