Actions45
- Evento Actions
- Criar Evento De Acesso Concedido
- Criar Evento De Aguardando Pagamento
- Criar Evento De Boleto Impresso
- Criar Evento De Carrinho Abandonado
- Criar Evento De Nota Nps
- Criar Evento De Pacote Aguardando Retirada
- Criar Evento De Pacote Saiu Para Entrega
- Criar Evento De Pedido Cancelado
- Criar Evento De Pedido Despachado
- Criar Evento De Pedido Entregue
- Criar Evento De Pedido Estornado
- Criar Evento De Pedido Pago
- Criar Evento De Pedido Processando
- Criar Evento De Pesquisa Nps
- Criar Evento De Progresso De Envio
- Criar Evento De Redefinicao De Senha
- Gerenciamento Da Conta Actions
- Grupo De Variável Customizada Actions
- Integração Actions
- Lead Actions
- Lista De Lead Actions
- Variável Customizada Actions
Overview
The node is designed to create an "Order Dispatched" event within an integration system. It collects detailed customer and order information, including personal data, order details, product metadata, delivery parameters, and address information. This event can be used to notify other systems or workflows that an order has been dispatched, enabling automated follow-up actions such as sending notifications to customers, updating order statuses in CRM or ERP systems, or triggering logistics processes.
Practical examples:
- E-commerce platforms can use this node to signal when a customer's order has left the warehouse.
- Customer support systems can automatically log dispatched orders for tracking and service purposes.
- Marketing automation tools can trigger shipment confirmation emails or SMS messages based on this event.
Properties
| Name | Meaning |
|---|---|
| ID | The ID of the existing integration |
| Primeiro Nome (first_name) | Customer's first name |
| Sobrenome (last_name) | Customer's last name |
| Telefone (phone) | Customer's phone number including country code and area code (DDD) |
| Data De Nascimento (birthdate) | Customer's birth date in format YYYY-MM-DD |
| Moeda (currency) | Currency type used by the customer (e.g., BRL, USD, GBP) |
| Gênero (gender) | Customer's gender |
| Customer's email address | |
| CPF/CNPJ | Customer's document number (CPF or CNPJ) |
| IP | Customer's IP address |
| Produtos (products) | List of products in the order, each with: |
| - Nome Do Produto (productname): Product name | |
| - Quantidade Do Produto (productquantity): Quantity of the product | |
| - Valor Do Produto (productvalue): Value of the product | |
| ID Do Pedido (orderid) | Order ID |
| Valor Somado Dos Produtos Do Pedido (products_total) | Sum of the values of all products in the order |
| Valor Do Pedido Total (total) | Total value of the order |
| Desconto (discount) | Total discount applied to the order |
| Status | Current status description of the order for enrichment |
| Parâmetros Adicionais (addressparameter) | Customer address details including city, complement, country, neighborhood, number, postal code, state, street |
| Parâmetros Adicionais (deliveryparameter) | Delivery details including tracking code, estimated delivery date, description, message, tracking URL, freight value |
Output
The node outputs JSON data representing the created "Order Dispatched" event. This output includes all the input properties structured into a single event object, which can be used downstream in workflows for further processing or logging.
If the node supports binary data output, it is not indicated in the provided source or property definitions.
Dependencies
- Requires an API key or authentication token to connect to the external integration system where the event will be created.
- The node depends on the integration platform's configuration to handle event creation.
- No additional external libraries or services are explicitly required beyond the integration API.
Troubleshooting
- Missing Required Fields: Ensure all required fields such as
ID,first_name,phone,products,orderid,products_total,total, anddiscountare provided; missing these may cause errors. - Invalid Date Formats: Dates like
birthdateandorderdatemust follow the specified format (YYYY-MM-DD). Incorrect formats may lead to rejection by the API. - Incorrect Currency Codes: Use standard currency codes (e.g., BRL, USD, GBP) to avoid validation errors.
- API Authentication Errors: Verify that the API key or authentication token is correctly configured and has sufficient permissions.
- Network Issues: Connectivity problems with the external integration endpoint can cause failures; check network settings and endpoint availability.
Links and References
- Refer to your integration platform's API documentation for event creation specifics.
- Standard ISO 4217 currency codes: https://www.iso.org/iso-4217-currency-codes.html
- Date format reference: https://en.wikipedia.org/wiki/ISO_8601