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 customer subscriptions, specifically allowing you to update existing subscriptions. It is useful in scenarios where subscription details need to be modified programmatically, such as changing plan details, updating billing information, or adjusting subscription status.
For example, you might use this node to:
- Update a customer's subscription plan after they upgrade or downgrade.
- Modify subscription metadata or custom fields.
- Change billing cycles or payment methods associated with a subscription.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the customer subscription to update (required). |
| Request Body | JSON object containing the fields and values to update in the subscription (required). |
| Additional Fields | Optional JSON object for any extra fields to include in the request (not typically used here). |
Output
The node outputs the JSON response returned by the Kobana API after updating the subscription. This typically includes the updated subscription data structure reflecting the changes made.
The output is structured as an array of JSON objects, each representing the updated subscription resource. No binary data is involved.
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 error: If the provided subscription 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 entered in the "Request Body" property is valid. Invalid JSON will cause parsing errors.
- Authentication failures: Confirm that the API key credential is correctly configured and has sufficient permissions.
- API rate limits or downtime: Temporary API issues may cause errors; retry after some time or check Kobana service status.
Links and References
- Kobana API Documentation (general reference for API endpoints and payloads)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes