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 transaction imports, specifically allowing users to update existing transaction import records. It is useful in scenarios where imported financial transactions need correction or additional data after initial import. For example, if a transaction import record was created with incomplete or incorrect details, this node can update that record by sending a JSON request body with the new information.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the transaction import resource to update (required). |
| Request Body | A JSON object representing the fields and values to update in the transaction import. |
| Additional Fields | Optional JSON object for any extra fields to include in the request (not typically used here). |
Output
The node outputs the JSON response from the Kobana API after performing the update operation on the transaction import. This JSON contains the updated transaction import data as returned by the API. The output is structured as an array of JSON objects, each corresponding to an input item processed.
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 required.
Troubleshooting
- Invalid ID: If the provided ID does not correspond to an existing transaction import, the API will likely return an error. Verify the ID is correct.
- Malformed JSON in Request Body: The "Request Body" must be valid JSON. Invalid JSON syntax will cause parsing errors before the request is sent.
- Authentication Errors: Ensure the API key credential is correctly configured and has permissions to update transaction imports.
- API Environment Mismatch: Using the wrong environment setting (production vs sandbox) may cause unexpected results or failures.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output.
Links and References
- Kobana API Documentation (general reference for API endpoints and payloads)
- n8n documentation on Using Credentials for API authentication setup