Notificações Inteligentes

Overview

The node is designed to create an "Access Granted Event" within a system that tracks customer interactions and events. This event typically records when a customer gains access to a members-only area or service, capturing relevant user details and product information associated with the access.

This node is beneficial in scenarios such as:

• Membership platforms where tracking user access events is critical.
• E-commerce or subscription services that want to log when customers access exclusive content or areas.
• Marketing automation workflows that trigger follow-up actions based on access events.

For example, when a customer logs into a members-only portal for the first time, this node can be used to record that event along with customer details like name, email, and products they have access to.

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).
Email	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. 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 for the members page (required).
Senha	User password for the members page (required, masked input).

Output

The node outputs JSON data representing the created access event. This output typically includes confirmation details about the event creation and may echo back the submitted customer and product information. There is no indication that binary data is produced by this node.

Dependencies

• Requires an API key or authentication token configured in n8n to connect to the external service handling these events.
• The node depends on an external service endpoint that accepts event creation requests with customer and product data.
• Proper configuration of URLs for member pages and first access is necessary for correct event processing.

Troubleshooting

• Missing Required Fields: Errors may occur if required fields such as 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 may cause failures.
• Authentication Failures: If the API key or credentials are not set up correctly, the node will fail to authenticate with the external service.
• Network Issues: Connectivity problems to the external API endpoint can cause timeouts or errors.
• Product Data Validation: Each product must include name, quantity, and value; missing any of these may result in errors.

To resolve common errors:

• Double-check all required properties are filled.
• Validate date and numeric inputs.
• Confirm API credentials and network connectivity.
• Review error messages returned from the external service for specific guidance.

Links and References

• No direct links available from the source code.
• For best practices, refer to the documentation of the external service managing access events.
• General n8n documentation on creating custom nodes and handling fixed collections: https://docs.n8n.io/creating-nodes/