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 such as bank billets, customers, subscriptions, webhooks, and more. Specifically, for the V1 > Imports resource with the Get operation, it retrieves detailed information about a specific import by its ID.
Use cases include automating data retrieval from Kobana imports, integrating import status or details into workflows, or triggering subsequent actions based on import data. For example, you might use this node to fetch an import's details after uploading financial transaction data, enabling further processing or reporting.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the import resource to retrieve. This is required for the Get operation. |
Output
The node outputs JSON data representing the import resource retrieved from the Kobana API. The structure corresponds directly to the API response for the import identified by the provided ID. It typically includes all relevant fields describing the import, such as metadata, status, timestamps, and any associated data.
No binary data output is indicated for this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n, which provides authentication to access the Kobana API.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- Network connectivity to the Kobana API endpoints is necessary.
Troubleshooting
- Invalid or missing ID: The node requires a valid import ID. Providing an empty or incorrect ID will result in an error from the API.
- Authentication errors: Ensure that the Kobana API credential is correctly configured and has the necessary permissions.
- API endpoint unreachable: Check network connectivity and verify if the correct environment (production vs sandbox) is selected.
- JSON parsing errors: Input fields expecting JSON must be correctly formatted; otherwise, the node may throw parsing errors.
- Continue on Fail: If enabled, the node will continue processing other items even if one fails, returning error details in the output.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on Using Credentials
- n8n documentation on HTTP Request Node for understanding request construction principles