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 provides integration with the Kobana API, specifically allowing users to manage "Discharges" and other financial-related resources via various operations. For the V1 > Discharges resource with the Get operation, it retrieves detailed information about a specific discharge record by its ID.
Typical use cases include:
- Fetching details of a particular discharge transaction for reconciliation or auditing.
- Automating workflows that require up-to-date discharge status or data.
- Integrating Kobana discharge data into broader financial or CRM systems.
Example: A user wants to retrieve the details of a bank billet discharge by specifying its unique ID to verify payment status or update internal records.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the discharge resource to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the discharge resource retrieved from the Kobana API. The structure corresponds directly to the API response for a single discharge entity, typically including fields such as IDs, status, amounts, dates, and related metadata.
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: Since the ID property is required, omitting it or providing an incorrect value will cause the API request to fail. Ensure the ID is correct and properly formatted.
- Authentication errors: If the API key credential is missing, invalid, or expired, the node will return authentication errors. Verify the API key configuration in n8n credentials.
- Network or API errors: Temporary network issues or API downtime can cause failures. Retrying or checking Kobana service status may help.
- Unexpected API responses: If the discharge ID does not exist or is inaccessible, the API may return a 404 or similar error. Confirm the ID exists and the authenticated user has permission to access it.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n Documentation (for general usage of custom nodes and credentials)
Note: This summary is based solely on static analysis of the provided source code and property definitions.