Gestor Clientes Max - Finanças
Overview
This node, "Gestor Clientes Max - Finanças," manages financial accounts by interacting with an external financial management API. It supports creating, retrieving, updating, deleting financial accounts, and fetching summaries or overdue accounts. The "Create" operation specifically allows users to add new financial account entries such as receivables or payables.
Common scenarios for this node include automating financial record keeping, integrating financial data from other systems, managing client billing or expenses, and tracking payment statuses. For example, a business could use it to automatically create new payable or receivable accounts when invoices are generated or payments are scheduled.
Properties
| Name | Meaning |
|---|---|
| Tipo | Type of financial account: "Receita (A Receber)" (receivable) or "Despesa (A Pagar)" (payable). |
| Descrição | Description of the financial account. |
| Valor | Amount of the financial account in format like "150.00". |
| Data de Vencimento | Due date of the financial account. |
| Categoria | Category of the financial account. |
| Status | Status of the financial account; options: "Pendente" (pending), "Pago" (paid), "Vencido" (overdue), "Cancelado" (cancelled). |
| Cliente ID (Opcional) | Optional client ID associated with the financial account. |
| Agendamento ID (Opcional) | Optional appointment ID associated with the financial account. |
| Método de Pagamento | Payment method used; options: "Dinheiro" (cash), "PIX", "Cartão de Crédito" (credit card), "Cartão de Débito" (debit card), "Transferência" (transfer). |
| Observações | Additional notes about the financial account. |
Output
The node outputs JSON objects representing the created financial account as returned by the external API. This typically includes all details of the newly created account such as its ID, type, description, amount, due date, category, status, associated client or appointment IDs, payment method, and any notes.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the external financial management API.
- The node makes HTTP requests to the API base URL configured in the credentials.
- Proper configuration of the API key and endpoint is necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Incorrect date format for "Data de Vencimento" may lead to request errors.
- Required fields missing or empty will cause the API to reject the creation request.
- Network connectivity problems can prevent communication with the API.
Error messages:
"Unknown operation: create"indicates the operation parameter was not recognized; ensure "create" is selected.- API error responses will be passed through; check the message for details such as validation errors or permission issues.
- If the node throws an error about missing credentials, verify that the API key credential is properly set up.
Resolution tips:
- Double-check all required input properties are provided and correctly formatted.
- Verify API key validity and permissions.
- Ensure the API endpoint is reachable from the n8n environment.
- Use the node's "Continue On Fail" option to handle individual item errors gracefully during batch operations.
Links and References
- No direct links available from the source code.
- Refer to the external financial management API documentation for detailed information on endpoints and data formats.
- n8n documentation on HTTP Request node for understanding underlying HTTP calls.