AvantGuard - WebhookSite icon

AvantGuard - WebhookSite

AvantGuard - WebhookSite

Actions100

Overview

This node operation updates an existing article by its unique identifier. It allows users to modify various attributes of the article such as its content, name, sharing settings, and associations with folders or companies. This is useful in scenarios where articles need to be programmatically maintained or updated in bulk, for example, updating product documentation, knowledge base articles, or blog posts within a content management system.

Practical examples include:

  • Automatically updating the content of help articles when new information becomes available.
  • Changing article metadata like the name or folder association based on organizational changes.
  • Enabling or disabling public sharing of articles dynamically.

Properties

Name Meaning
Id The unique numeric identifier of the article to update (required).
Additional Body Fields Optional fields to update on the article:
- Content The main textual content of the article.
- Name The title or name of the article.
- Enable Sharing Boolean flag indicating if the article should have a public URL accessible without authentication.
- Folder Id Numeric ID to associate the article with a specific folder.
- Company Id Numeric ID to associate the article with a specific company.

Output

The node outputs JSON data representing the updated article object after the PUT request completes successfully. This typically includes all the article's properties reflecting the new state post-update.

If the node supports binary data output (not indicated here), it would represent any file attachments or media related to the article, but this operation focuses on JSON body updates only.

Dependencies

  • Requires an API key credential for authenticating requests to the external service managing articles.
  • The node uses a base URL configured in credentials to send HTTP PUT requests.
  • No additional external dependencies are indicated beyond the API connection.

Troubleshooting

  • Invalid Id: If the provided article Id does not exist, the API will likely return a "Not Found" error. Verify the Id before running the node.
  • Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key or token is correctly configured.
  • Validation Errors: Providing invalid data types or missing required fields may result in validation errors from the API. Double-check property values, especially for numeric fields.
  • Network Issues: Connectivity problems can cause timeouts or failed requests. Confirm network access to the API endpoint.

Links and References

  • Refer to the external API documentation for detailed information on article resource endpoints and field definitions.
  • Consult n8n documentation on how to configure API credentials and use HTTP request nodes for similar operations.

Discussion