Notificações Inteligentes icon

Notificações Inteligentes

NI Integration
Join our community

Actions48

Overview

The node operation "Remove Leads From List" is designed to remove specified leads from a particular lead list by their unique identifiers. This is useful in scenarios where you want to manage your marketing or sales contact lists dynamically, for example, removing contacts who have unsubscribed, bounced, or are no longer relevant for a campaign.

Practical examples:

  • Cleaning up a mailing list by removing leads who opted out.
  • Managing segmented lists by removing leads that no longer fit certain criteria.
  • Automating lead lifecycle management by removing leads after a status change.

Properties

Name Meaning
List ID Unique identifier of the lead list from which leads will be removed.
Leads (IDs) Comma-separated string of lead IDs to remove from the list (e.g., "17, 25, 33").

Output

The node outputs JSON data representing the result of the removal operation. Typically, this would include confirmation of which leads were successfully removed or any errors encountered during the process.

If the node supports binary data output, it would generally relate to attachments or files associated with the leads or lists, but based on the provided code and properties, this node focuses on JSON responses only.

Dependencies

  • Requires an API key or authentication token configured in n8n to access the external service at https://api.notificacoesinteligentes.com.
  • The node uses HTTP requests to interact with the external API endpoints for managing lead lists.
  • Network connectivity to the external API endpoint is necessary.

Troubleshooting

  • Invalid List ID: If the provided List ID does not exist or is incorrect, the API may return an error indicating the list was not found. Verify the List ID before running the node.
  • Malformed Lead IDs: Lead IDs must be positive integers separated by commas. Invalid formats may cause the request to fail or ignore some IDs.
  • Authentication Errors: Ensure that the API credentials are correctly set up in n8n; otherwise, the node will fail to authenticate with the external service.
  • API Rate Limits or Timeouts: The external API might limit the number of requests or have timeouts. If you encounter such errors, consider adding delays or retries.
  • Empty Removal Result: If none of the specified leads are removed, verify that the leads actually belong to the list.

Links and References

Discussion