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 "Discharges" under the V1 API version, specifically supporting the Update operation. The update operation allows modifying an existing discharge resource by specifying its ID and providing a JSON request body with the fields to update.
Typical use cases include automating updates to discharge records in financial or billing workflows, such as correcting details, changing statuses, or adding metadata. For example, you might update a discharge record to reflect a payment adjustment or to add additional notes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the discharge resource to update. |
| Request Body | A JSON object representing the fields and values to update on the discharge resource. |
| Additional Fields | Optional JSON object with extra fields for the request (not typically used for update). |
Output
The node outputs the JSON response returned by the Kobana API after performing the update operation. This JSON contains the updated discharge resource data reflecting the changes made.
- The output is structured as an array of JSON objects, each corresponding to an input item processed.
- No binary data output is involved.
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 other external dependencies are required.
Troubleshooting
- Invalid ID: If the provided ID does not exist or is malformed, the API will return an error indicating the resource was not found. Verify the ID correctness.
- Malformed JSON in Request Body: The request body must be valid JSON. Errors parsing this will cause the node to fail. Use proper JSON formatting.
- Authentication Errors: Ensure the API key credential is correctly configured and has permissions to update discharges.
- API Rate Limits or Downtime: Network or API availability issues may cause errors; retry or check service status.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output.
Links and References
- Kobana API Documentation (general reference for API endpoints and payloads)
- n8n documentation on Using Credentials
- JSON formatting guides for constructing request bodies