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 "Access Granted Event" (Evento de Acesso Concedido) within a system that tracks customer-related events. This event typically records when a customer gains access to a members-only area or service, capturing relevant personal and access details.
This node would be beneficial in scenarios such as:
- Membership platforms where tracking user access events is important.
- Systems that require logging of user login or first-time access for auditing or marketing purposes.
- Integrations where customer data and access events need to be synchronized with external CRMs or analytics tools.
For example, when a customer logs into a membership site for the first time, this node can create an event recording their login credentials, access URLs, and personal information, enabling downstream workflows like sending welcome emails or updating user status.
Properties
| Name | Meaning |
|---|---|
| ID | The identifier of the existing integration (not used directly in this operation). |
| Primeiro Nome | Customer's first name (required). |
| Sobrenome | Customer's last name (optional). |
| Telefone | Customer's phone number including country code and area code (required). |
| Data De Nascimento | Customer's birthdate in format YYYY-MM-DD (optional). |
| Moeda | Currency type used by the customer (e.g., BRL, USD, GBP) (optional). |
| Gênero | Customer's gender (optional). |
| Customer's email address (optional). | |
| CPF/CNPJ | Customer's document number (CPF or CNPJ) (optional). |
| IP | Customer's IP address (optional). |
| Produtos | Collection of product metadata related to the event (required). Each product includes: |
| - Nome Do Produto: Product name (required) | |
| - Quantidade Do Produto: Quantity of the product (required) | |
| - Valor Do Produto: Value/price of the product (required) | |
| URL Da Página De Membros | URL for redirecting to the members page (required). |
| URL De Primeiro Acesso Do Cliente | URL for the customer's first access to create a password (required). |
| Login | User login on the members page (required). |
| Senha | User password on the members page (required, input masked). |
Output
The node outputs JSON data representing the created access event. This JSON typically contains confirmation details about the event creation, including any identifiers or status messages returned by the underlying API or system.
If binary data were involved (not indicated here), it would represent files or attachments related to the event, but this node focuses on structured JSON event data only.
Dependencies
- Requires an API key or authentication token configured in n8n to connect to the external system managing these events.
- The node depends on an external service or API endpoint that accepts event creation requests with customer and product data.
- Proper network connectivity and permissions are necessary to send data to the target system.
Troubleshooting
- Missing Required Fields: Errors may occur if required fields like first name, phone, products, member URL, login, or password are missing. Ensure all mandatory inputs are provided.
- Invalid Data Formats: Date fields should follow the specified format (YYYY-MM-DD). Incorrect formats might cause validation errors.
- Authentication Failures: If the API key or credentials are invalid or expired, the node will fail to create the event. Verify credential configuration.
- Network Issues: Connectivity problems can prevent event creation. Check firewall settings and API endpoint availability.
- Product Data Issues: The products collection must include at least one product with valid name, quantity, and value. Empty or malformed product data will cause errors.
Links and References
- No direct links available from the source code. For further details, consult the documentation of the external system or API managing the access events.
- General best practices for n8n custom nodes: https://docs.n8n.io/integrations/creating-nodes/