Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node operation deletes an article by its unique identifier. It is useful in scenarios where you need to programmatically remove outdated, incorrect, or unwanted articles from a content management system or database via an API. For example, if you manage a blog or knowledge base and want to automate cleanup of articles that are no longer relevant, this node can be integrated into workflows to delete those articles based on their IDs.
Properties
Name | Meaning |
---|---|
Id | ID of the requested article to delete (number) |
Output
The output JSON typically contains the response from the API after attempting to delete the article. This may include confirmation of deletion, status codes, or error messages. The exact structure depends on the API's response but generally confirms whether the deletion was successful.
No binary data output is expected for this operation.
Dependencies
- Requires an API key or authentication token configured in the node credentials to authorize requests.
- Depends on the external service's API endpoint that manages articles.
- The base URL for the API must be set in the node's credentials or configuration.
Troubleshooting
Common issues:
- Providing an invalid or non-existent article ID will likely result in an error response indicating the article was not found.
- Missing or incorrect API authentication will cause authorization errors.
- Network connectivity problems can prevent the request from reaching the API.
Error messages:
- "Article not found" — Verify the article ID is correct and exists.
- "Unauthorized" or "Authentication failed" — Check that the API key or credentials are properly configured.
- Timeout or network errors — Ensure stable internet connection and correct API endpoint URL.
Links and References
- Refer to the external API documentation for the article management service to understand the delete endpoint specifics.
- n8n documentation on creating and using API credentials for authenticated requests.