Lectful Central

Overview

This node interacts with the Lectful Central API to perform administrative operations, including managing blog posts. Specifically, the Get Blog Post by Slug operation retrieves a single blog post using its URL-friendly slug identifier.

This operation is useful when you want to fetch detailed information about a specific blog post without knowing its internal ID, for example:

• Displaying a blog post on a website based on the slug in the URL.
• Integrating blog content dynamically into other applications or dashboards.
• Automating content retrieval workflows where slugs are used as unique identifiers.

Properties

Output

The output JSON contains the full response from the Lectful Central API for the requested blog post. It typically includes all details of the blog post such as title, content, slug, creation date, author info, and any other metadata provided by the API.

If the API returns a string response, the node attempts to parse it as JSON; otherwise, it outputs the raw string.

No binary data is output by this operation.

Example output structure (simplified):

{
  "id": 123,
  "title": "Example Blog Post",
  "slug": "example-blog-post",
  "content": "<p>Blog post content here...</p>",
  "created_at": "2023-01-01T12:00:00Z",
  "author": {
    "id": 45,
    "name": "Author Name"
  }
}

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 API key must have permissions to read blog posts.
• No additional external dependencies beyond standard HTTP requests.

Troubleshooting

• Missing or invalid credentials:
  If using stored credentials, ensure they are correctly configured with a valid base URL and API key. If using manual mode, both Base URL Override and API Key Override must be provided.
  Error message: "Valid credentials are required when using 'Use Stored Credentials' mode..." or "Base URL Override is required..."

• Invalid slug or blog post not found:
  If the slug does not correspond to any blog post, the API may return a 404 error or an empty response. Verify the slug value is correct.

• API connectivity issues:
  Network problems or incorrect base URL can cause request failures. Check the base URL and network connectivity.

• Invalid JSON response:
  If the API returns malformed JSON, the node will output the raw string but may log a parsing failure.

Links and References

• Lectful Central API Documentation (Assumed, replace with actual URL if available)
• n8n HTTP Request Helper Documentation (for understanding underlying request mechanism)

This summary covers the logic and usage of the Get Blog Post by Slug operation within the Lectful Central node based on static analysis of the source code and provided property definitions.