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
This node integrates with the Lectful Central API to manage features related to subscription plans and other administrative operations. Specifically, the Create Feature operation allows users to create a new feature associated with a plan in the Lectful system.
Typical use cases include:
- Adding new capabilities or limits to subscription plans.
- Defining feature flags or boolean toggles for product functionality.
- Setting usage limits or token costs for specific features within a plan.
For example, you might create a feature named "API Calls Max" with a limit type to restrict the maximum number of API calls allowed under a subscription plan.
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 |
| Feature Name | The name of the feature to create (required) |
| Feature Code | Unique code identifier for the feature (e.g., api.calls.max) (required) |
| Feature Description | Description text explaining the feature |
| Feature Type | Type of the feature (required): - Limit - Feature - Boolean |
| Limit Value | Numeric limit value; required if feature type is "Limit" |
| Is Unlimited | Boolean flag indicating whether the feature has unlimited usage |
| Token Cost | Number representing the token cost associated with the feature |
| Sort Order | Numeric value defining the display order of the feature |
Output
The node outputs an array of JSON objects corresponding to the API response from the Lectful Central server after creating the feature. The JSON structure typically contains the details of the newly created feature, including its ID, name, code, type, limits, and other metadata as returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Lectful Central API.
- Authentication can be provided either via stored credentials configured in n8n or manual entry of the base URL and API key.
- The node expects the API to be reachable at the specified base URL with valid authentication tokens.
- No additional external dependencies beyond HTTP requests to the Lectful API.
Troubleshooting
- Missing Credentials Error: If using stored credentials mode without properly configured credentials, the node will throw an error indicating missing or invalid credentials. Solution: Configure the API key and base URL in the credentials or switch to manual mode.
- Manual Mode Missing Parameters: When using manual configuration, both Base URL Override and API Key Override must be provided; otherwise, the node throws an error.
- Invalid Limit Value: If the feature type is set to "Limit" but no limit value is provided, the API may reject the request or the node may fail. Ensure that the limit value is set appropriately.
- Invalid JSON or Parameter Types: Although not common for this operation, ensure all inputs conform to expected types and formats.
- API Errors: Any errors returned by the Lectful API (e.g., duplicate feature codes, invalid parameters) will be surfaced in the node output or error messages.
Links and References
- Lectful Central API Documentation (Assumed, please replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for authentication and error handling
If you need further details on other operations or resources, feel free to ask!