Actions14
Overview
This node provides integration with a financial management API, allowing users to update existing financial accounts. It is useful for scenarios where you need to modify details of financial records such as receivables or payables within an automated workflow. For example, you can update the status of a payment, change the due date, adjust the amount, or add notes related to a specific financial account.
Typical use cases include:
- Updating the status of an invoice from "pending" to "paid".
- Changing the due date of a bill.
- Adding payment method information after a transaction.
- Modifying the category or description of a financial record.
Properties
| Name | Meaning |
|---|---|
| Financial Account ID | The unique identifier of the financial account to update. |
| 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: "Pendente" (pending), "Pago" (paid), "Vencido" (overdue), or "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: "Dinheiro" (cash), "PIX", "Cartão de Crédito" (credit card), "Cartão de Débito" (debit card), or "Transferência" (transfer). |
| Observações | Additional notes about the financial account. |
Output
The node outputs a JSON object representing the updated financial account as returned by the API. This typically includes all fields of the financial account such as its ID, type, description, amount, due date, category, status, associated client and appointment IDs, payment method, and any notes.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the external financial management API.
- The node expects the API base URL and API key to be configured in the credentials.
- HTTP requests are made to endpoints under
/financial-accountson the API server.
Troubleshooting
Common issues:
- Invalid or missing Financial Account ID will cause the update to fail.
- Incorrect API key or expired token will result in authentication errors.
- Providing invalid values for required fields (e.g., malformed date or amount) may cause validation errors from the API.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Unknown operation: financial.update": Indicates the operation name is not recognized; ensure the operation parameter is correctly set.- API response errors usually contain descriptive messages; check the error message returned in the node output.
Resolutions:
- Verify that all required properties are provided and correctly formatted.
- Confirm API credentials are valid and have necessary permissions.
- Check network access to the API endpoint.
- Review API documentation for field constraints and allowed values.
Links and References
- No direct links available from the source code. Users should refer to the documentation of the external financial management API integrated by this node for detailed API usage and field definitions.