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 operation "Criar Lead" (Create Lead) is designed to add a new lead record into a system. It is useful in scenarios where you want to capture potential customer information such as name, phone number, and email for marketing, sales follow-up, or CRM purposes. For example, after collecting user data from a web form or an event registration, this node can be used to create a lead entry automatically.
Properties
| Name | Meaning |
|---|---|
| Nome | The full name of the lead (required). |
| Telefone | The phone number of the lead, including area code (DDD) (required). |
| The email address of the lead (required). | |
| Notas | Additional notes or observations about the lead. |
| Variáveis Customizadas | Custom variables to assign additional attributes to the lead. Each variable has: - Slug: identifier of the custom variable - Valor: value to assign to that variable |
| Tags | Tags to add to the lead for categorization or filtering. Multiple tags can be added. |
Output
The node outputs JSON data representing the created lead. This typically includes the lead's details such as name, phone, email, any custom variables set, and tags assigned. If the system supports it, the output may also include identifiers or status confirming successful creation.
No binary data output is indicated.
Dependencies
- Requires access to the target system's API or database where leads are stored.
- Needs appropriate authentication credentials (e.g., an API key or token) configured in n8n to authorize lead creation.
- No other external dependencies are evident from the provided source.
Troubleshooting
- Missing Required Fields: Errors may occur if required fields like "Nome", "Telefone", or "Email" are not provided. Ensure these inputs are filled.
- Invalid Phone or Email Format: The system might reject improperly formatted phone numbers or emails. Validate input formats before execution.
- Authentication Failures: If API credentials are missing or invalid, the node will fail to create leads. Verify credential configuration.
- API Limitations or Quotas: Creating too many leads in a short time might hit rate limits; check API usage policies.
- Custom Variables Misconfiguration: Incorrect slugs or values in custom variables could cause errors or unexpected behavior.
Links and References
- Refer to your CRM or lead management system API documentation for exact field requirements and supported custom variables.
- General best practices for lead data collection and validation can be found in marketing automation resources.