Actions32
- Contatos Actions
- Oportunidades Actions
- Tarefas Actions
- Produtos Actions
- Funis Actions
- Campos Personalizados Actions
- Notas Actions
- Anexos Actions
- Propostas Actions
- Webhooks Actions
Overview
The node integrates with the Linqer CRM API to manage contacts. Specifically, for the "Contatos" resource and the "Criar" operation, it allows users to create new contact records in the Linqer CRM system. This is useful in scenarios where you want to automate adding new contacts from various sources (e.g., form submissions, lead generation tools) directly into your CRM without manual entry.
Practical examples include:
- Automatically creating a contact when a new lead fills out a web form.
- Syncing contacts from other systems or databases into Linqer CRM.
- Adding detailed contact information including social media profiles and tags for better segmentation and follow-up.
Properties
| Name | Meaning |
|---|---|
| Nome | The full name of the contact (required). |
| The email address of the contact. | |
| Telefone Principal | The primary phone number of the contact. |
| Telefone Secundário | A secondary phone number for the contact. |
| Tipo | The type of contact: either "Individual" or "Empresa" (Company). |
| Documento | The CPF or CNPJ document number of the contact (Brazilian individual/company tax IDs). |
| Tipo de Documento | The type of document provided: "CPF" or "CNPJ". |
| Endereço | The physical address of the contact. |
| Setor | The industry sector in which the contact operates. |
| Website | The contact's website URL. |
| Notas | Additional notes about the contact. |
| Tags | Comma-separated tags for categorizing the contact. |
| Ativo | Boolean indicating if the contact is active. |
| Redes Sociais | Social media profiles including Facebook, Instagram, LinkedIn, and Twitter URLs or handles. |
Output
The node outputs JSON data representing the created contact as returned by the Linqer CRM API. This typically includes all the contact details stored in the CRM along with any generated identifiers or metadata.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests against the Linqer CRM API.
- The node uses HTTP requests to the Linqer CRM public API endpoints.
- Proper configuration of the API base URL and authentication token is necessary in the credentials setup.
Troubleshooting
Common issues:
- Missing required fields such as "Nome" will cause the API to reject the request.
- Invalid document numbers or mismatched document types (CPF vs CNPJ) may result in validation errors.
- Network or authentication failures if the API key is incorrect or expired.
- Improperly formatted tags or social media URLs might be ignored or cause partial failures.
Error messages:
"Operação 'create' não suportada para contatos": Indicates an unsupported operation was requested; ensure the operation parameter is set correctly.- API response errors related to invalid input data will usually contain descriptive messages from the Linqer CRM API.
Resolutions:
- Verify all required properties are provided and correctly formatted.
- Check API credentials and permissions.
- Review the Linqer CRM API documentation for field constraints and validation rules.
Links and References
- Linqer CRM API Documentation (Assumed link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- General info on Brazilian CPF and CNPJ formats for document validation.
