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
Feature Management → Get Feature
AI-generatedOverview
The "Lectful Central" node integrates with the Lectful Central API, enabling administrative operations across various resources such as tenants, blogs, subscriptions, features, invoices, payments, and more. Specifically, the Feature Management - Get Feature operation retrieves detailed information about a specific feature by its ID.
This node is beneficial for automating administrative workflows related to managing software features, subscription plans, and other business entities within the Lectful platform. For example, you can use it to fetch feature details dynamically during a workflow to make decisions or update other systems accordingly.
Practical example:
- Retrieve a feature's configuration or limits before provisioning a new user account or adjusting subscription entitlements.
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 | Informational note shown when using Manual Configuration mode explaining credential usage. |
| Base URL Override | Optional base URL to override the stored credential's base URL (exclude /api/v1). |
| API Key Override | Optional API key to override the stored credential's API key. |
| Feature ID | The numeric ID of the feature to retrieve (required). |
Output
The node outputs an array of JSON objects, each representing the API response for the corresponding input item. For the Get Feature operation, the output JSON contains the detailed data of the requested feature, including fields such as:
id: Feature identifiername: Feature namecode: Unique feature codedescription: Description of the featuretype: Feature type (e.g., limit, boolean)- Other feature-specific properties like limits, token cost, and sort order
If the API returns a string response, the node attempts to parse it into JSON; otherwise, it outputs the raw string.
The node does not output binary data.
Dependencies
- Requires access to the Lectful Central API.
- Requires either:
- Stored credentials configured in n8n containing the base URL and API key for Lectful Central API, or
- Manual entry of Base URL and API key via node parameters.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
Missing or invalid credentials error:
Occurs if neither stored credentials nor manual overrides are provided or valid.
Resolution: Configure valid credentials in n8n or provide manual Base URL and API key.Base URL or API key missing in Manual Configuration mode:
The node requires both Base URL Override and API Key Override when manual mode is selected.
Resolution: Provide both parameters.Invalid Feature ID:
If the feature ID parameter is missing or invalid, the API will likely return an error.
Resolution: Ensure the Feature ID is a valid number and corresponds to an existing feature.API request failures:
Network issues, incorrect URLs, or API downtime may cause errors.
Resolution: Verify network connectivity, correct API endpoint, and API service status.JSON parsing errors:
When providing JSON inputs (not applicable for this operation), malformed JSON will cause errors.
Resolution: Validate JSON syntax before input.
Links and References
- Lectful Central API Documentation (Assumed, replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for authentication and error handling.
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.