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 creation of new statement transactions. It is useful in scenarios where you need to automate the addition of transaction records into a financial system, such as importing bank statement lines or recording manual adjustments.
For example, a finance team could use this node to automatically create statement transactions from a CSV import or an external banking feed, ensuring that the accounting system stays up-to-date without manual entry.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the details of the statement transaction to be created. |
| Additional Fields | Optional JSON object containing extra fields for the request to customize the transaction. |
- Request Body: This is a required property where you provide the full JSON payload describing the statement transaction to create.
- Additional Fields: An optional JSON object to include any additional parameters supported by the API for the create operation.
Output
The node outputs a JSON array where each item corresponds to the response from the Kobana API after creating a statement transaction. The structure of each JSON object matches the API's response schema for a created statement transaction, typically including identifiers, status, amounts, dates, and other relevant transaction details.
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 production or sandbox.
- No other external dependencies are needed beyond the Kobana API access.
Troubleshooting
- Invalid JSON in Request Body or Additional Fields: Since these properties expect JSON strings, malformed JSON will cause errors. Ensure valid JSON syntax.
- Authentication Errors: If the API key credential is missing or invalid, requests will fail. Verify the API key and its permissions.
- API Endpoint Errors: Providing incorrect or incomplete data in the request body may result in API validation errors. Consult the Kobana API documentation for required fields.
- Network Issues: Connectivity problems to the Kobana API endpoints can cause timeouts or failures. Check network access and endpoint availability.
Links and References
- Kobana API Documentation (hypothetical link; replace with actual if available)
- n8n Documentation on Creating Custom Nodes