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 manage billing wallets (referred to as "Bank Billet Accounts") in version 1 of the API. The Get operation retrieves detailed information about a specific billing wallet by its unique ID.
Typical use cases include:
- Fetching details of a particular billing wallet to verify its configuration or status.
- Integrating Kobana billing wallet data into workflows for financial reconciliation or reporting.
- Automating retrieval of wallet information before performing updates or validations.
Example: You have multiple billing wallets set up for different business units and want to retrieve the details of one wallet by its ID to check its current settings or status.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the billing wallet resource to retrieve. This is required to specify which billing wallet to get. |
Output
The node outputs the JSON response from the Kobana API representing the billing wallet's details. The structure typically includes all properties of the billing wallet such as its ID, name, status, configuration, and other metadata as provided by the API.
No binary data output is involved in 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
- Missing or invalid ID: The operation requires a valid billing wallet ID. Ensure the ID property is correctly set and corresponds to an existing wallet.
- Authentication errors: If the API key credential is missing, invalid, or lacks permissions, the request will fail. Verify the API key and its permissions.
- Network or API endpoint issues: The node uses different URLs for production and sandbox environments. Confirm that the environment setting matches your API key and intended usage.
- Unexpected API errors: The node returns error messages from the Kobana API in the output if the request fails. Review these messages for clues on resolving issues.
Links and References
- Kobana API Documentation (general reference for API endpoints and resources)
- n8n documentation on creating custom nodes (for understanding node development concepts)