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 interacts with the Kobana API to perform various operations on user information and other resources. Specifically, for the V1 > User Info resource with the Update operation, it updates user information by sending a PUT request with a JSON body containing the updated data.
Use cases include automating updates to user profiles or account details in Kobana, such as changing contact information, preferences, or other user-related fields. This is useful in workflows where user data needs to be synchronized or modified based on external triggers or inputs.
Example: Automatically update a user's profile information when a form is submitted or when data changes in another system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the user info resource to update. |
| Request Body | A JSON object representing the fields and values to update in the user info resource. |
| Additional Fields | (Optional) A JSON object with extra fields that can be included in the request if needed. |
Output
The node outputs the JSON response from the Kobana API after performing the update operation. This typically includes the updated user information object reflecting the changes made.
- The output is an array of JSON objects, each corresponding to an input item processed.
- No binary data output is indicated 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 required beyond the Kobana API access.
Troubleshooting
- Invalid ID error: If the provided ID does not exist or is malformed, the API will return an error. Verify the ID is correct.
- Malformed JSON in Request Body: Ensure the JSON provided in the "Request Body" property is valid and correctly formatted.
- Authentication errors: Confirm that the API key credential is valid and has sufficient permissions.
- API environment mismatch: Make sure the environment setting matches the intended API endpoint (sandbox vs production).
- 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 payloads)
- n8n documentation on HTTP Request Node for understanding API interaction patterns