Gestor Clientes Max - Finanças
Overview
This node integrates with a financial management API to manage financial accounts. Specifically, the Update operation allows users to modify an existing financial account by providing its ID and updated details such as type, description, amount, due date, category, status, and optional related client or appointment IDs.
Common scenarios for this node include:
- Updating payment status or amount of an invoice or bill.
- Changing due dates or categories of financial entries.
- Adding notes or changing payment methods after initial creation.
Practical example: A business uses this node to update a payable account when a payment is received, marking it as "paid" and adding payment method details.
Properties
| Name | Meaning |
|---|---|
| Financial Account ID | The unique identifier of the financial account to update (required). |
| Tipo | Type of financial account: "Receita (A Receber)" (receivable) or "Despesa (A Pagar)" (payable). |
| Descrição | Description of the financial account (required). |
| Valor | Amount of the financial account in format like "150.00" (required). |
| Data de Vencimento | Due date of the financial account (required). |
| Categoria | Category of the financial account (required). |
| Status | Status of the financial account: "Pendente" (pending), "Pago" (paid), "Vencido" (overdue), or "Cancelado" (cancelled). |
| Cliente ID (Opcional) | Optional ID of the client associated with the financial account. |
| Agendamento ID (Opcional) | Optional ID of the appointment associated with the financial account. |
| Método de Pagamento | Payment method used: "Dinheiro" (cash), "PIX", "Cartão de Crédito" (credit card), "Cartão de Débito" (debit card), or "Transferência" (transfer). |
| Observações | Optional notes about the financial account. |
Output
The output JSON contains the updated financial account object returned from the API after a successful update. This typically includes all fields of the financial account such as ID, type, description, amount, due date, category, status, client and appointment IDs if set, payment method, and notes.
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating requests to the financial management API.
- The node makes HTTP requests to the API base URL configured in the credentials.
- Proper network connectivity to the API endpoint is necessary.
Troubleshooting
- Error: Unknown operation — Occurs if an unsupported operation name is provided; ensure "update" is selected.
- HTTP errors (4xx or 5xx) — Could indicate invalid financial account ID, missing required fields, or server issues. Verify the ID exists and all required properties are correctly filled.
- Authentication errors — Check that the API key credential is valid and has proper permissions.
- Date format issues — The due date is sent as YYYY-MM-DD; ensure the input date is correctly formatted.
- Continue on Fail — If enabled, errors per item will be returned in the output JSON under an
errorfield instead of stopping execution.
Links and References
- API Documentation (Replace with actual API docs link if available)
- n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/