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 allows interaction with the Kobana API, providing quick access to various operations across multiple resources. Specifically, for the V1 > Events resource with the Get operation, it retrieves detailed information about a specific event by its ID.
Use cases include:
- Fetching details of an event for monitoring or reporting purposes.
- Integrating event data into workflows for automation or notifications.
- Auditing or logging event information from Kobana within n8n workflows.
Example: You want to retrieve details of a particular event by its unique identifier to trigger further processing or alerting in your automation pipeline.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the event resource to retrieve. This is a required string input. |
Output
The node outputs the JSON response returned by the Kobana API for the requested event. This typically includes all available fields describing the event, such as timestamps, event type, status, and any associated metadata.
The output is structured as an array of JSON objects, each representing one event (in this case, only one since it's a get-by-ID operation). There is no binary data output for 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
- Missing or invalid ID: The "ID" property is required. If omitted or incorrect, the API will return an error indicating the resource was not found.
- Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
- Network issues: Verify connectivity to the Kobana API endpoints (
https://api.kobana.com.brfor production or sandbox URL). - API rate limits or errors: Handle API errors gracefully; the node supports continuing on failure if enabled.
Common error messages:
"Resource not found": Check that the provided ID is correct."Unauthorized"or"Invalid credentials": Verify API key validity and permissions."Request timeout"or"Network error": Check network connectivity and retry.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on Using API Credentials