Actions215
- V1 > Bank Billets Actions
- V1 > Bank Billet Accounts Actions
- V1 > Bank Billet Batches Actions
- V1 > Bank Billet Batch Exports Actions
- V1 > Bank Billet Discharges Actions
- V1 > Bank Billet Payments Actions
- V1 > Bank Billet Registrations Actions
- V1 > Bank Billet Remittances Actions
- V1 > Customers Actions
- V1 > Customer Subscriptions Actions
- V1 > Discharges Actions
- V1 > Email Deliveries Actions
- V1 > Events Actions
- V1 > Imports Actions
- V1 > Installments Actions
- V1 > Remittances Actions
- V1 > Reports Actions
- V1 > SMS Deliveries Actions
- V1 > User Info Actions
- V1 > Webhook Deliveries Actions
- V1 > Webhooks Actions
- Admin > Users Actions
- Admin > Connections Actions
- Admin > Certificates Actions
- Admin > Subaccounts Actions
- Charge > PIX Actions
- Charge > PIX Accounts Actions
- Data > Bank Billet Queries Actions
- EDI > EDI Boxes Actions
- Financial > Accounts Actions
- Financial > Balances Actions
- Financial > Commands Actions
- Financial > Statement Transactions Actions
- Financial > Transaction Imports Actions
- Financial > Providers Actions
- Payment > Bank Billets Actions
- Payment > Bank Billet Batches Actions
- Payment > Batches Actions
- Payment > DARFs Actions
- Payment > DARF Batches Actions
- Payment > PIX Actions
- Payment > PIX Batches Actions
- Payment > Utilities Actions
- Payment > Utility Batches Actions
- Transfer > Batches Actions
- Transfer > Internal Actions
- Transfer > Internal Batches Actions
- Transfer > PIX Actions
- Transfer > PIX Batches Actions
- Transfer > TED Actions
- Transfer > TED Batches Actions
Overview
This node integrates with the Kobana API to manage financial statement transactions, specifically allowing users to update existing statement transactions. It is useful in scenarios where you need to modify details of a financial transaction record within your accounting or financial management workflows. For example, you might update transaction metadata, correct amounts, or add additional information to a statement transaction after it has been initially recorded.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the statement transaction to update. |
| Request Body | A JSON object representing the fields and values to update on the statement transaction. |
| Additional Fields | Optional JSON object for any extra fields to include in the request (not mandatory here). |
Output
The node outputs a JSON array where each element corresponds to the updated statement transaction returned by the Kobana API. The structure of each JSON object matches the API's response format for a statement transaction update, typically including updated transaction details such as IDs, amounts, dates, descriptions, and any other relevant financial data.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Kobana API.
- The node dynamically selects the API base URL depending on whether the environment is set to production or sandbox.
- No other external dependencies are required.
Troubleshooting
- Invalid ID: If the provided ID does not correspond to an existing statement transaction, the API will likely return an error indicating the resource was not found. Verify the ID before running the node.
- Malformed JSON in Request Body: The "Request Body" property must be valid JSON. Invalid JSON syntax will cause parsing errors. Use proper JSON formatting.
- Authentication Errors: Ensure that the API key credential is correctly configured and has sufficient permissions to update statement transactions.
- API Rate Limits or Downtime: If requests fail intermittently, check for API rate limits or service availability issues on the Kobana side.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on Using Credentials for setting up API authentication
