Linqer CRM icon

Linqer CRM

Integração com a API do CRM Linqer

Actions32

Overview

The node integrates with the Linqer CRM API to manage custom fields within the CRM system. Specifically, for the "Campos Personalizados" (Custom Fields) resource and the "Atualizar" (Update) operation, it updates an existing custom field's properties such as its name, type, whether it is required, locked, or a system field.

This node is useful in scenarios where you need to programmatically modify metadata about custom fields in your CRM, for example:

  • Changing the label or type of a custom field after initial creation.
  • Updating field constraints like making a field mandatory or locking it from further edits.
  • Managing system vs user-defined custom fields dynamically.

Practical example: You have a custom field named "Customer Priority" of type text, and you want to update it to be a required field and lock it to prevent users from changing it accidentally.

Properties

Name Meaning
Nome The name of the custom field to update.
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 (true/false).
Bloqueado Whether the custom field is locked for editing (true/false).
Campo do Sistema Whether the field is a system field (true/false).
ID do Campo The unique identifier of the custom field to update.

Output

The output JSON contains the response from the Linqer CRM API after updating the custom field. This typically includes the updated custom field's details such as its ID, name, type, and status flags (required, locked, system).

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Linqer CRM API.
  • The node uses HTTP methods (PUT) to communicate with the endpoint /v1/custom-fields/public/{fieldId}.
  • The base URL for the API is configured via the credential settings.
  • No additional external dependencies are needed beyond the configured API authentication.

Troubleshooting

  • Common issues:

    • Invalid or missing fieldId will cause the API to reject the request.
    • Providing invalid values for the type property may result in errors.
    • Attempting to update a system-locked field without proper permissions might fail.
    • Network or authentication failures can cause request errors.

  • Error messages:

    • "Operação \"update\" não suportada para campos personalizados": Indicates that the operation requested is not supported; ensure the operation parameter is correctly set to "update".
    • API error responses related to authorization or validation will be passed through; check the API key validity and input parameters.

  • Resolution tips:

    • Verify that the fieldId corresponds to an existing custom field.
    • Ensure all required properties are provided and valid.
    • Confirm the API key credential is correctly configured and has necessary permissions.
    • Use the node's "Continue On Fail" option to handle individual item errors gracefully.

Links and References

Discussion