Lectful Central

Overview

The "Lectful Central" node integrates with the Lectful Central API, enabling administrative operations across various resources such as authentication, tenant management, blog management, image management, subscriptions, and more. Specifically, for the Blog Management resource with the List Blog Posts operation, this node retrieves a paginated list of all blog posts from the Lectful Central system.

This node is beneficial in scenarios where you want to automate content workflows, synchronize blog data with other systems, or build dashboards that display blog post information. For example, you could use it to fetch the latest blog posts regularly and push summaries to a newsletter service or update a website's blog section dynamically.

Properties

These properties control how the node authenticates requests to the Lectful Central API.

Output

The output is an array of JSON objects representing the API response. For the List Blog Posts operation, the json field contains the paginated list of blog posts retrieved from the endpoint /admin/blogs. The structure typically includes metadata about pagination and an array of blog post objects with their details (e.g., title, slug, content, creation date).

No binary data is output by this operation.

Example output snippet (simplified):

[
  {
    "json": {
      "data": [
        {
          "id": 123,
          "title": "First Blog Post",
          "slug": "first-blog-post",
          "content": "Content of the first blog post...",
          "created_at": "2024-01-01T12:00:00Z"
        },
        {
          "id": 124,
          "title": "Second Blog Post",
          "slug": "second-blog-post",
          "content": "Content of the second blog post...",
          "created_at": "2024-01-02T12:00:00Z"
        }
      ],
      "pagination": {
        "page": 1,
        "per_page": 15,
        "total": 50
      }
    }
  }
]

Dependencies

• Requires access to the Lectful Central API.
• Authentication can be provided either via:
  • Stored credentials configured in n8n (an API key and base URL).
  • Manual configuration by specifying the base URL and API key directly in the node parameters.
• The node uses HTTP requests with Bearer token authorization.
• No additional external libraries are required beyond what n8n provides.

Troubleshooting

• Missing or invalid credentials:
  If neither stored credentials nor manual overrides are properly set, the node will throw errors indicating missing base URL or API key. Ensure credentials are correctly configured or manual values are provided.

• Invalid Base URL Override or API Key Override:
  When using manual mode, both base URL and API key must be provided; otherwise, execution will fail.

• API request failures:
  Network issues, incorrect API keys, or insufficient permissions may cause API calls to fail. Check the error messages returned by the API for details.

• Parsing errors:
  The node attempts to parse string responses as JSON. If the API returns malformed JSON, parsing will fail, causing errors.

• Rate limits or API downtime:
  If the Lectful Central API enforces rate limits or experiences downtime, requests may fail temporarily.

Links and References

• Lectful Central API Documentation (Assumed, replace with actual if available)
• n8n Documentation on Creating Custom Nodes
• General REST API best practices for authentication and pagination

If you need summaries for other operations or resources, feel free to ask!