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 "Lectful Central" node integrates with the Lectful Central API, enabling administrative operations across various resources such as authentication, tenant management, blog management, subscription handling, and health checks. Specifically, the Health Checks - Startup Health Check operation verifies if the Lectful Central application is in the process of starting up.
This node is beneficial for monitoring and automating workflows that depend on the availability and readiness of the Lectful Central system. For example, before triggering downstream processes or integrations, you can use the startup health check to ensure the application has started successfully.
Practical example:
- Use the Startup Health Check to programmatically verify that the Lectful Central backend is booting up correctly after a deployment or restart, preventing premature API calls that might fail.
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) |
| Credentials Note | Notice shown when using Manual Configuration mode, explaining that credentials fields can be left empty and overridden by manual inputs. |
| Base URL Override | Optional base URL to override the stored credential's base URL (without /api/v1). Required if using Manual Configuration. |
| API Key Override | Optional API key to override the stored credential's API key. Required if using Manual Configuration. |
Output
The node outputs an array of JSON objects representing the API response from the health check endpoint. The structure depends on the Lectful Central API's response but typically includes status information about the application's startup state.
Example output JSON structure (simplified):
{
"status": "starting",
"details": {
"services": [
{"name": "database", "status": "ok"},
{"name": "cache", "status": "pending"}
]
}
}
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.
- Network connectivity to the Lectful Central instance.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
Missing or invalid credentials error:
If using "Use Stored Credentials" mode, ensure that valid credentials (Base URL and API key) are configured in n8n. If using "Manual Configuration," both Base URL Override and API Key Override must be provided.Base URL Override required error:
When "Manual Configuration" is selected, the Base URL Override cannot be empty.API Key Override required error:
When "Manual Configuration" is selected, the API Key Override cannot be empty.Timeouts or network errors:
Verify network connectivity to the Lectful Central API endpoint and that the API is accessible.Unexpected API responses or parsing errors:
The node attempts to parse string responses as JSON; if parsing fails, the raw string is returned. Ensure the Lectful Central API is returning valid JSON.
Links and References
- Lectful Central API Documentation (Assumed, replace with actual URL if available)
- n8n Documentation: Creating Custom Nodes
- General REST API usage in n8n: HTTP Request Node