Actions32
- Contatos Actions
- Oportunidades Actions
- Tarefas Actions
- Produtos Actions
- Funis Actions
- Campos Personalizados Actions
- Notas Actions
- Anexos Actions
- Propostas Actions
- Webhooks Actions
Overview
This node integrates with the Linqer CRM API to manage custom fields within the CRM system. Specifically, the "Criar" (Create) operation under the "Campos Personalizados" (Custom Fields) resource allows users to create new custom fields in their CRM instance.
Use cases for this node include:
- Extending the CRM data model by adding new fields tailored to specific business needs.
- Automating the creation of custom fields as part of a workflow that sets up or updates CRM configurations.
- Ensuring consistent field definitions across multiple CRM accounts or environments.
For example, you might use this node to add a new mandatory text field called "Customer Feedback" or a boolean field "Is VIP" to track special customers.
Properties
| Name | Meaning |
|---|---|
| Nome | The name of the custom field to be created. |
| Tipo | The type of the custom field. Options: Texto (text), Número (number), Data (date), Booleano (boolean), Lista (select). |
| Obrigatório | Whether the custom field is required (mandatory) or not. |
| Bloqueado | Whether the custom field is locked for editing after creation. |
| Campo do Sistema | Indicates if the field is a system field (usually reserved or predefined by the system). |
Output
The node outputs JSON data representing the newly created custom field as returned by the Linqer CRM API. This typically includes details such as the field's unique identifier, name, type, and other metadata confirming the creation.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Linqer CRM API.
- The node expects the API URL and authentication token to be configured in the credential settings.
- Network access to the Linqer CRM API endpoint is necessary.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing invalid or incomplete property values (e.g., empty name or unsupported type) may result in API errors.
- Attempting to create a custom field with a name that already exists could lead to conflicts.
Error Messages:
"Operação "create" não suportada para campos personalizados": This indicates an unsupported operation was requested; ensure the operation parameter is set correctly.- HTTP errors from the API (e.g., 400 Bad Request) usually mean input validation failed; verify all required properties are correctly set.
Resolution Tips:
- Double-check API credentials and permissions.
- Validate all input parameters before execution.
- Review API documentation for constraints on custom field creation.
Links and References
- Linqer CRM API Documentation (hypothetical link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for error handling and authentication.