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 payment bank billets (bank slips). Specifically, the Payment > Bank Billets - Get operation retrieves detailed information about a single bank billet by its unique ID. This is useful in scenarios where you need to fetch the current status, details, or metadata of a specific bank slip for payment tracking, reconciliation, or customer service purposes.
Practical examples:
- Fetching a bank billet's details after creation to confirm its issuance.
- Retrieving payment status or due date information for a particular bank slip.
- Integrating with accounting systems to pull up-to-date bank billet data on demand.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the bank billet to retrieve. This is required and must be provided as a string. |
Output
The output is a JSON object representing the bank billet resource retrieved from the Kobana API. It contains all relevant fields describing the bank billet, such as its ID, amount, due date, status, payer information, and other metadata defined by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Kobana API via an API key credential configured in n8n.
- 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 bank billet ID will result in an error response from the API.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity problems can prevent successful API calls.
Error messages and resolutions:
- "Resource not found" — Verify that the provided bank billet ID exists and is correct.
- "Unauthorized" or "Authentication failed" — Check that the API key credential is properly set up and has necessary permissions.
- "Request timeout" or "Network error" — Ensure stable internet connection and that the Kobana API endpoint is reachable.
Links and References
- Kobana API Documentation (general reference for API endpoints and bank billet resource)
- n8n documentation on API Credentials for setting up API keys
