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, enabling automation of various administrative and user-related tasks within the Lectful platform. Specifically, for the Blog - Delete Post (Admin) operation, it allows administrators to delete a blog post by its ID. This is useful in scenarios where outdated or incorrect blog content needs to be removed programmatically as part of a workflow.
Practical examples include:
- Automatically deleting blog posts that are flagged or expired.
- Integrating with content moderation systems to remove inappropriate posts.
- Managing blog content lifecycle in bulk via automated workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication Mode | Choose how to authenticate with the Lectful API: - Use Stored Credentials - Manual Configuration |
| Credentials Note | Notice shown when using Manual Configuration mode explaining credential overrides |
| Base URL Override | Optional base URL to override the stored credential's base URL (without /api/v1) |
| API Key Override | Optional API key to override the stored credential's API key |
| Post ID | The unique identifier of the blog post to delete (required) |
Output
The node outputs the JSON response from the Lectful API after attempting to delete the specified blog post. The output JSON typically contains confirmation of deletion or error details if the operation failed.
No binary data is output by this operation.
Example output JSON structure on success might look like:
{
"message": "Blog post deleted successfully",
"id": 12345
}
On failure, the output JSON will contain an error message describing the issue.
Dependencies
- Requires access to the Lectful API.
- Requires either stored credentials configured in n8n or manual entry of the Lectful API base URL and API key.
- Proper permissions for the API key to perform admin-level blog post deletions.
Troubleshooting
- Missing or invalid credentials: If neither stored credentials nor manual configuration is properly set, the node will throw an error indicating missing authentication information.
- Invalid Post ID: Providing a non-existent or malformed blog post ID will result in an API error; ensure the Post ID is correct.
- Insufficient permissions: The API key used must have admin rights to delete blog posts; otherwise, the API will reject the request.
- Base URL Override errors: When using manual mode, forgetting to provide the base URL or API key override will cause execution to fail.
- API connectivity issues: Network problems or incorrect base URLs can cause request failures.
To resolve these issues:
- Verify credentials and API keys.
- Confirm the Post ID exists and is valid.
- Check API permissions for the key.
- Ensure network connectivity and correct base URL.
Links and References
- Lectful API Documentation (hypothetical link, replace with actual if available)
- n8n documentation on HTTP Request Node for understanding API calls
- Best practices for managing API credentials securely in n8n workflows