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 integrates with the Kobana API to perform operations related to querying bank billet data, specifically under the "Data > Bank Billet Queries" resource. The "Create" operation allows users to send a request with a custom JSON body to create a new bank billet query in the Kobana system.
Typical use cases include automating the creation of bank billet queries for financial reconciliation, reporting, or triggering downstream workflows based on newly created bank billet data. For example, a user might create a bank billet query to retrieve specific billing information or to initiate processing of payment slips programmatically.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the request payload to create the bank billet query. This must be provided and contains all necessary fields as per the Kobana API specification for creating a bank billet query. |
| Additional Fields | Optional JSON object with extra fields that can be included in the request to customize or extend the creation parameters beyond the standard request body. |
Output
The node outputs the JSON response returned by the Kobana API after creating the bank billet query. This output typically includes details about the newly created query such as its ID, status, timestamps, and any other metadata provided by the API.
If the API returns binary data (not typical for this operation), it would represent file contents or attachments related to the bank billet query, but this is not indicated in the current implementation.
Dependencies
- Requires an active Kobana API credential configured in n8n with appropriate permissions.
- The node dynamically selects the API base URL depending on whether the environment is production or sandbox.
- The request uses HTTP methods and endpoints defined by the Kobana API v1 or v2 depending on the resource; for this resource, v1 is used.
Troubleshooting
- Invalid JSON in Request Body or Additional Fields: Since the node expects JSON strings for the request body and additional fields, malformed JSON will cause parsing errors. Ensure that the JSON syntax is correct before running the node.
- 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: Using incorrect or unsupported fields in the request body may result in API errors. Consult the Kobana API documentation for valid fields and formats.
- Network Issues: Connectivity problems to the Kobana API endpoints (production or sandbox) will cause request failures. Check network access and firewall settings.
- Continue On Fail Behavior: If enabled, the node will return error messages in the output JSON instead of stopping execution, which helps in debugging batch executions.
Links and References
- Kobana API Documentation (official API docs for detailed request/response schemas)
- n8n Documentation on HTTP Request Node (for understanding how API requests are made)
- JSON Validation Tools (e.g., https://jsonlint.com) to verify JSON syntax before inputting into the node properties.
