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 enables interaction with the Kobana API, specifically for managing "Discharges" under version 1 (V1). The "Create" operation allows users to create a new discharge record by sending a JSON request body to the Kobana API. This is useful in financial or billing workflows where discharges (likely representing payment discharges or similar financial events) need to be programmatically created and tracked.
Practical examples include:
- Automatically creating a discharge record when a payment is confirmed.
- Integrating discharge creation into an automated billing or accounting system.
- Creating discharges based on external triggers or data sources within an n8n workflow.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the discharge details to be sent in the creation request. |
| Additional Fields | A JSON object containing any extra fields to include in the request (optional). |
Note: For this operation, the "Request Body" property is required and must contain the necessary data for creating the discharge.
Output
The node outputs the JSON response returned by the Kobana API after creating the discharge. This typically includes details of the newly created discharge such as its ID, status, timestamps, and any other relevant metadata provided by the API.
If the API supports binary data output for this resource (not indicated here), it would be summarized accordingly, but in this case, the output is purely JSON.
Dependencies
- Requires an active Kobana API credential configured in n8n, which provides authentication tokens or API keys needed to authorize requests.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- No additional external dependencies are required beyond the Kobana API access.
Troubleshooting
- Invalid JSON in Request Body: If the JSON provided in the "Request Body" field is malformed, the node will throw a parsing error. Ensure the JSON syntax is correct.
- Authentication Errors: If the Kobana API credentials are missing, invalid, or expired, the node will fail to authenticate. Verify that the API key or token is correctly set up in n8n credentials.
- API Endpoint Errors: If the API returns errors due to invalid or missing required fields in the request body, check the Kobana API documentation for required parameters and ensure they are included.
- Network Issues: Connectivity problems to the Kobana API endpoints can cause timeouts or failures. Confirm network access and endpoint availability.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- Kobana API Documentation (assumed official docs URL)
- n8n Documentation on Creating Custom Nodes
- JSON Validation Tools (e.g., https://jsonlint.com/) for verifying request body syntax
