Actions12
Overview
The "SEO Content Machine" node integrates with an external SEO content management API to manage and control SEO-related tasks. Specifically, the Task - Start operation initiates a previously created SEO task by sending a start command to the API.
This node is useful in workflows where automated control over SEO content generation or processing tasks is needed. For example, after creating or configuring a task, you can use this node to trigger its execution programmatically, enabling seamless automation of SEO content pipelines.
Practical examples:
- Automatically starting a content generation task once all required parameters are set.
- Integrating SEO task execution into larger marketing automation workflows.
- Triggering SEO data collection or analysis tasks on demand.
Properties
| Name | Meaning |
|---|---|
| Task | The specific SEO task to start. You can select it from a searchable list or provide its ID. |
Output
The node outputs a JSON object representing the response from the SEO content machine API for the start task request. This typically includes confirmation of the task start status and any relevant metadata returned by the API.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"status": "success",
"taskId": "abc123",
"message": "Task started successfully"
}
Dependencies
- Requires an API key credential for authenticating with the SEO Content Machine API.
- The node uses HTTP requests authenticated via this credential to communicate with the external service.
- No additional environment variables or configurations are explicitly required beyond the API credential setup.
Troubleshooting
Common issues:
- Invalid or missing task ID: Ensure the task ID provided exists and matches the expected format.
- Authentication failures: Verify that the API key credential is correctly configured and has necessary permissions.
- Network errors: Check connectivity to the SEO Content Machine API endpoint.
Error messages:
- Errors thrown by the node will include context about the failing item index.
- If the API returns an error (e.g., task not found or unauthorized), the node will throw an error unless "Continue On Fail" is enabled.
Resolution tips:
- Double-check the task selection input; use the list mode to avoid typos.
- Confirm API credentials are valid and active.
- Enable "Continue On Fail" during testing to isolate problematic inputs without stopping the entire workflow.
Links and References
- SEO Content Machine API Documentation (hypothetical link for reference)
- n8n HTTP Request Node documentation for understanding authenticated API calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/