Lectful Central

Overview

This node integrates with the Lectful Central API to perform administrative operations related to subscription management and other resources. Specifically, for the Subscription Management resource with the List Plans operation, it retrieves a paginated list of all subscription plans available in the system.

This is useful when you want to automate workflows that need to fetch subscription plan data, such as syncing plans with another system, generating reports, or dynamically displaying available plans in an application.

Example use case:

• Automatically retrieve all subscription plans to update a pricing page on your website.
• Fetch plans to analyze or export subscription offerings for business intelligence.

Properties

These properties control how the node authenticates requests to the Lectful Central API.

For the List Plans operation specifically, the following input parameters are used (inherited from the general pagination pattern in the code, though not explicitly listed in the provided properties JSON but visible in the source):

Output

The node outputs an array of JSON objects representing the API response for the requested operation.

For List Plans, the output JSON contains a paginated list of subscription plans retrieved from the Lectful Central API endpoint /admin/plans. Each item in the output corresponds to a subscription plan object as returned by the API.

The exact structure of each plan object depends on the API but typically includes fields like plan ID, name, description, product family association, active status, and sort order.

No binary data output is produced by this operation.

Dependencies

• Requires access to the Lectful Central API.
• Requires either:
  • Stored credentials configured in n8n containing a valid base URL and API key, or
  • Manual configuration of Base URL and API key via node parameters.
• The API key must have sufficient permissions to access subscription plan data.
• No additional external dependencies beyond standard HTTP request capabilities.

Troubleshooting

• Missing or invalid credentials:
  Error thrown if neither stored credentials nor manual overrides provide a valid base URL and API key.
  Resolution: Configure credentials properly or use manual mode with correct values.

• Base URL Override missing in manual mode:
  If manual authentication mode is selected but no base URL override is provided, an error occurs.
  Resolution: Provide a valid Base URL Override parameter.

• API Key Override missing in manual mode:
  Similar to above, missing API key override causes failure.
  Resolution: Provide a valid API Key Override parameter.

• API errors or network issues:
  Errors from the Lectful Central API (e.g., unauthorized, not found) will be surfaced.
  Resolution: Check API key permissions, endpoint availability, and network connectivity.

• Pagination parameters:
  Providing invalid page or perPage values may result in unexpected results or empty responses.
  Resolution: Use sensible positive integers for pagination.

Links and References

• Lectful Central API Documentation (Assumed, replace with actual URL if known)
• n8n Documentation on HTTP Request Node (for understanding underlying request mechanics)

Note: This summary is based solely on static analysis of the provided source code and property definitions.