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 provides integration with the Kobana API, enabling users to perform various operations on multiple resources related to financial and administrative management. Specifically, for the EDI > EDI Boxes resource with the Create operation, it allows creating new EDI boxes by sending a JSON request body to the Kobana API.
Common scenarios where this node is beneficial include automating the creation of EDI boxes in financial workflows, integrating EDI data exchange processes, or managing electronic document interchange setups programmatically within an n8n workflow.
For example, a user can automate the creation of an EDI box by providing the necessary configuration details as a JSON object, which the node sends to the Kobana API to create the resource without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the data required to create the EDI box. This must be provided and should conform to the API's expected schema for EDI box creation. |
| Additional Fields | Optional JSON object containing extra fields that can be included in the request to customize or extend the creation parameters. |
Output
The node outputs the JSON response returned by the Kobana API after attempting to create the EDI box. This typically includes details about the newly created EDI box such as its ID, status, configuration, and any other metadata provided by the API.
If the API returns binary data (not typical for this operation), the node would handle it accordingly, but for the "Create" operation on EDI Boxes, the output is expected to be purely JSON.
Dependencies
- Requires an active Kobana API credential configured in n8n, which includes authentication tokens or API keys necessary to authorize requests.
- The node dynamically selects the API base URL depending on whether the environment is 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" or "Additional Fields" is malformed, the node will throw a parsing error. Ensure the JSON syntax is correct.
- Authentication Errors: If the API credentials are missing, invalid, or expired, the node will fail to authenticate. Verify that the Kobana API credential is correctly set up and has valid permissions.
- API Endpoint Errors: Providing incorrect or incomplete data in the request body may cause the API to return validation errors. Review the API documentation for required fields and formats.
- Network Issues: Connectivity problems between n8n and the Kobana API endpoint can cause timeouts or connection errors. Check network settings and firewall rules if such errors occur.
Links and References
- Kobana API Documentation (official API docs for detailed request/response schemas)
- n8n Documentation on Creating Custom Nodes
