Lectful Central

Overview

The node interacts with the Lectful Central API, specifically for administrative operations related to feature management and other resources. For the Feature Management - List Features operation, it retrieves a paginated list of all features associated with subscription plans. This is useful for administrators or automation workflows that need to fetch and process feature data, such as generating reports, syncing features with other systems, or managing plan capabilities programmatically.

Practical examples include:

• Automatically retrieving all available features to display in a dashboard.
• Syncing feature lists with external billing or CRM systems.
• Filtering features by type or plan for targeted updates or audits.

Properties

Additional parameters specific to the List Features operation under Feature Management:

Output

The output is an array of JSON objects representing the features retrieved from the Lectful Central API. Each object corresponds to a feature and includes details such as its ID, name, code, description, type, limits, token cost, and sort order.

Example structure of one feature item (fields may vary):

{
  "id": 123,
  "name": "API Calls Max",
  "code": "api.calls.max",
  "description": "Maximum number of API calls allowed",
  "type": "limit",
  "limit": 10000,
  "is_unlimited": false,
  "token_cost": 10,
  "sort_order": 1,
  "featureable_id": 456,
  "featureable_type": "App\\Models\\Plan"
}

No binary data output is produced by 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.
• The node uses HTTP requests with Bearer token authorization.
• No additional external dependencies beyond standard HTTP request handling.

Troubleshooting

• Missing or invalid credentials:
  Error if neither stored credentials nor manual overrides are provided or valid. Ensure credentials are correctly configured or manual Base URL and API key are entered.

• Base URL Override required in Manual mode:
  If using Manual Configuration mode without providing a Base URL Override, the node throws an error.

• API Key Override required in Manual mode:
  Similarly, missing API key override in Manual mode causes an error.

• Invalid query parameters:
  Providing invalid values for filters like planId or featureType may result in empty responses or API errors.

• Network or API errors:
  Standard HTTP errors from the Lectful Central API will be surfaced. Check network connectivity and API availability.

• JSON parsing errors:
  The node attempts to parse string responses into JSON; malformed responses could cause errors.

To resolve issues, verify authentication settings, parameter correctness, and API endpoint accessibility.

Links and References

• Lectful Central API Documentation (Assumed URL, replace with actual if known)
• n8n documentation on HTTP Request Node for understanding underlying request mechanics.
• General API troubleshooting tips: check API keys, permissions, and network connectivity.