Actions14
Overview
This node integrates with a financial management API to create new financial accounts (entries) such as receivables or payables. It is useful for automating the recording of financial transactions related to clients and appointments, including tracking due dates, payment status, categories, and payment methods.
Typical use cases include:
- Automatically creating invoices or bills when a service is scheduled or completed.
- Recording expenses or income entries in an accounting system.
- Managing financial records linked to specific clients or appointments for better tracking and reporting.
For example, you can create a "Receivable" account entry for a client’s upcoming payment with details like amount, due date, category, and payment method, which helps streamline financial workflows.
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 (format: e.g., 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), "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), "Transferência" (Transfer) |
| Observações | Notes or observations about the financial account |
Output
The node outputs JSON data representing the created financial account record as returned by the API. This typically includes all submitted fields plus any additional metadata or identifiers assigned by the backend system.
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 expects the API base URL and authentication token to be configured in the credentials.
- Uses HTTP requests to communicate with the API endpoints for financial accounts.
Troubleshooting
Common issues:
- Missing required fields such as description, amount, or due date will cause the API to reject the request.
- Invalid date formats or amounts not matching the expected decimal format may result in errors.
- Authentication failures if the API key is invalid or missing.
- Network connectivity problems preventing access to the API endpoint.
Error messages:
"Unknown operation": Indicates an unsupported operation was requested; ensure the operation is set to "Create" for this context.- API error responses usually contain descriptive messages; check the node's error output for details.
Resolutions:
- Verify all required input properties are correctly filled.
- Confirm the API key credential is valid and has necessary permissions.
- Check that the due date is provided in a proper ISO date/time format.
- Ensure network access to the API endpoint is available from the n8n environment.
Links and References
- No direct links provided in the source code. For more information, consult the documentation of the external financial management API integrated by this node.