Sapo Blog icon

Sapo Blog

Manage Sapo blogs and articles

Actions33

Overview

This node integrates with the Sapo blogging platform to manage blogs, articles, and comments. Specifically, the "Kiểm Tra Spam" (Spam Check) operation allows users to verify whether a particular comment on an article is considered spam. This can be useful for content moderation workflows where automated or manual spam detection is required to maintain the quality of user interactions.

Practical examples include:

  • Automatically checking new comments on blog articles to filter out spam before publishing.
  • Integrating spam checks into a moderation queue to flag suspicious comments.
  • Using the node as part of a larger automation that notifies moderators or deletes spam comments.

Properties

Name Meaning
ID Blog The unique numeric identifier of the blog containing the article and comment.
ID Bình Luận The unique numeric identifier of the comment to check for spam. Required for this operation.

Output

The node outputs a JSON object representing the result of the spam check for the specified comment. The exact structure depends on the response from the Sapo API but generally includes details indicating whether the comment is flagged as spam or not.

If the operation succeeds, the output JSON will contain the spam check result data. If the operation fails and "Continue On Fail" is enabled, the output will contain an error message describing the failure.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the Sapo API via an API key credential configured in n8n.
  • The node depends on the SapoApiBase class which handles communication with the Sapo blogging platform.
  • Proper permissions on the Sapo account are necessary to perform spam checks on comments.

Troubleshooting

  • Common issues:

    • Invalid or missing blog ID, article ID, or comment ID parameters will cause errors.
    • Network or authentication failures when connecting to the Sapo API.
    • Attempting to check spam on a non-existent comment or article.

  • Error messages:

    • Errors returned from the Sapo API will be surfaced with their message and stack trace if "Continue On Fail" is disabled.
    • Typical errors include "Comment not found", "Unauthorized access", or "Invalid parameters".

  • Resolutions:

    • Verify that all required IDs are correctly set and correspond to existing resources.
    • Ensure the API credentials are valid and have sufficient permissions.
    • Enable "Continue On Fail" to handle errors gracefully within workflows.

Links and References

Discussion