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 a wide range of operations to manage various financial and administrative resources. Specifically, the V1 > Imports resource supports updating import records by their ID.
The Update operation for the Imports resource allows users to modify existing import data by specifying the import's unique identifier and providing the updated information in JSON format. This is useful in scenarios where import details need correction or enhancement after creation, such as adjusting metadata or correcting imported transaction details.
Practical example: You have an import record representing a batch of financial transactions that was initially created with incomplete or incorrect data. Using this node’s update operation, you can send a corrected JSON payload to update that import record without needing to recreate it from scratch.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the import resource to update. |
| Request Body | The JSON object containing the fields and values to update on the import resource. |
| Additional Fields | Optional JSON object with extra fields to include in the request (not specifically used here but available). |
Output
The node outputs the JSON response returned by the Kobana API after performing the update operation. This typically includes the updated import resource data reflecting the changes made.
- The output is structured as an array of JSON objects, each corresponding to an input item processed.
- 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 endpoints.
- The node dynamically selects the API base URL depending on whether the environment is production or sandbox.
- The node uses HTTP methods (PUT for update) to interact with the Kobana REST API.
Troubleshooting
- Invalid ID error: If the provided ID does not correspond to an existing import resource, the API will likely return an error indicating the resource was not found. Verify the ID is correct.
- Malformed JSON in Request Body: The
Request Bodymust be valid JSON. Invalid JSON syntax will cause parsing errors before the request is sent. - Authentication errors: Ensure the Kobana API credentials are correctly set up and have sufficient permissions.
- API rate limits or downtime: Temporary failures may occur if the Kobana API is unavailable or rate limits are exceeded. Retry later or check API status.
Links and References
- Kobana API Documentation (general reference for API endpoints and data models)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes
