Actions63
- Authentication Actions
- Tenant Management Actions
- Blog Management Actions
- Image Management Actions
- BuilderX AI Integration Actions
- Form Submissions Actions
- Subscription Management Actions
- Subscription Operations Actions
- Product Family Management Actions
- Feature Management Actions
- Invoice Management Actions
- Payment Management Actions
- Payment Method Management Actions
- Coupon Management Actions
- Health Checks Actions
Overview
The "Update Subscription" operation in the Lectful Central node allows users to modify existing subscription details via the Lectful Central API. This operation is useful for updating subscription attributes such as the subscription's end date or associated price.
Typical use cases include:
- Extending or shortening a subscription period by changing its end date.
- Changing the pricing plan linked to a subscription.
- Adjusting trial periods or other subscription-related dates (if supported).
For example, an admin might update a customer's subscription to extend their access by setting a new subscription end date in ISO 8601 format.
Properties
| Name | Meaning |
|---|---|
| Authentication Mode | Choose how to authenticate with the Lectful Central API: - Use Stored Credentials - Manual Configuration (provide base URL and API key manually) |
| Credentials Note | Notice shown when using Manual Configuration mode explaining credential overrides. |
| Base URL Override | Optional base URL to override the stored credential's base URL (without /api/v1). |
| API Key Override | Optional API key to override the stored credential's API key. |
| Subscription ID | The unique numeric identifier of the subscription to update (required). |
| Subscription Ends At | New subscription end date in ISO 8601 format (optional; used to set or change the end date). |
Output
The node outputs the JSON response returned by the Lectful Central API after attempting to update the subscription. This typically includes the updated subscription object with its current state and properties.
If the API returns a string response, the node attempts to parse it into JSON before outputting.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Lectful Central API.
- Authentication can be provided either by:
- Stored credentials configured in n8n (an API key and base URL).
- Manual configuration by specifying the base URL and API key directly in the node parameters.
- The node uses HTTP Bearer token authentication with the API key.
Troubleshooting
- Missing or invalid credentials: If neither stored credentials nor manual overrides are properly set, the node will throw an error indicating that valid credentials are required.
- Base URL or API key missing in manual mode: When using manual configuration, both the base URL override and API key override must be provided; otherwise, an error is thrown.
- Invalid Subscription ID: Providing an incorrect or non-existent subscription ID will likely result in an API error.
- Invalid date format: The
Subscription Ends Atproperty must be in ISO 8601 format; otherwise, the API may reject the request. - API errors: Any errors returned from the Lectful Central API (e.g., permission denied, invalid parameters) will be surfaced in the node's output or error messages.
To resolve issues:
- Verify credentials and API access.
- Ensure all required fields are correctly filled.
- Confirm date formats comply with ISO 8601.
- Check API documentation or logs for detailed error information.
Links and References
- Lectful Central API Documentation (Assumed, replace with actual URL if available)
- ISO 8601 Date Format Reference
This summary is based on static analysis of the node's source code and input property definitions.