Gestor Clientes Max - Cliente icon

Gestor Clientes Max - Cliente

Gerenciar clientes: criar, buscar, atualizar e deletar clientes via API. Use para operações relacionadas a cadastro de clientes.
Join our community

Actions4

Overview

This node, "Gestor Clientes Max - Cliente," manages client records through an external API. It supports creating, retrieving, updating, and deleting client data. The "Update" operation specifically allows modifying existing client information by specifying the client ID and new values for various fields.

Typical use cases include automating client data management in CRM workflows, synchronizing client details between systems, or updating client profiles based on external triggers. For example, when a client's contact information changes, this node can update the record automatically to keep databases consistent.

Properties

Name Meaning
Client ID The unique identifier of the client to update (required).
User ID Identifier of the user performing the update; mandatory for Super Admin users.
Nome Client's name (required).
Email Client's email address.
Telefone Client's phone number.
CPF Client's CPF (Brazilian individual taxpayer registry identification).
Data de Nascimento Client's birth date in YYYY-MM-DD format.
Endereço Full address of the client.
Preço da Consulta Consultation price in Brazilian reais (number).
Status de Pagamento Payment status with options: "A Pagar" (To Pay), "Pago" (Paid), "Cancelado" (Cancelled).
Observações Additional notes about the client (multi-line text).

Output

The node outputs JSON objects representing the updated client data returned from the API after the update operation. This typically includes all client fields as stored in the external system, reflecting the new state post-update.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the Gestor Clientes Max API.
  • The node uses HTTP methods (PUT) to communicate with the API endpoint /clients/{clientId}.
  • Proper configuration of the API base URL and credentials within n8n is necessary.

Troubleshooting

  • Common issues:
    • Missing or incorrect Client ID will cause the update to fail.
    • Invalid or expired API key will result in authentication errors.
    • Providing invalid date formats or unsupported field values may cause API validation errors.
  • Error messages:
    • "Unknown operation: update" indicates the operation parameter was not recognized; ensure it is set correctly.
    • HTTP errors from the API (e.g., 400 Bad Request, 401 Unauthorized) should be checked for detailed messages.
  • Resolutions:
    • Verify that all required fields are provided and correctly formatted.
    • Confirm API credentials are valid and have sufficient permissions.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion