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
This node interacts with the Lectful Central API to perform administrative operations related to blog management, among other resources. Specifically, for the "Get Blog Post by ID" operation under the "Blog Management" resource, it retrieves a specific blog post using its unique numeric ID.
Common scenarios where this node is beneficial include:
- Fetching detailed information about a particular blog post for display or processing.
- Integrating blog content dynamically into workflows or external systems.
- Automating content retrieval for reporting or synchronization purposes.
Practical example:
- A marketing automation workflow that fetches a blog post by its ID to include its content in an email campaign or social media post.
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 | Informational note shown when using Manual Configuration mode explaining credential usage. |
| Base URL Override | Optional base URL to override the stored credential's base URL (exclude /api/v1). |
| API Key Override | Optional API key to override the stored credential's API key. |
| Blog Post ID | The unique numeric identifier of the blog post to retrieve. This is required for this operation. |
Output
The output is a JSON object representing the retrieved blog post data as returned by the Lectful Central API. The structure typically includes fields such as the blog post's title, slug, content, creation date, and other metadata provided by the API.
If the API response is a string, the node attempts to parse it as JSON; otherwise, it returns the raw response.
No binary data output is produced by this operation.
Example output snippet (conceptual):
{
"id": 123,
"title": "Example Blog Post",
"slug": "example-blog-post",
"content": "<p>This is the blog content.</p>",
"created_at": "2023-01-01T12:00:00Z",
...
}
Dependencies
- Requires access to the Lectful Central API.
- Requires either stored credentials configured in n8n or manual entry of the base URL and API key.
- The node uses HTTP Bearer token authentication with the API key.
- No additional external dependencies beyond standard HTTP requests.
Troubleshooting
- Missing or invalid credentials: If neither stored credentials nor manual overrides are properly set, the node will throw an error indicating missing or invalid credentials. Ensure credentials are correctly configured or manual parameters are provided.
- Base URL Override required in manual mode: When using manual authentication mode, the base URL override must be provided; otherwise, an error is thrown.
- API errors: If the blog post ID does not exist or the API returns an error, the node will throw an error with the message from the API. Verify the blog post ID is correct.
- JSON parsing errors: If the API returns a non-JSON string unexpectedly, the node logs a warning but returns the raw string. Check API response format if issues arise.
Links and References
- Lectful Central API Documentation (Assumed URL, replace with actual if available)
- n8n Documentation on HTTP Request Node (for understanding underlying request mechanics)