Lectful icon

Lectful

Interact with the VIPay Lectful API

Actions88

Overview

This node integrates with the Lectful API to manage blog-related administrative tasks, specifically including the deletion of blog categories in an admin context. It allows users to delete a specified blog category by its ID, which is useful for maintaining and organizing blog content by removing outdated or irrelevant categories.

Common scenarios where this node is beneficial include:

  • Automating blog maintenance workflows where categories need to be programmatically removed.
  • Integrating with other systems to synchronize blog taxonomy changes.
  • Managing blog content structure in bulk or via automated processes without manual intervention.

Practical example:

  • An admin wants to delete a blog category identified by a specific ID after archiving related posts. This node can be used in an n8n workflow to send the delete request to the Lectful API, ensuring the category is removed from the system.

Properties

Name Meaning
Authentication Mode Choose how to authenticate with the Lectful API: either using 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 Configuration mode.
API Key Override Optional API key to override the credential setting, used in Manual Configuration mode.
Category ID The ID of the blog category to delete (required).

Output

The node outputs the JSON response returned by the Lectful API after attempting to delete the specified blog category. This typically includes confirmation of deletion or error details if the operation failed.

No binary data output is produced by this operation.

Example output JSON structure might look like:

{
  "success": true,
  "message": "Category deleted successfully"
}

or in case of failure:

{
  "error": "Category not found"
}

Dependencies

  • Requires access to the Lectful API.
  • Requires either stored API credentials configured in n8n or manual entry of the base URL and API key.
  • The API key must have sufficient permissions to perform administrative blog category deletions.

Troubleshooting

  • Missing or invalid credentials: If neither valid stored credentials nor manual overrides are provided, the node will throw an error indicating that authentication information is required.
  • Base URL or API key missing in manual mode: When using manual configuration, both the base URL override and API key override must be provided; otherwise, an error is thrown.
  • Invalid Category ID: Providing an incorrect or non-existent category ID will result in an API error, typically indicating the category was not found.
  • API permission errors: Insufficient permissions on the API key may cause authorization failures.
  • Network issues: Connectivity problems to the Lectful API endpoint will cause request failures.

To resolve these issues:

  • Ensure credentials are correctly set up or manual parameters are properly filled.
  • Verify the category ID exists before attempting deletion.
  • Confirm the API key has admin rights for blog management.
  • Check network connectivity and Lectful API status.

Links and References

Discussion