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 allows you to interact with the Kobana API, specifically to create reports under the "V1 > Reports" resource. The "Create" operation lets you send a JSON request body to generate a new report in Kobana.
Typical use cases include automating report generation workflows where you need to programmatically create financial or operational reports based on dynamic data inputs. For example, you might use this node to generate daily sales reports or customer activity summaries by providing the appropriate JSON payload describing the report parameters.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the content and parameters of the report to be created. |
| Additional Fields | Optional JSON object with extra fields that can be included in the request for flexibility. |
- Request Body is required and must contain the full JSON structure expected by the Kobana API for creating a report.
- Additional Fields allows adding any other optional parameters as a JSON object to customize the request further.
Output
The node outputs the JSON response returned by the Kobana API after creating the report. This typically includes details about the newly created report such as its ID, status, creation timestamp, and any metadata provided by the API.
If the API supports binary data (e.g., downloadable report files), the node would handle it accordingly, but based on the static code analysis, the output here is purely JSON.
Dependencies
- Requires an active Kobana API credential configured in n8n with appropriate permissions to create reports.
- The node dynamically selects the API base URL depending on whether the environment is production or sandbox.
- No additional external dependencies are indicated beyond the Kobana API access.
Troubleshooting
- Invalid JSON in Request Body: If the JSON provided in the "Request Body" or "Additional Fields" is malformed, the node will throw a parsing error. Ensure valid JSON syntax.
- Authentication Errors: If the API key or credentials are missing or invalid, the node will fail to authenticate. Verify your Kobana API credentials in n8n.
- API Endpoint Errors: Incorrect or incomplete request bodies may cause the Kobana API to return errors. Consult the Kobana API documentation for required fields.
- Rate Limits or Network Issues: Temporary network failures or rate limiting by the Kobana API may cause errors. Implement retry logic or check API usage limits.
Links and References
- Kobana API Documentation (assumed official docs for detailed API schema)
- n8n Documentation on Creating Custom Nodes
- JSON validation tools like JSONLint to verify request body correctness before use
