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
Admin > Connections → Get
AI-generatedOverview
This node provides integration with the Kobana API, enabling users to perform various administrative and transactional operations related to financial and customer management. Specifically, for the Admin > Connections resource with the Get operation, it allows retrieving detailed information about a specific admin connection by its ID.
Common scenarios where this node is beneficial include:
- Fetching details of an existing admin connection for auditing or monitoring purposes.
- Integrating Kobana's admin connection data into workflows for reporting or automation.
- Validating connection status or properties before performing further administrative actions.
Practical example:
- A workflow that triggers when a new admin connection is created and uses this node to fetch and log the connection details for compliance tracking.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the admin connection resource to retrieve. This property is required for the Get operation. |
Output
The node outputs the JSON response from the Kobana API corresponding to the requested admin connection. The output structure reflects the admin connection's data fields as returned by the API, typically including connection metadata such as identifiers, status, configuration, and timestamps.
If the node encounters an error during execution (e.g., invalid ID or network issues), the output will contain an error field with the error message.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to 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 configured Kobana API credentials.
Troubleshooting
- Invalid ID Error: If the provided ID does not correspond to any existing admin connection, the API will return an error. Verify the ID is correct and exists in your Kobana account.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access admin connections.
- Network Issues: Connectivity problems may cause request failures. Check network settings and Kobana service availability.
- JSON Parsing Errors: Input fields expecting JSON must be correctly formatted; otherwise, parsing errors can occur.
To resolve errors, review the error messages returned in the output and verify input parameters and credentials accordingly.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on Using Credentials for setting up API authentication
