Lectful

Overview

This node integrates with the Lectful API, enabling users to manage various aspects of an online learning platform. Specifically, for the Blog resource and the Get Post (Admin) operation, it retrieves detailed information about a specific blog post using its unique ID with administrative privileges.

Typical use cases include:

• Fetching detailed blog post data for internal management or editing workflows.
• Integrating blog content into other systems or dashboards where admin-level access is required.
• Automating content review or moderation processes by retrieving posts programmatically.

Example: An education platform administrator wants to pull the full details of a blog post by its ID to display in a custom CMS or to perform automated checks before publishing.

Properties

Output

The node outputs an array of JSON objects, each representing the response from the Lectful API for the requested blog post. The JSON structure corresponds directly to the blog post's data as returned by the Lectful API's admin endpoint, typically including fields such as:

• id: Blog post ID
• title: Title of the blog post
• content: Full content/body of the post
• excerpt: Short summary or excerpt
• status: Publication status (e.g., draft, published)
• author_id: ID of the author user
• category_ids: Array of category IDs associated with the post
• tag_ids: Array of tag IDs associated with the post
• published_at: Date and time when the post was published
• image_id: ID of the featured image

No binary data output is involved in this operation.

Dependencies

• Requires access to the Lectful API.
• Requires either stored credentials configured in n8n or manual entry of the base URL and API key.
• The API key must have sufficient permissions to access blog posts with admin rights.
• 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 authentication details.
• Invalid Post ID: Providing an incorrect or non-existent blog post ID will result in an API error; verify the ID is correct.
• API permission errors: Insufficient permissions on the API key may cause authorization failures.
• Base URL format: When using manual configuration, ensure the base URL does not include the /api/v1 suffix, as it is appended automatically.
• Network issues: Connectivity problems to the Lectful API endpoint will cause request failures.

To resolve these issues:

• Confirm credentials and API keys are correctly configured.
• Verify the blog post ID exists and is accessible.
• Check network connectivity and API endpoint availability.
• Review API key permissions for admin-level blog access.

Links and References

• Lectful API Documentation (general reference for API endpoints and authentication)
• n8n documentation on HTTP Request Node for understanding underlying request mechanics (conceptual)

This summary focuses exclusively on the Blog resource and the Get Post (Admin) operation as requested.