SEO Content Machine icon

SEO Content Machine

SEO Content Machine node

Overview

This node integrates with the SEO Content Machine API to manage "Task" resources, specifically allowing users to delete a task by its ID. The "Delete Task" operation sends a request to remove a specified task from the SEO Content Machine system.

Common scenarios for this node include automating cleanup of tasks that are no longer needed, managing task lifecycle in bulk workflows, or integrating task deletion as part of a larger content automation pipeline.

For example, after processing and exporting content generated by a task, you might use this node to delete the task automatically to keep your project organized.

Properties

Name Meaning
Task The identifier of the task to delete. You can select the task either from a searchable list of existing tasks or specify the task ID directly as a string.

The "Task" property supports two modes:

  • From List: Search and select a task from existing tasks.
  • By ID: Enter the task ID manually (must be alphanumeric, dashes, or underscores, minimum 2 characters).

Output

The node outputs JSON data representing the response from the SEO Content Machine API after attempting to delete the specified task. This typically includes confirmation of deletion or error details if the operation failed.

The output is structured as:

{
  "json": {
    // API response fields indicating success or failure of the delete operation
  }
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the SEO Content Machine service configured in n8n.
  • The node makes authenticated HTTP requests to the SEO Content Machine API endpoint.
  • Network access to the SEO Content Machine API base URL is necessary.

Troubleshooting

  • Invalid Task ID: If the task ID does not match the required pattern (alphanumeric, dashes, underscores, at least 2 characters), the node will reject it before making the API call.
  • Task Not Found: If the specified task ID does not exist, the API may return an error indicating the task was not found.
  • Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
  • Network Issues: Connectivity problems to the SEO Content Machine API endpoint will cause request failures.
  • API Rate Limits: Excessive requests may be throttled; handle such errors by retrying after some delay.

If the node encounters an error during execution, it will either stop the workflow or continue based on the "Continue On Fail" setting, providing error details in the output.

Links and References

Discussion