Overview
This node, named "Impetus," is designed to send article data to a specified API endpoint for blog post creation. It is useful in scenarios where users want to automate the publishing of articles by pushing content directly from n8n workflows to a blogging platform or CMS via an API. For example, after gathering or generating article content within a workflow, this node can be used to submit that content to a remote service to create new blog posts without manual intervention.
Properties
| Name | Meaning |
|---|---|
| API URL | The URL of the API endpoint where the articles will be sent. |
| Título | The title of the article to be created. |
| Slug | The slug (URL-friendly identifier) for the article. |
| Conteúdo | The HTML content/body of the article. |
| SEO Description | The SEO description metadata for the article. |
| Keywords | Comma-separated keywords associated with the article for SEO purposes. |
Output
The node outputs JSON data representing the response from the API after attempting to create the article. This typically includes confirmation details or error messages returned by the API. There is no indication that the node handles binary data output.
Dependencies
- Requires access to the target API specified by the user through the "API URL" property.
- The API must accept POST requests with JSON payloads containing the article data.
- No explicit mention of authentication mechanisms; if the API requires authentication, it must be handled externally or configured separately in the workflow.
Troubleshooting
- Common issues:
- Incorrect or unreachable API URL leading to connection errors.
- Missing required fields such as title, slug, or content causing API validation failures.
- API rejecting requests due to missing authentication or incorrect headers.
- Error messages:
- Network errors or timeouts indicate connectivity problems with the API endpoint.
- API response errors usually contain details about which field is invalid or missing; ensure all required properties are correctly filled.
- Resolution tips:
- Verify the API URL and network accessibility.
- Confirm that all required input properties are provided and correctly formatted.
- If the API requires authentication, ensure credentials or tokens are properly included in the request headers or managed elsewhere in the workflow.
Links and References
- No external links provided in the source code.
- For further guidance, consult the documentation of the target API to understand expected request formats and authentication requirements.