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 its unique identifier and optionally filter the results based on lead attributes such as name, phone number, or email address. Additionally, it supports including related data about the lists or their sources.

Common scenarios for this node include:

• Extracting all leads from a marketing or sales list for further processing.
• Filtering leads within a list to target specific contacts based on their name, phone, or email.
• Enriching lead data by including relationships like the lists they belong to or the source of those lists.

Practical example:

• A marketing automation workflow that pulls leads from a particular campaign list, filters them by email domain, and then sends personalized emails.

Properties

Name	Meaning
ID Da Lista	The unique identifier of the list from which to retrieve leads.
Incluir Relacionamentos	Additional parameters to include related data of the leads in the list. Options: "Listas", "Fonte Das Listas".
Filtrar Leads Da Lista Por:	Filters to narrow down leads within the list by specific criteria:
- Nome Do Lead	Filter leads by their name within the list.
- Telefone Do Lead	Filter leads by their phone number within the list.
- Email Do Lead	Filter leads by their email address within the list.

Output

The node outputs JSON data representing the leads retrieved from the specified list. Each lead object typically contains details such as name, phone, email, and potentially additional related information if requested via the "Incluir Relacionamentos" property.

If binary data output is supported (not evident from the provided code), it would represent attachments or files associated with leads, but no such indication is present here.

Dependencies

• Requires access to an external service or API managing leads and lists.
• Needs proper authentication credentials (e.g., an API key or token) configured in n8n to authorize requests.
• The node depends on the underlying API's availability and correct configuration of the list identifier.

Troubleshooting

• Common issues:

  • Providing an invalid or empty list ID will result in failure to retrieve leads.
  • Incorrect filter values may return no results or unexpected data.
  • Missing or invalid authentication credentials can cause authorization errors.

• Error messages and resolutions:

  • "List not found" — Verify the list ID is correct and exists in the system.
  • "Unauthorized" or "Authentication failed" — Check that the API credentials are properly set up and valid.
  • "No leads found" — Adjust or remove filters to ensure matching leads exist.

Links and References

• Refer to the external API documentation managing leads and lists for detailed information on list IDs, filtering options, and relationship data.
• n8n documentation on creating and configuring API credentials for secure access.