Lectful Central icon

Lectful Central

Interact with the Lectful Central API for admin operations

Overview

This node integrates with the Lectful Central API to manage subscription-related entities, specifically enabling administrative operations such as creating prices for subscription plans. The "Create Price" operation under the "Subscription Management" resource allows users to define new pricing options associated with existing subscription plans.

Typical use cases include:

  • Adding a new price tier or billing option to an existing subscription plan.
  • Automating subscription pricing updates in response to business changes.
  • Managing trial periods and billing cycles programmatically.

For example, a SaaS company could use this node to create a monthly flat fee price of $29.99 USD for a specific subscription plan, including optional trial periods and activation status.

Properties

Name Meaning
Authentication Mode Choose how to authenticate with the Lectful Central API: either using stored credentials configured in n8n or manual configuration by providing base URL and API key.
Credentials Note Informational note shown when using Manual Configuration mode explaining credential usage.
Base URL Override Optional base URL to override the credential setting (without /api/v1), used only in Manual Configuration mode.
API Key Override Optional API key to override the credential setting, used only in Manual Configuration mode.
Price Name The name of the price to create (required).
Price Description A description of the price (optional).
Amount (in cents) The price amount in cents (e.g., 2999 for $29.99) (required).
Currency Currency code for the price (e.g., USD, EUR) (required).
Pricing Model The pricing model; currently only "Flat Fee" is supported (required).
Period Unit The billing cycle unit: Day, Week, Month, or Year (required).
Period The billing cycle frequency (number of units per billing cycle) (required).
Trial Period (days) Optional trial period length in days.
Is Active Boolean indicating whether the price is active (default true).
Plan ID (for Price) The ID of the subscription plan this price belongs to (required).

Output

The node outputs an array of JSON objects representing the API response from the Lectful Central server after creating the price. The structure corresponds to the created price entity, typically including fields such as:

  • id: Unique identifier of the created price.
  • name: The price name.
  • description: The price description.
  • amount: The price amount in cents.
  • currency: The currency code.
  • pricing_model: The pricing model used.
  • period_unit: Billing cycle unit.
  • period: Billing cycle frequency.
  • trial_period: Trial period in days if specified.
  • is_active: Whether the price is active.
  • priceable_id: The associated plan ID.
  • Other metadata returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires access to the Lectful Central API.
  • Requires either stored API credentials configured in n8n or manual entry of the base URL and API key.
  • The API key must have permissions to create prices on subscription plans.
  • Network connectivity to the Lectful Central API endpoint.

Troubleshooting

  • Missing or invalid credentials: If neither stored credentials nor manual overrides are provided correctly, the node will throw errors indicating missing or invalid credentials. Ensure that the API key and base URL are correctly set.
  • Invalid input parameters: Required fields such as Price Name, Amount, Currency, Pricing Model, Period Unit, Period, and Plan ID must be provided. Omitting these will cause API errors.
  • API errors: Errors returned from the Lectful Central API (e.g., invalid plan ID, unauthorized access) will be surfaced in the node's output. Check the API response message for details.
  • JSON parsing issues: Not applicable here since inputs are simple types, but ensure numeric values like amount and period are valid numbers.
  • Network issues: Timeouts or connectivity problems will cause execution failures. Verify network access to the API endpoint.

Links and References

Discussion