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 various operations on EDI Boxes, specifically supporting the "Get" operation for retrieving an EDI Box by its ID. It is useful in scenarios where you need to fetch detailed information about a specific EDI Box within your automation workflows, such as verifying box contents, status, or metadata before processing or routing data further.
Practical examples include:
- Retrieving an EDI Box to check its current state before triggering downstream processes.
- Fetching EDI Box details to log or audit data exchanges.
- Using the EDI Box information to conditionally route messages or trigger notifications.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the EDI Box resource to retrieve. This is a required string input. |
Output
The node outputs a JSON object representing the retrieved EDI Box resource. The structure corresponds directly to the Kobana API response for an EDI Box, typically including fields such as identifiers, status, timestamps, and any relevant metadata associated with the EDI Box.
No binary data output is produced by this operation.
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 additional external dependencies are needed beyond the Kobana API access.
Troubleshooting
Common issues:
- Invalid or missing ID parameter will cause the API request to fail.
- Authentication errors if the API key credential is not configured correctly.
- Network or connectivity issues when reaching the Kobana API endpoints.
Error messages:
- Errors returned from the Kobana API will be passed through, often indicating invalid IDs or permission issues.
- If the node is set to continue on failure, error details will be included in the output JSON under an
errorfield.
Resolutions:
- Ensure the ID provided is correct and exists in the Kobana system.
- Verify that the API key credential is valid and has necessary permissions.
- Check network connectivity and endpoint accessibility.
Links and References
- Kobana API Documentation (official API docs for detailed resource schemas and operations)
- n8n documentation on API credentials for setting up authentication tokens