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 bank billet registrations and other related financial resources. Specifically, for the V1 > Bank Billet Registrations resource with the Get operation, it retrieves detailed information about a specific bank billet registration by its unique ID.
Common scenarios where this node is beneficial include:
- Fetching details of a particular bank billet registration for verification or reporting.
- Integrating Kobana's bank billet data into workflows that require up-to-date payment or billing information.
- Automating retrieval of bank billet registration data as part of financial reconciliation processes.
Practical example:
- A finance team wants to automatically pull the status and details of a bank billet registration after it has been created or updated in Kobana, to update their internal systems or trigger further actions based on the payment status.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the bank billet registration to retrieve. This is a required string input. |
Output
The node outputs a JSON object representing the bank billet registration details retrieved from the Kobana API. The structure corresponds directly to the API response for a single bank billet registration resource, typically including fields such as registration ID, status, amounts, dates, and related metadata.
No binary data output is produced by 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:
- Invalid or missing ID parameter will cause the API request to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent successful API calls.
Error messages and resolutions:
"Resource not found"or similar errors indicate the provided ID does not exist; verify the ID value.- Authentication errors suggest checking the API key credential configuration.
- JSON parsing errors may occur if the input body or parameters are malformed; ensure valid JSON syntax.
Links and References
- Kobana API Documentation (general reference for endpoints and data structures)
- n8n documentation on API Credentials for setting up API key authentication