Lectful Central icon

Lectful Central

Interact with the Lectful Central API for admin operations

Overview

This node integrates with the Lectful Central API to perform administrative operations related to feature management, among many other resources. Specifically, for the Delete Feature operation under the Feature Management resource, it allows users to delete a specific feature by its ID.

This is useful in scenarios where you need to programmatically manage features associated with plans or products, such as removing deprecated or obsolete features from your system. For example, if a feature is no longer offered or needs to be removed due to policy changes, this operation can automate that deletion process within an n8n workflow.

Properties

Name Meaning
Authentication Mode Choose how to authenticate with the Lectful Central API:
- Use Stored Credentials
- Manual Configuration (provide base URL and API key manually)
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
Feature ID The numeric ID of the feature to delete (required)

Output

The node outputs the JSON response returned by the Lectful Central API after attempting to delete the specified feature. Typically, this will be an object indicating success or failure of the deletion request.

  • The output is structured as an array of items, each containing a json property with the API response.
  • No binary data output is produced by this operation.

Example output snippet (conceptual):

[
  {
    "json": {
      "message": "Feature deleted successfully"
    }
  }
]

Or, in case of error:

[
  {
    "json": {
      "error": "Feature not found"
    }
  }
]

Dependencies

  • Requires access to the Lectful Central API.
  • Requires either:
    • Stored credentials configured in n8n with a valid base URL and API key, or
    • Manual configuration providing the base URL and API key directly in the node parameters.
  • The node uses HTTP Bearer token authentication with the provided API key.
  • No additional external dependencies are required.

Troubleshooting

  • Missing or invalid credentials:
    If neither stored credentials nor manual configuration is properly set, the node will throw an error indicating missing or invalid credentials. Ensure that either stored credentials are configured correctly or manual base URL and API key are provided.

  • Base URL or API key missing in manual mode:
    When using Manual Configuration mode, both Base URL Override and API Key Override must be provided; otherwise, the node throws an error.

  • Feature ID not provided or invalid:
    The Feature ID parameter is required. Omitting it or providing an invalid ID will cause the API call to fail.

  • API errors:
    Errors returned by the Lectful Central API (e.g., feature not found, permission denied) will be included in the node output as error messages. Review the API response for details.

  • Continue on Fail:
    If enabled, the node will continue processing subsequent items even if one item fails, returning error details in the output JSON.

Links and References


If you need summaries for other operations or resources, feel free to ask!

Discussion