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 interacts with the Kobana API to perform various operations related to bank billet data queries. Specifically, for the Data > Bank Billet Queries resource with the Get operation, it retrieves detailed information about a specific bank billet query by its unique ID.
Common scenarios where this node is beneficial include:
- Fetching detailed status or metadata of a particular bank billet query.
- Integrating Kobana's bank billet data retrieval into automated workflows.
- Using the retrieved data for reporting, auditing, or further processing in financial applications.
Practical example:
- A user wants to automatically check the status of a bank billet query by providing its ID and then use that data to trigger notifications or update records in another system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the bank billet query resource to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the bank billet query details fetched from the Kobana API. The structure of the JSON depends on the API response but typically includes all relevant fields describing the queried bank billet data.
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 ID will likely result in an error from the API indicating the resource was not found.
- Network connectivity problems or incorrect API credentials can cause authentication failures.
- Malformed JSON inputs in other operations (not applicable here since only ID is used) could cause errors.
Error messages and resolutions:
"Resource not found"or similar: Verify the ID is correct and exists in the Kobana system.- Authentication errors: Check that the API key credential is correctly configured and has necessary permissions.
- Timeout or network errors: Ensure stable internet connection and that the Kobana API endpoint is reachable.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on Using Credentials for setting up API keys