Lectful icon

Lectful

Interact with the VIPay Lectful API

Actions88

Overview

This node integrates with the Lectful API to manage blog posts in an administrative context. Specifically, the Update Post (Admin) operation allows users to update existing blog posts by specifying various attributes such as title, content, excerpt, SEO metadata, status, categories, tags, publication date, author, and featured image.

Typical use cases include:

  • Automating updates to blog content from external systems.
  • Managing blog post metadata for SEO purposes programmatically.
  • Changing the publication status or scheduling posts.
  • Associating posts with categories, tags, authors, and images dynamically.

For example, a marketing automation workflow could update blog posts with new content and metadata based on campaign data or editorial calendar changes.

Properties

Name Meaning
Authentication Mode Choose how to authenticate with the Lectful API: "Use Stored Credentials" or "Manual Configuration".
Base URL Override (Manual mode) Optional base URL to override the credential setting (without /api/v1).
API Key Override (Manual mode) Optional API key to override the credential setting.
Post ID The unique identifier of the blog post to update (required).
Title New title of the blog post.
Content New content/body of the blog post.
Excerpt New excerpt/summary of the blog post.
Meta Title New meta title for SEO purposes.
Meta Description New meta description for SEO purposes.
Status Status of the blog post; options are "Draft" or "Published".
Category IDs Comma-separated list of category IDs to associate with the post.
Tag IDs Comma-separated list of tag IDs to associate with the post.
Published At Date and time when the post should be published.
Author ID ID of the author user to assign to the post.
Image ID ID of the featured image for the post.

Output

The node outputs an array of JSON objects representing the API response for each input item processed. For the Update Post (Admin) operation, the output JSON contains the updated blog post details as returned by the Lectful API after a successful update request.

The structure typically includes fields like:

  • id: Blog post ID
  • title, content, excerpt
  • meta_title, meta_description
  • status
  • category_ids, tag_ids
  • published_at
  • author_id
  • image_id
  • Other metadata related to the blog post

No binary data is output by this operation.

Dependencies

  • Requires access to the Lectful API.
  • Authentication can be provided either via stored credentials configured in n8n or manually by specifying the base URL and API key.
  • The node expects the Lectful API to be reachable at the specified base URL with valid authentication tokens.
  • No additional external dependencies beyond HTTP requests to the Lectful API.

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.
  • Invalid Post ID: The Post ID must correspond to an existing blog post; otherwise, the API will return an error.
  • Malformed category or tag IDs: Category and tag IDs must be comma-separated integers. Invalid formatting may cause API errors.
  • API errors: The node logs detailed messages about the API request and response. Common HTTP errors like 401 Unauthorized or 404 Not Found indicate authentication issues or missing resources.
  • Empty required fields: While most update fields are optional, the Post ID is mandatory. Omitting it will cause the node to throw an error.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

This summary is based solely on static analysis of the provided source code and property definitions.

Discussion