Notificações Inteligentes icon

Notificações Inteligentes

NI Integration
Join our community

Actions48

Overview

The "Event" resource with the "Waiting Payment" operation in this node is designed to send event data related to orders that are awaiting payment. This is useful for tracking and managing customer orders that have not yet been paid, enabling workflows such as sending reminders, updating order statuses, or triggering follow-up actions based on payment status.

Typical use cases include:

  • E-commerce platforms notifying internal systems or third-party services about orders pending payment.
  • Automating customer notifications or alerts when an order is waiting for payment.
  • Integrating with payment gateways or CRM systems to update order/payment statuses dynamically.

For example, when a customer places an order but has not completed payment, this node can dispatch an event containing detailed order and customer information, including payment method specifics like PIX (a Brazilian instant payment system), allowing downstream processes to handle the waiting payment scenario appropriately.

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
Tax ID (CPF/CNPJ) Customer’s tax document identifier (CPF or CNPJ)
IP Address Customer’s IP address
Products List of products in the order; each product includes: Product Name (string), Quantity (number), Value (number) (required)
Order ID Unique identifier of the order (required)
Order Products Total Value Sum of the values of all products in the order (required)
Order Total Value Total amount of the order including discounts (required)
Discount Total discount applied to the order (required)
Status Current order status description for enrichment
Payment Method Payment type for the order; options: Credit Card, Bank Deposit, PIX (default: Bank Deposit)
BACEN Code BACEN code required for PIX payments (required if payment method is PIX)
PIX Due Date Due date/time for PIX payment in UTC+0 timezone (required if payment method is PIX)
QR Code QR code string for PIX payment (required if payment method is PIX)
PIX Payment URL URL for PIX payment (required if payment method is PIX)
PIX Amount Amount for PIX payment (required if payment method is PIX)

Output

The node outputs JSON data representing the event sent regarding the waiting payment order. The output JSON contains structured information about the customer, order details, products, payment method, and any relevant metadata.

No binary data output is indicated.

Dependencies

  • Requires an API key credential to authenticate requests to the external service at https://api.notificacoesinteligentes.com.
  • The node uses HTTP requests with authentication to communicate with this external API.
  • No additional environment variables or configurations are explicitly required beyond the API key credential setup.

Troubleshooting

  • Common Issues:

    • Missing required fields such as customer first name, phone, order ID, or product details may cause the event dispatch to fail.
    • Incorrect formatting of dates (e.g., PIX due date) could lead to errors or rejected events.
    • Using the PIX payment method without providing all required PIX-specific fields (BACEN code, QR code, payment URL, due date, amount) will likely cause validation errors.
    • Network timeouts or authentication failures when connecting to the external API.

  • Error Messages:

    • Authentication errors typically indicate invalid or missing API credentials; verify the API key configuration.
    • Validation errors usually specify which required property is missing or malformed; ensure all required properties are correctly set.
    • Timeout or connection errors suggest network issues or API endpoint unavailability; retry or check connectivity.

Links and References

Note: The above summary is based solely on static analysis of the provided source code and property definitions.

Discussion