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 transfer batches, specifically allowing users to retrieve detailed information about a particular transfer batch by its ID. It is useful in financial workflows where batch transfers need to be tracked or audited. For example, a user might want to fetch the status and details of a specific batch of bank transfers to verify completion or reconcile accounts.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the transfer batch to retrieve. This is a required string input. |
Output
- The output is a JSON object representing the transfer batch details as returned by the Kobana API.
- The structure typically includes fields such as batch metadata, status, creation date, list of transfers within the batch, and other relevant batch-specific information.
- No binary data output is produced by 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 additional external dependencies are needed beyond the Kobana API access.
Troubleshooting
Common issues:
- Providing an invalid or non-existent batch ID will likely result in an error from the API indicating that the resource was not found.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Resource not found"or similar indicates the provided ID does not correspond to any existing transfer batch.- Authentication errors suggest checking the API key credential configuration.
- JSON parsing errors may occur if the input parameters are malformed; ensure the ID is a valid string.
Resolutions:
- Verify the batch ID is correct and exists in the Kobana system.
- Confirm that the API key credential is properly set up and has necessary permissions.
- Check network connectivity and retry the operation.
Links and References
- Kobana API Documentation (general reference for API endpoints and usage)
- n8n documentation on API Credentials for setting up API keys
