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 manage financial providers and related resources. Specifically, for the Financial > Providers resource with the Create operation, it allows users to create new financial provider entries by sending a JSON request body to the Kobana API.
Common scenarios where this node is beneficial include automating the onboarding of new financial providers into a system, integrating financial data sources, or managing provider configurations programmatically within an n8n workflow.
For example, a user can automate the creation of a new financial provider by supplying the required JSON data describing the provider's details, which the node then sends to the Kobana API to create the provider record.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the data for the new financial provider to be created. |
| Additional Fields | A JSON object containing any extra fields to include in the request (optional). |
The "Request Body" property is required and must contain the necessary data as per the Kobana API specification for creating a financial provider.
The "Additional Fields" property allows adding arbitrary JSON fields to extend or customize the request beyond the standard body.
Output
The node outputs the JSON response returned by the Kobana API after creating the financial provider. This typically includes details of the newly created provider such as its ID, name, status, and other metadata as defined by the API.
The output is structured as an array of JSON objects, each corresponding to an input item processed. Each object contains the full API response for that creation request.
No binary data output is produced by this node.
Dependencies
- Requires an active Kobana API credential configured in n8n, providing authentication to access the Kobana API.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- Network connectivity to the Kobana API endpoints is necessary.
Troubleshooting
- Invalid JSON in Request Body: If the JSON provided in the "Request Body" or "Additional Fields" is malformed, the node will throw a parsing error. Ensure valid JSON syntax.
- Authentication Errors: If the API credentials are missing or invalid, the node will fail with an authentication error. Verify that the Kobana API credential is correctly set up.
- API Validation Errors: The Kobana API may reject requests if required fields are missing or invalid. Review the API documentation for required fields and correct data formats.
- Network Issues: Connectivity problems to the Kobana API endpoint will cause request failures. Check network settings and firewall rules.
Links and References
- Kobana API Documentation (official API docs for detailed request/response schemas)
- n8n Documentation (for general usage of custom nodes and credentials)
