Notificações Inteligentes icon

Notificações Inteligentes

NI Integration

Overview

This node is designed to send a "Password Reset Event" to an external notification or event tracking service. It captures customer details and the URL for resetting the password, then transmits this information as an event. This is useful in scenarios where you want to track password reset requests for security auditing, customer support, or triggering follow-up actions such as sending confirmation emails or alerts.

Practical examples include:

  • Automatically logging password reset attempts in a CRM or analytics platform.
  • Triggering workflows that notify support teams when users reset their passwords.
  • Integrating with marketing tools to analyze user behavior related to account recovery.

Properties

Name Meaning
First Name Customer’s first name (required)
Last Name Customer’s last name
Phone Customer phone number including country and area code (required)
Birth Date Customer’s birth date in format Year-Month-Day (e.g., 2001-08-20)
Currency Currency used by the customer (e.g., BRL, USD, GBP)
Gender Customer’s gender
Email Customer’s email address
Tax ID (CPF/CNPJ) Customer’s tax document identifier
IP Address Customer’s IP address
Password Reset URL Link to reset the password (required)

Output

The node outputs JSON data representing the result of sending the password reset event to the external service. The exact structure depends on the API response but typically includes confirmation of event receipt or error details.

The node does not output binary data.

Dependencies

  • Requires access to an external API at https://api.notificacoesinteligentes.com to send event data.
  • Needs an API authentication token or key configured in n8n credentials to authorize HTTP requests.
  • The node uses HTTP requests with authentication to communicate with the external service.

Troubleshooting

  • Common issues:

    • Missing required fields such as First Name, Phone, or Password Reset URL will cause errors.
    • Network connectivity problems or incorrect API credentials will prevent successful event submission.
    • API rate limits or timeouts may cause request failures.
  • Error messages:

    • Authentication errors indicate invalid or missing API credentials; verify and update credentials.
    • Validation errors from the API usually mean required fields are missing or incorrectly formatted; ensure all required properties are provided correctly.
    • Timeout errors suggest network issues or slow API response; retry or check connectivity.

Links and References


Note: The summary is based on static analysis of the provided source and property definitions without runtime execution.

Discussion