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 categories and other resources. Specifically, the Update Category (Admin) operation allows updating an existing blog category's details such as its name and description via the admin API endpoint.
Typical use cases include:
- Modifying the metadata of a blog category in a content management workflow.
- Automating updates to blog categories based on external triggers or data changes.
- Integrating blog category management into broader automation pipelines for website or content platform administration.
For example, you might use this node to update the description of a blog category after receiving new information from a marketing team or to rename a category to better reflect current content themes.
Properties
| Name | Meaning |
|---|---|
| Authentication Mode | Choose how to authenticate with the Lectful API: - Use Stored Credentials - Manual Configuration (provide Base URL and API key manually) |
| Credentials Note | Informational note shown when using Manual Configuration mode about credential usage. |
| 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. |
| Category ID | The unique identifier of the blog category to update (required). |
| Category Name | New name for the blog category (optional for update; required for creation). |
| Category Description | New description text for the blog category (optional). |
Output
The node outputs the JSON response returned by the Lectful API after performing the update operation. This typically includes the updated blog category object with fields such as:
id: The category ID.name: The updated category name.description: The updated category description.- Other metadata related to the category.
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 API base URL and API key.
- The API key must have sufficient permissions to perform admin-level blog category updates.
Troubleshooting
- Missing or invalid credentials: If neither stored credentials nor manual overrides are provided correctly, the node will throw an error indicating missing authentication details.
- Invalid Category ID: Providing a non-existent or incorrect category ID will result in an API error. Verify the category ID before running the node.
- API permission errors: Ensure the API key used has admin privileges to update blog categories.
- Malformed input: If the category name or description contains invalid characters or exceeds allowed lengths, the API may reject the request.
- Network issues: Connectivity problems to the Lectful API endpoint will cause request failures.
To resolve these issues:
- Double-check authentication settings.
- Confirm the category ID exists in the Lectful system.
- Review API key permissions.
- Validate input data formats.
- Check network connectivity and API availability.
Links and References
- Lectful API Documentation (general reference for API endpoints and data models)
- n8n documentation on HTTP Request Node for understanding API calls
- Best practices for managing API credentials securely in n8n workflows
If you need further details on other operations or resources, feel free to ask!