Notificações InteligentesInstall

Overview

This node operation "Get All Leads" retrieves a list of leads from an external service. It allows users to filter the leads by various criteria such as name, phone number, email address, and tag ID. Additionally, it supports including related data like lists, list sources, and tags associated with each lead. This operation is useful for scenarios where you want to fetch and process multiple leads based on specific filters or enrich the lead data with related entities.

Practical examples:

• Fetch all leads with a specific email domain to run targeted marketing campaigns.
• Retrieve leads tagged with a particular campaign identifier to analyze campaign effectiveness.
• Include related lists and tags to get a comprehensive view of each lead's segmentation.

Properties

Name	Meaning
Filters	Set filters to search for specific leads. Options include:
	- Name: Filter leads by their name.
	- Phone: Filter leads by phone number.
	- Email: Filter leads by email address.
	- Tag ID: Filter leads by a specific tag identifier.
Include Relationships	Select which related entities to include in the response. Options are:
	- Lists: Include lists the lead belongs to.
	- List Source: Include the source information of the lists.
	- Tags: Include tags associated with the lead.

Output

The output JSON contains an array of lead objects matching the specified filters. Each lead object includes its core properties (such as name, phone, email) and, if requested, related entities like lists, list sources, and tags. The structure depends on the included relationships but generally provides detailed lead information suitable for further processing or analysis.

No binary data output is indicated for this operation.

Dependencies

• Requires access to an external API at https://api.notificacoesinteligentes.com.
• Needs an API authentication token or key configured within n8n to authorize requests.
• The node uses HTTP GET requests with query parameters to filter and include related data.

Troubleshooting

• Common issues:

  • Incorrect or missing API credentials will cause authentication failures.
  • Using invalid filter values may result in empty responses or errors.
  • Network timeouts or connectivity problems can interrupt data retrieval.

• Error messages:

  • Authentication errors typically indicate misconfigured or expired API keys; verify and update credentials.
  • Timeout errors suggest network issues or slow API responses; consider increasing timeout settings.
  • Empty results might mean no leads match the filters; try broadening filter criteria.

Links and References

• API Documentation (hypothetical link to the external service API docs)
• n8n HTTP Request Node documentation for configuring authentication and query parameters.