Actions88
- Blog Actions
- Get All Posts (Admin)
- Get Post (Admin)
- Create Post (Admin)
- Update Post (Admin)
- Delete Post (Admin)
- Get Categories (Admin)
- Get Category (Admin)
- Create Category (Admin)
- Update Category (Admin)
- Delete Category (Admin)
- Get Tags (Admin)
- Get Tag (Admin)
- Create Tag (Admin)
- Update Tag (Admin)
- Delete Tag (Admin)
- Get Authors (Admin)
- Get All Posts (Public)
- Get Post (Public)
- Get Categories (Public)
- Get Tags (Public)
- Get Posts by Category (Public)
- Get Posts by Tag (Public)
- Section Actions
- AI Resource Actions
- Authentication Actions
- User Actions
- Course Actions
- Lecture Actions
- Enrollment Actions
- Learning Path Actions
- Assignment Actions
- Progress Actions
- Video Actions
- Article Actions
- Quiz Question Actions
- Quiz Choice Actions
- Quiz Submission Actions
- Image Actions
Overview
This node integrates with the Lectful API to manage blog posts and related entities with administrative privileges. Specifically, the Get All Posts (Admin) operation retrieves a list of all blog posts accessible via admin rights, allowing filtering by status, author, category, and tag, as well as pagination control.
Typical use cases include:
- Automating retrieval of blog content for internal dashboards or CMS synchronization.
- Filtering blog posts by draft or published status to manage editorial workflows.
- Extracting posts by specific authors, categories, or tags for targeted content analysis or reporting.
For example, an editor could use this node to fetch all draft blog posts authored by a particular user to review pending content before publication.
Properties
| Name | Meaning |
|---|---|
| Authentication Mode | Choose how to authenticate with the Lectful API: either using stored credentials or manual input. |
| Credentials Note | Informational note shown when Manual Configuration is selected, explaining credential overrides. |
| Base URL Override | Optional base URL to override the stored credential's base URL (excluding /api/v1). |
| API Key Override | Optional API key to override the stored credential's API key. |
| Status Filter | Filter blog posts by status: All, Draft, or Published. |
| Author ID Filter | Filter blog posts by a specific author ID. |
| Category ID Filter | Filter blog posts by a specific category ID. |
| Tag ID Filter | Filter blog posts by a specific tag ID. |
| Per Page | Number of posts to retrieve per page (default is 20). |
Output
The output is a JSON array where each item corresponds to a blog post object returned by the Lectful API. The structure typically includes fields such as:
id: Unique identifier of the blog post.title: Title of the blog post.content: Full content of the post.excerpt: Short excerpt or summary.status: Publication status (e.g., draft, published).author_id: Identifier of the author.category_ids: Array of associated category IDs.tag_ids: Array of associated tag IDs.published_at: Timestamp of when the post was published.image_id: ID of the featured image if any.- Other metadata fields like SEO meta title and description.
No binary data is output by this operation.
Dependencies
- Requires access to the Lectful API, which needs authentication via either stored credentials or manual configuration (base URL and API key).
- The node expects the Lectful API to be reachable at the configured base URL.
- Proper API permissions are required to access admin-level blog post data.
Troubleshooting
- Missing or invalid credentials: If neither stored credentials nor manual overrides are properly set, the node will throw an error indicating that valid credentials are required.
- Base URL or API key missing in manual mode: When using manual configuration, both base URL override and API key override must be provided; otherwise, an error is thrown.
- API request failures: Network issues, incorrect filters, or insufficient permissions may cause API errors. Check the error message returned by the API for details.
- Parsing errors: If the API returns unexpected data formats, the node attempts to parse JSON but may fail, resulting in raw string output.
To resolve these issues:
- Verify credentials and API keys.
- Confirm the base URL is correct and accessible.
- Ensure the API user has admin rights for blog operations.
- Review filter values for correctness.
Links and References
- Lectful API Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- General REST API troubleshooting tips: REST API Best Practices