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 "Lectful Central" node integrates with the Lectful Central API, enabling administrative operations across various resources such as subscriptions, tenants, blogs, payments, and more. Specifically, for the Subscription Management resource and the Delete Plan operation, this node allows users to delete a subscription plan by its unique identifier.
This operation is useful in scenarios where a subscription plan is no longer offered or needs to be removed from the system to prevent new subscriptions under that plan. For example, an admin might use this node to clean up deprecated plans or remove test plans after migration.
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. |
| Plan ID | The unique numeric identifier of the subscription plan to delete. This is required. |
Output
The node outputs the JSON response returned by the Lectful Central API after attempting to delete the specified plan. Typically, for a successful deletion, the API may return confirmation details or an empty object. If the deletion fails, the output will contain error information.
The output structure is:
{
"json": {
// API response data or error message
}
}
No binary data is involved in this operation.
Dependencies
- Requires access to the Lectful Central API.
- Authentication can be provided either via:
- 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.
- No additional external dependencies are needed beyond HTTP access to the Lectful Central API.
Troubleshooting
Common Issues
Missing or invalid credentials:
If neither stored credentials nor manual overrides are properly set, the node will throw an error indicating missing or invalid credentials.Missing Plan ID:
The Plan ID parameter is required. Omitting it will cause the node to fail.API errors on deletion:
The API might reject the deletion if the plan is linked to active subscriptions or other dependent entities.
Error Messages and Resolutions
"Base URL Override is required when using Manual Configuration mode":
Ensure you provide a valid base URL without the/api/v1suffix when using manual authentication."API Key Override is required when using Manual Configuration mode":
Provide a valid API key in manual mode."Valid credentials are required when using 'Use Stored Credentials' mode":
Configure the Lectful Central API credentials in n8n or switch to manual mode.API response errors (e.g., 404 Not Found, 400 Bad Request):
Verify the Plan ID exists and that the plan is eligible for deletion.
Links and References
- Lectful Central API Documentation (Assumed URL; replace with actual if known)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for DELETE operations
If you need summaries for other resources or operations, feel free to ask!