Lectful Central

Overview

The "Update Feature" operation in the Lectful Central node allows users to modify an existing feature within the Feature Management resource. This operation is useful for administrators or automation workflows that need to update feature details such as name, description, limits, token costs, and display order dynamically.

Typical scenarios include:

• Adjusting feature limits or token costs based on new business rules.
• Updating feature descriptions or names to reflect changes in product offerings.
• Changing whether a feature is unlimited or setting its sort order for UI display.

For example, if a subscription plan's API call limit feature needs to be increased or renamed, this operation can automate that update without manual intervention.

Properties

Note: Only the Feature ID is required to identify which feature to update; other properties are optional and only included if you want to change them.

Output

The output is a JSON object representing the updated feature as returned by the Lectful Central API. It typically includes all feature attributes such as ID, name, description, type, limits, token cost, and sort order after the update.

Example output structure (simplified):

{
  "id": 123,
  "name": "Updated Feature Name",
  "description": "Updated description",
  "limit": 1000,
  "is_unlimited": false,
  "token_cost": 10,
  "sort_order": 2,
  "type": "limit",
  "featureable_id": 456,
  "featureable_type": "App\\Models\\Plan"
}

The node does not output binary data for this operation.

Dependencies

• Requires access to the Lectful Central API.
• Authentication via either stored credentials configured in n8n or manual entry of Base URL and API key.
• Proper permissions to update features in the Lectful Central system.

Troubleshooting

• Missing or invalid credentials: If neither stored credentials nor manual configuration with valid Base URL and API key are provided, the node will throw an error. Ensure credentials are correctly set or manual parameters are filled.
• Feature ID not provided or invalid: The operation requires a valid numeric Feature ID. Omitting it or providing an invalid ID will cause the API request to fail.
• Invalid property values: For example, setting a negative limit or invalid JSON in other operations may cause errors. Validate inputs before execution.
• API errors: The node logs API responses and errors. Common API errors include unauthorized access (check API key), resource not found (verify Feature ID), or validation errors (check input fields).
• JSON parsing errors: Although not typical for this operation, if any JSON input is malformed, the node will throw an error.

To resolve issues, verify credentials, input parameters, and consult API documentation for correct field formats.

Links and References

• Lectful Central API Documentation (hypothetical link, replace with actual if available)
• n8n Documentation on Creating Custom Nodes
• General REST API best practices for authentication and error handling.