SEO Content Machine icon

SEO Content Machine

SEO Content Machine node
Join our community

Actions12

Overview

This node integrates with the SEO Content Machine API to manage and control SEO-related tasks programmatically. Specifically, the "Abort" operation under the "Task" resource allows users to stop an ongoing task by its ID. This is useful in scenarios where a task is no longer needed or if it was started by mistake, helping to save resources and avoid unnecessary processing.

Practical examples include:

  • Automatically aborting content generation tasks that exceed a certain time limit.
  • Stopping duplicate or erroneous SEO tasks triggered by other workflows.
  • Managing task lifecycle dynamically based on external conditions.

Properties

Name Meaning
Task The identifier of the task to abort. It can be selected from a searchable list of existing tasks or provided directly by its ID string.

The "Task" property supports two modes for specifying the task:

  • From List: Search and select from existing tasks.
  • By ID: Provide the task ID manually (must match the pattern [a-zA-Z0-9\-_]{2,}).

Output

The node outputs a JSON object representing the response from the SEO Content Machine API after attempting to abort the specified task. The exact structure depends on the API but typically includes status information about the abort request.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the SEO Content Machine API.
  • The node uses HTTP GET requests to communicate with the API endpoint /task/abort/{taskId}.
  • Proper configuration of the API credential within n8n is necessary for successful execution.

Troubleshooting

  • Invalid Task ID: If the provided task ID does not match the required pattern or does not exist, the API may return an error. Ensure the task ID is correct and exists.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up.
  • Network Issues: Connectivity problems with the SEO Content Machine API endpoint can cause request failures. Check network access and API availability.
  • API Rate Limits: Excessive requests might be throttled by the API. Implement retry logic or reduce request frequency if needed.

Common error messages are passed through from the API and wrapped as node errors. Enabling "Continue On Fail" allows the workflow to proceed despite individual item errors.

Links and References

Discussion