Notificações Inteligentes icon

Notificações Inteligentes

NI Integration
Join our community

Actions48

Overview

This node operation "Add Lists to Lead" is designed to associate one or more lists with a specific lead in a marketing or CRM system. It allows users to add the lead to multiple lists by specifying their IDs, which can be useful for segmenting leads, targeting campaigns, or organizing contacts based on different criteria.

Common scenarios include:

  • Adding a lead to mailing lists for targeted email campaigns.
  • Associating a lead with interest groups or categories.
  • Managing lead segmentation dynamically based on user actions or data updates.

For example, if you have a lead identified by ID 123 and want to add them to lists with IDs 456 and 789, this operation will update the lead's record to reflect these associations.

Properties

Name Meaning
Lead ID The unique identifier of the lead to which lists will be added.
List ID(s) Comma-separated list of IDs representing the lists to associate with the lead (e.g., "1234, 5678").

Output

The node outputs JSON data representing the result of the operation. Typically, this would include confirmation that the specified lists were successfully associated with the lead, possibly returning the updated lead object or status information.

If the node supports binary data output, it would relate to any files or attachments linked to the lead or lists, but based on the provided code and properties, this operation focuses on JSON data only.

Dependencies

  • Requires an API key or authentication token to access the external service at https://api.notificacoesinteligentes.com.
  • The node uses HTTP requests to communicate with the external API endpoint.
  • Proper configuration of credentials and permissions in n8n is necessary to perform this operation.

Troubleshooting

  • Invalid Lead ID: If the lead ID does not exist or is incorrect, the API may return an error indicating the lead was not found. Verify the lead ID before running the node.
  • Invalid List IDs: Providing malformed or non-existent list IDs may cause the operation to fail or ignore those lists. Ensure list IDs are valid integers and exist in the system.
  • Authentication Errors: Missing or invalid API credentials will prevent the node from accessing the service. Check that the API key or authentication token is correctly configured.
  • Network Issues: Timeouts or connectivity problems with the external API can cause failures. Ensure stable internet connection and that the API endpoint is reachable.
  • Rate Limits: Excessive requests might trigger rate limiting on the API side. Implement retries or backoff strategies if needed.

Links and References

Discussion