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-related administrative tasks, specifically including the deletion of blog tags in admin mode. It allows users to authenticate either via stored credentials or manual configuration and perform various operations on blog resources such as posts, categories, tags, and authors.
The Delete Tag (Admin) operation under the Blog resource enables administrators to delete a specific blog tag by its ID. This is useful for maintaining and organizing blog content by removing obsolete or unwanted tags.
Practical example:
An administrator wants to clean up the blog's tagging system by removing tags that are no longer relevant. Using this node, they can specify the tag ID and delete it directly through the API without manually accessing the backend.
Properties
| Name | Meaning |
|---|---|
| Authentication Mode | Choose how to authenticate with the Lectful API: "Use Stored Credentials" or "Manual Configuration". |
| Credentials Note | Informational note shown when using Manual Configuration mode about credential usage. |
| Base URL Override | Optional base URL to override the credential setting (without /api/v1), used in Manual mode. |
| API Key Override | Optional API key to override the credential setting, used in Manual mode. |
| Tag ID | The ID of the blog tag to be deleted (required for Delete Tag (Admin) operation). |
Output
The node outputs an array of JSON objects representing the API response for each input item processed.
For the Delete Tag (Admin) operation, the output JSON typically contains the result of the delete request, which may be an empty object or confirmation message indicating successful deletion.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Lectful API.
- Requires either:
- Stored API credentials configured in n8n (base URL and API key), or
- Manual entry of Base URL and API key overrides.
- The node uses HTTP requests with Bearer token authentication to communicate with the Lectful API.
Troubleshooting
Missing or invalid credentials:
If neither stored credentials nor manual overrides are provided correctly, the node will throw errors indicating missing Base URL or API key. Ensure credentials are properly configured or manual parameters are set.Invalid Tag ID:
Providing an incorrect or non-existent Tag ID will likely result in an API error. Verify the Tag ID before attempting deletion.API connectivity issues:
Network problems or incorrect Base URL can cause request failures. Confirm the API endpoint is reachable and correct.Permission errors:
Deleting tags requires admin-level permissions. Ensure the API key used has sufficient rights.
Links and References
- Lectful API Documentation (Assumed official API docs; replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- REST API concepts for DELETE requests
Summary of execute() logic for Blog Resource - Delete Tag (Admin) Operation
- Retrieves input parameters including authentication mode and tag ID.
- Determines authentication method:
- If manual, uses provided Base URL and API key.
- Otherwise, fetches stored credentials.
- Constructs API request to DELETE
/admin/blog/tags/{tagId}endpoint. - Sends authenticated HTTP DELETE request.
- Collects and returns the API response as JSON output.
- Handles errors gracefully, optionally continuing on failure if configured.