Notificações InteligentesInstall

Overview

This node operation "Get All Lists" under the "Lead List" resource retrieves multiple lead lists from an external service. It allows users to fetch all available lead lists with optional filtering and inclusion of related data such as source information or lead counts. This is useful in scenarios where you want to manage, analyze, or display collections of leads grouped into lists, for example, syncing lead lists from a marketing platform or CRM into n8n workflows.

Practical examples:

• Fetching all lead lists that match a specific name or type filter.
• Including additional relationship data like the source of each list or the number of leads it contains.
• Appending extra properties such as whether the list has any leads.

Properties

Name	Meaning
Include Relationships	Relationships to include in the request. Options: Source, Lead Count
Additional Relationships	Properties to include in the response. Option: Has Leads
Filters	Set filters to search for specific lists. Contains: - Name: Filter lists by name - Type: Filter lists by type

Output

The output JSON will contain an array of lead lists matching the query parameters. Each list object may include additional related data depending on the selected "Include Relationships" and "Additional Relationships" options:

• Basic list details (e.g., id, name, type).
• If "Source" is included, source information about the list.
• If "Lead Count" is included, the count of leads in the list.
• If "Has Leads" is appended, a property indicating whether the list contains any leads.

No binary data output is indicated.

Dependencies

• Requires access to an external API at https://api.notificacoesinteligentes.com.
• Needs an API authentication token or key configured in n8n credentials to authorize requests.
• The node uses HTTP GET requests with query string parameters to retrieve data.

Troubleshooting

• Common issues:
  • Authentication failures due to missing or invalid API credentials.
  • Network timeouts or connectivity problems reaching the external API.
  • Incorrect filter values leading to empty results.
• Error messages:
  • Timeout errors if the API does not respond within the expected timeframe.
  • Authorization errors if the API key is invalid or missing.
• Resolutions:
  • Verify and configure correct API credentials in n8n.
  • Check network connectivity and API endpoint availability.
  • Ensure filter inputs are valid and correctly formatted.

Links and References

• API Documentation (assumed base URL for reference)
• n8n HTTP Request Node documentation for configuring authentication and query parameters.