Notificações Inteligentes

Overview

This node operation "Buscar Todos Os Leads" (Search All Leads) is designed to retrieve multiple lead records from a data source, applying optional filters and including related entities as needed. It is useful in scenarios where you want to fetch a list of leads based on specific criteria such as name, phone number, email, or tag ID. Additionally, it allows including related information like lists, tags, users, or the source of lists to enrich the lead data.

Practical examples:

• Fetch all leads with a specific tag to run targeted marketing campaigns.
• Retrieve leads filtered by phone number or email for follow-up communications.
• Include related user or tag information to better understand lead context.

Properties

Name	Meaning
Filtros	Collection of filters to narrow down the leads retrieved. Options include:
- Nome	Filter leads by their name.
- Telefone	Filter leads by their phone number.
- Email	Filter leads by their email address.
- Tag ID	Filter leads by the ID of an associated tag.
Incluir Relacionamentos	Multi-select option to include related entities in the response. Options are:
- Listas	Include lists associated with the leads.
- Fonte Das Listas	Include the source information of the lists.
- Tags	Include tags associated with the leads.
- Usuários	Include users related to the leads.

Output

The output JSON will contain an array of lead objects matching the specified filters. Each lead object may include additional nested data depending on the selected relationships (lists, tags, users, list sources). The structure typically includes lead details such as name, phone, email, and any related entities requested.

If binary data is supported (not indicated in the provided code), it would represent attachments or files related to leads, but this is not evident here.

Dependencies

• Requires access to the external service or API that manages lead data.
• Needs appropriate API authentication credentials configured in n8n to authorize requests.
• No other explicit dependencies are visible in the provided source snippet.

Troubleshooting

• Common issues might include incorrect filter values leading to empty results.
• Missing or invalid API credentials can cause authentication errors.
• Selecting relationships that do not exist or are unsupported by the backend may result in errors or incomplete data.
• Network connectivity problems could prevent successful data retrieval.

To resolve these:

• Verify filter inputs for correctness.
• Ensure API credentials are properly set up and valid.
• Confirm that requested relationships are supported by the data source.
• Check network status and retry if necessary.

Links and References

• Refer to the API documentation of the lead management system for detailed filter and relationship options.
• n8n documentation on creating and configuring nodes: https://docs.n8n.io/
• General best practices for filtering and paginating API data.