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
Overview
The "Get Subscription" operation of the Lectful Central node allows you to retrieve detailed information about a specific subscription by its unique subscription ID. This is useful in scenarios where you need to fetch the current status, billing details, trial periods, or other metadata related to a subscription managed within the Lectful Central system.
Practical examples include:
- Fetching subscription details to display in a customer dashboard.
- Verifying subscription status before granting access to premium features.
- Automating workflows that depend on subscription data, such as sending renewal reminders or updating CRM records.
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) |
| Base URL Override | Optional base URL to override the credential setting (without /api/v1). Only shown if Manual Configuration is selected. |
| API Key Override | Optional API key to override the credential setting. Only shown if Manual Configuration is selected. |
| Subscription ID | The unique numeric identifier of the subscription to retrieve. This property is required. |
Output
The output is a JSON object representing the subscription details retrieved from the Lectful Central API. It typically includes all relevant subscription fields such as:
- Subscription identifiers
- Tenant and price IDs
- Status and billing information
- Trial period dates
- Current and end period timestamps
- Auto-collection settings
- Any other metadata provided by the API for the subscription
The exact structure depends on the API response but will be a direct representation of the subscription resource.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Lectful Central API.
- Authentication can be done via stored credentials configured in n8n or manual entry of the base URL and API key.
- The node expects the API to be reachable at the specified base URL with valid authentication tokens.
Troubleshooting
- Missing or invalid credentials: If using stored credentials, ensure they are properly configured with a valid base URL and API key. If using manual mode, both the base URL override and API key override must be provided.
- Subscription ID not provided or invalid: The subscription ID is required and must be a valid number corresponding to an existing subscription.
- API connectivity issues: Network problems or incorrect base URLs can cause request failures. Verify the base URL and network access.
- API errors: The API may return errors if the subscription does not exist or if the user lacks permissions. Check error messages returned in the node output for details.
- JSON parsing errors: The node attempts to parse string responses into JSON; malformed responses could cause errors.
Links and References
- Lectful Central API Documentation (Assumed link, replace with actual if available)
- n8n Documentation on HTTP Request Node for understanding API calls
- General REST API best practices for troubleshooting connectivity and authentication issues