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, specifically allowing you to update provider information. It supports updating a financial provider by specifying its ID and providing the updated data in JSON format.
Common scenarios where this node is beneficial include:
- Automating updates to financial provider details in your system.
- Integrating Kobana's financial provider management into workflows for syncing or maintaining up-to-date provider data.
- Bulk updating multiple providers programmatically within an automation pipeline.
For example, you might use this node to update contact information or configuration settings of a financial provider after receiving new data from another system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the financial provider to update. |
| Request Body | A JSON object containing the fields and values to update on the financial provider. |
| Additional Fields | Optional JSON object with extra fields to include in the request (not specifically used in update operation here but available generally). |
Output
The node outputs the JSON response returned by the Kobana API after performing the update operation. This typically includes the updated financial provider object with its current state as stored in Kobana.
The output is structured as an array of JSON objects, each representing the updated resource corresponding to an input item.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Kobana API.
- The node automatically selects the API base URL depending on whether the environment is production or sandbox.
- No additional external dependencies are required beyond the Kobana API access.
Troubleshooting
- Invalid ID: If the provided ID does not correspond to an existing financial provider, the API will return an error. Verify the ID is correct.
- Malformed JSON in Request Body: Ensure the JSON provided in the "Request Body" field is valid and matches the expected schema for the financial provider update.
- Authentication Errors: Confirm that the API key credential is correctly configured and has sufficient permissions.
- API Rate Limits or Downtime: Temporary failures may occur due to API limits or service issues; retrying later or checking API status can help.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output.
Links and References
- Kobana API Documentation (general reference for API endpoints and data schemas)
- n8n documentation on Using Credentials
- JSON validation tools for verifying request body correctness (e.g., https://jsonlint.com/)
