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 financial data and related resources. Specifically, for the Financial > Providers resource with the Get operation, it retrieves detailed information about a specific financial provider by its unique ID.
Common scenarios where this node is beneficial include:
- Fetching details of a financial provider to display or process in workflows.
- Integrating Kobana's financial provider data into other systems or automations.
- Validating or enriching data based on provider information retrieved from Kobana.
Practical example:
- A workflow that triggers when a new transaction occurs and needs to fetch the associated financial provider’s details to route the transaction or generate reports.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the financial provider to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the financial provider's details as returned by the Kobana API. The structure typically includes all relevant fields describing the provider, such as name, contact info, status, and other metadata defined by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n, which provides authentication to access the Kobana API endpoints.
- 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: Since the ID property is required, omitting it or providing an incorrect ID will cause the API request to fail. Ensure the ID is correct and corresponds to an existing financial provider.
- Authentication errors: If the Kobana API credential is not set up correctly or has expired, the node will fail to authenticate. Verify the API key/token and credential configuration.
- API endpoint errors: Network issues or Kobana service downtime can cause request failures. Check network connectivity and Kobana service status.
- JSON parsing errors: Input fields expecting JSON must be valid JSON strings; otherwise, parsing will fail. For this operation, no JSON input is required except the ID string.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on Using Credentials for setting up API keys and tokens