SEO Content Machine icon

SEO Content Machine

SEO Content Machine node
Join our community

Actions12

Overview

The node integrates with the SEO Content Machine API to manage and interact with "Task" resources. Specifically, for the Status operation on a Task, it retrieves the current status of a specified task by its ID. This is useful in workflows where you need to monitor or check the progress or state of content generation or other automated tasks managed by SEO Content Machine.

Practical examples include:

  • Checking if a content generation task has completed before proceeding to the next step.
  • Monitoring task states to trigger alerts or conditional logic in automation.
  • Integrating task status checks into larger content marketing or SEO workflows.

Properties

Name Meaning
Task The identifier of the task to check the status for. Can be selected from a list of existing tasks or provided directly by ID.

The "Task" property supports two modes:

  • From List: Select a task from a searchable list.
  • By ID: Enter a valid task ID manually (must match regex [a-zA-Z0-9\-_]{2,}).

Output

The output JSON contains the response from the SEO Content Machine API endpoint /task/status/{taskId}, which provides the current status details of the specified task. The exact structure depends on the API but typically includes fields such as task state, progress, timestamps, and any relevant metadata about the task's execution.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the SEO Content Machine API.
  • The node uses HTTP requests authenticated via this credential to communicate with the SEO Content Machine service.
  • Proper configuration of the API credential in n8n is necessary for successful operation.

Troubleshooting

  • Invalid Task ID: If the task ID does not conform to the expected format, the node will throw a validation error. Ensure the ID matches the pattern [a-zA-Z0-9\-_]{2,}.
  • API Authentication Errors: If the API key is missing, invalid, or expired, the node will fail to authenticate. Verify that the API credential is correctly set up and active.
  • Task Not Found: If the specified task ID does not exist, the API may return an error or empty result. Confirm the task ID is correct and the task exists.
  • Network Issues: Connectivity problems can cause request failures. Check network access and API endpoint availability.
  • To continue processing despite errors, enable the "Continue On Fail" option in the node settings.

Links and References

Discussion