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 perform various operations related to financial transaction imports, specifically allowing users to create new transaction import records. It is useful in scenarios where you need to automate the import of financial transactions into your system from external sources or files, streamlining bookkeeping and reconciliation processes.
For example, a finance team can use this node to automatically upload batches of bank transactions into their accounting software, reducing manual data entry and errors.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the request body for creating the transaction import. This contains all necessary fields as defined by the Kobana API for transaction imports. |
| Additional Fields | A JSON object containing any extra optional fields to include in the request. |
Output
The node outputs the JSON response returned by the Kobana API after creating the transaction import. This typically includes details about the newly created import record such as its ID, status, timestamps, and any metadata provided by the API.
The output is structured as an array of JSON objects, each corresponding to an input item processed. There is no binary data output.
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 required.
Troubleshooting
- Invalid JSON in Request Body or Additional Fields: If the JSON provided in the "Request Body" or "Additional Fields" properties is malformed, the node will throw a parsing error. Ensure that the JSON syntax is correct before running.
- Authentication Errors: If the API key credential is missing or invalid, the node will fail to authenticate. Verify that the API key is correctly configured in n8n credentials.
- API Endpoint Errors: If the request body lacks required fields or contains invalid data according to the Kobana API specification, the API may return validation errors. Review the API documentation to ensure compliance.
- Network Issues: Connectivity problems to the Kobana API endpoints (production or sandbox) will cause request failures. Check network access and firewall settings.
Links and References
- Kobana API Documentation (official API docs for detailed request/response schemas)
- n8n Documentation (for general usage of custom nodes and credentials)
