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 for the "Bài Viết" (Article) resource and the "Lấy Bình Luận" (Get Comment) operation, it retrieves a specific comment on an article within a blog.

Common scenarios include:

  • Fetching user comments on a particular article for moderation or display.
  • Integrating blog comment data into workflows for analysis or notifications.
  • Automating content management tasks related to article comments.

Example use case: Automatically retrieve a comment by its ID from a specified article and blog to analyze sentiment or trigger follow-up actions.

Properties

Name Meaning
ID Blog The unique numeric identifier of the blog containing the article.
ID Bài Viết The unique numeric identifier of the article within the blog.
ID Bình Luận The unique numeric identifier of the comment to retrieve from the article.

Output

The node outputs a JSON object representing the requested comment's details. This typically includes fields such as author, email, body text, IP address, timestamps, and other metadata associated with the comment.

No binary data output is involved in this operation.

Example output structure (simplified):

{
  "id": 123,
  "author": "John Doe",
  "email": "john@example.com",
  "body": "Great article!",
  "ip": "127.0.0.1",
  "created_at": "2023-01-01T12:00:00Z",
  ...
}

Dependencies

  • Requires an API key credential for authenticating with the Sapo platform.
  • The node depends on the SapoApiBase class to interact with the Sapo API endpoints.
  • Proper configuration of the API credentials in n8n is necessary for successful requests.

Troubleshooting

  • Common issues:

    • Invalid or missing blog, article, or comment IDs will cause errors.
    • Network or authentication failures due to incorrect API credentials.
    • Attempting to fetch a comment that does not exist or has been deleted.

  • Error messages:

    • Errors returned from the Sapo API are surfaced with their message and stack trace.
    • If the node is set to continue on failure, errors appear in the output JSON under an error field.

  • Resolutions:

    • Verify all IDs are correct and correspond to existing resources.
    • Ensure API credentials are valid and have sufficient permissions.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion