Actions12
Overview
The node integrates with an SEO content service to perform various content-related operations. Specifically, for the "Other" resource and "Spin" operation, it sends a text string to the service to be "spun" — that is, rewritten or paraphrased to create unique variations of the original content. This is useful in SEO workflows where you want to generate multiple versions of the same text to avoid duplicate content penalties or to refresh existing content.
Practical examples include:
- Automatically rewriting product descriptions to create unique listings.
- Generating alternative blog post introductions or summaries.
- Protecting certain keywords from being altered during spinning to maintain brand names or technical terms.
Properties
| Name | Meaning |
|---|---|
| Text | The input text to be spun (rewritten). |
| Protected Keywords | A CSV list of keywords that should not be changed during the spinning process. |
Output
The node outputs a JSON object containing the result of the spin operation. The exact structure depends on the external API response but generally includes the spun text. The output is accessible via the json property of the item.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the SEO content service.
- The node makes HTTP requests to the service's API endpoint
/spin. - The base URL for the API is obtained from the configured credentials.
- Proper network access to the SEO content service is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Network connectivity problems can prevent the node from reaching the API.
- Improperly formatted protected keywords (e.g., missing commas) might lead to unexpected spinning results.
- Empty or very short input text may cause the API to return errors or no meaningful output.
Error messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- HTTP request failures may show status codes like 400 or 500; check the input parameters and service status.
- Parsing errors could occur if the API returns malformed JSON; retry or contact support.
Links and References
- SEO Content Machine Official Website
- Content Spinning Concepts
- n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)