Notificações Inteligentes icon

Notificações Inteligentes

NI Integration
Join our community

Actions48

Overview

This node operation retrieves detailed information about a specific Lead by its unique identifier. It is useful in scenarios where you need to fetch the current state or attributes of a particular lead from your system, such as for display in dashboards, further processing, or integration with other workflows.

For example, you might use this operation to:

  • Fetch a lead's details before updating their information.
  • Retrieve associated tags or lists linked to the lead for segmentation purposes.
  • Display lead data in a CRM or marketing automation tool integrated via n8n.

Properties

Name Meaning
Lead ID The unique identifier of the lead to retrieve.
Include Relationships Select which related entities to include in the response. Options: Lists, List Source, Tags
  • Lead ID is required and must be provided as a string.
  • Include Relationships is optional and allows including additional related data such as the lists the lead belongs to, the source of those lists, and any tags assigned to the lead.

Output

The output JSON contains the detailed information of the requested lead. This includes the lead's core attributes (such as name, email, status, etc.) and optionally the related entities specified in the "Include Relationships" property:

  • If "Lists" is selected, the output will include the lists the lead is part of.
  • If "List Source" is selected, the source information of those lists will be included.
  • If "Tags" is selected, the tags assigned to the lead will be part of the output.

No binary data output is indicated by the source code.

Dependencies

  • Requires an API key credential to authenticate requests against the external service at https://api.notificacoesinteligentes.com.
  • The node uses HTTP requests with authentication to communicate with the external API.
  • Network connectivity to the external API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Lead ID will result in errors or empty responses.
    • Network timeouts or connectivity issues may cause request failures.
    • Insufficient permissions or invalid API credentials can lead to authentication errors.

  • Error messages:

    • Authentication failure: Verify that the API key or authentication token is correctly configured.
    • Not found error: Confirm that the Lead ID exists in the system.
    • Timeout or network errors: Check internet connection and API availability.

Links and References

Discussion