Notificações InteligentesInstall

Overview

This node operation "List Leads in List" retrieves leads from a specified lead list by its unique identifier. It allows filtering the leads by name, phone, or email and optionally includes related data such as other lists or the source of the list. This is useful for scenarios where you want to manage or analyze leads grouped in specific lists, such as marketing campaigns, sales pipelines, or customer segmentation.

Practical examples:

• Fetch all leads in a particular marketing campaign list to send targeted emails.
• Retrieve leads filtered by email domain to identify potential high-value customers.
• Include relationship data to understand which other lists a lead belongs to or the origin of the list.

Properties

Name	Meaning
List ID	Unique identifier of the lead list to retrieve leads from.
Include Relationships	Optional related data to include with each lead. Options: "Lists" (other lists the lead belongs to), "List Source" (origin/source of the list).
Lead Name	Filter leads by their name (partial or full match).
Lead Phone	Filter leads by their phone number.
Lead Email	Filter leads by their email address.

Output

The output contains a JSON array of lead objects retrieved from the specified list. Each lead object includes standard lead fields such as name, phone, and email. If the "Include Relationships" property is used, additional nested data about the lead's associated lists or the list source will be included.

No binary data output is indicated.

Dependencies

• Requires an API key credential to authenticate requests to the external service at https://api.notificacoesinteligentes.com.
• The node uses HTTP requests with authentication to fetch data from the external API.
• Proper network connectivity and valid credentials are necessary for successful execution.

Troubleshooting

• Common issues:
  • Invalid or missing List ID will result in errors or empty results.
  • Incorrect or expired API credentials will cause authentication failures.
  • Network timeouts or connectivity problems may prevent data retrieval.
• Error messages:
  • Authentication errors typically indicate invalid API keys; verify and update credentials.
  • "List not found" or similar errors suggest the provided List ID does not exist; confirm the ID.
  • Timeout errors may require increasing timeout settings or checking network status.

Links and References

• API Documentation (assumed base URL for reference)
• n8n HTTP Request Node documentation for configuring authenticated API calls.