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, providing quick access to a wide range of operations across multiple resources related to financial and payment management. Specifically, for the V1 > Imports resource with the Create operation, it allows users to create new import records by sending a JSON request body to the Kobana API.
Common scenarios where this node is beneficial include automating the import of financial data or transaction records into Kobana from external systems, enabling seamless synchronization and processing within workflows.
Practical example: A user can automate importing bank statement files or transaction batches by preparing the required JSON payload and using this node to create an import entry in Kobana, triggering further processing or reconciliation steps.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the data to be imported. This is required and defines the import content. |
| Additional Fields | Optional JSON object containing extra fields to customize the request beyond the main body. |
Output
The node outputs the JSON response returned by the Kobana API after creating the import. This typically includes details about the newly created import record such as its ID, status, timestamps, and any metadata provided by the API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Kobana API.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- No other external dependencies are required.
Troubleshooting
- Invalid JSON in Request Body or Additional Fields: Since the node parses these inputs as JSON, malformed JSON will cause errors. Ensure that the JSON syntax is correct.
- Authentication Errors: If the API key credential is missing or invalid, requests will fail. Verify that the credential is properly configured.
- API Endpoint or Resource Errors: Using incorrect resource names or unsupported operations will cause failures. Confirm that "V1 > Imports" and "Create" operation are selected.
- Network Issues: Connectivity problems to the Kobana API endpoints may result in timeouts or connection errors.
Links and References
- Kobana API Documentation (Assumed official API docs for reference)
- n8n Documentation on Creating Custom Nodes