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, specifically allowing administrative management of connections among many other resources. The "Admin > Connections" resource with the "Create" operation enables users to create new admin connection entries in the Kobana system.
Typical use cases include automating the creation of new connection configurations or credentials within an administrative context, such as setting up integrations or access points programmatically. For example, a user might automate onboarding processes by creating multiple admin connections based on input data without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the request body for creating the admin connection. This must be provided and contains all necessary fields as per the Kobana API specification for creating a connection. |
| Additional Fields | A collection that allows adding extra JSON fields to the request. It accepts a JSON object with additional parameters to customize the creation request beyond the standard body. |
Output
The node outputs the JSON response returned by the Kobana API after attempting to create the admin connection. This typically includes details of the newly created connection such as its ID, status, and any metadata returned by the API.
If the API returns binary data (not typical for this operation), it would be included accordingly, but for the "Create" operation on admin connections, the output is expected to be purely JSON.
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 other external dependencies are required.
Troubleshooting
- Invalid JSON in Request Body or Additional Fields: Since the node parses JSON strings from input properties, malformed JSON will cause errors. Ensure that the JSON syntax is correct.
- Authentication Errors: If the API key credential is missing or invalid, requests will fail. Verify that the API key is correctly configured in n8n credentials.
- API Endpoint Errors: If the API endpoint changes or the resource path is incorrect, the node will throw errors. Confirm that the resource and operation selections match the current Kobana API documentation.
- Handling API 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 if frequent failures occur.
Links and References
- Kobana API Documentation (Please replace with the actual URL)
- n8n Documentation on Creating Custom Nodes
- JSON Validation Tools (e.g., https://jsonlint.com) for verifying JSON inputs
