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
The node interacts with the Kobana API to update report resources in version 1 of the API. Specifically, for the "V1 > Reports" resource and the "Update" operation, it allows users to modify existing report data by sending an updated JSON request body to the API endpoint corresponding to the report's ID.
This node is beneficial when you need to programmatically update reports within Kobana, such as changing report parameters, filters, or metadata without manually accessing the Kobana dashboard. For example, automating updates to financial or operational reports based on new criteria or correcting report details dynamically.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the report resource to update. |
| Request Body | A JSON object representing the fields and values to update in the report. |
| Additional Fields | (Optional) A JSON object with extra fields that can be included in the request if needed. |
Output
The output is a JSON array containing the response from the Kobana API after attempting to update the specified report. This typically includes the updated report data or error information if the update failed.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Kobana API.
- The node uses either the production or sandbox Kobana API base URL depending on the environment configured in the credentials.
- No other external dependencies are required.
Troubleshooting
- Common issues:
- Invalid or missing report ID will cause the API to return an error.
- Malformed JSON in the Request Body will result in a request failure.
- Insufficient permissions or invalid API credentials will cause authentication errors.
- Error messages:
"Unknown error": Generic catch-all; check network connectivity and API credentials.- API-specific error messages returned in the JSON response should be reviewed for details.
- Resolutions:
- Ensure the report ID is correct and exists.
- Validate JSON syntax before submitting.
- Verify API key and environment settings in n8n credentials.
Links and References
- Kobana API Documentation (assumed official docs for further details)
- n8n documentation on HTTP Request Node for understanding API calls in workflows
