Sapo Trường Tùy Chỉnh icon

Sapo Trường Tùy Chỉnh

Quản lý trường tùy chỉnh trên Sapo

Actions72

Trang → Xóa

AI-generated

Overview

This node manages custom metafields on various resource types within the Sapo platform, such as pages, products, orders, and more. Specifically for the "Trang" (Page) resource with the "Xóa" (Delete) operation, it deletes a specified custom metafield from a given page by its ID.

Common scenarios include:

  • Removing obsolete or incorrect custom metadata from a page.
  • Cleaning up metafields during content updates or migrations.
  • Automating maintenance tasks that require deleting specific metafields based on business logic.

Example: You have a page with a custom metafield storing promotional information that is no longer relevant. Using this node, you can delete that metafield by specifying the page ID and the metafield ID.

Properties

Name Meaning
ID Tài Nguyên The numeric ID of the page ("Trang") resource from which the metafield will be deleted.
ID Trường Tùy Chỉnh The numeric ID of the custom metafield to delete from the specified page.

Output

The output JSON contains a single field indicating success:

{
  "success": true
}

This confirms that the metafield was successfully deleted from the specified page.

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Sapo platform.
  • Depends on the internal SapoApiBase class to interact with Sapo's metafield API endpoints.
  • The node expects proper configuration of the Sapo API credentials in n8n.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent page ID or metafield ID will likely cause an error.
    • Insufficient permissions or invalid API credentials may result in authentication errors.
    • Network connectivity problems can cause request failures.

  • Error messages:

    • Errors returned from the Sapo API are caught and presented as node errors unless "Continue On Fail" is enabled.
    • Typical error messages might include "Resource not found" if IDs are incorrect, or "Unauthorized" if credentials are invalid.

  • Resolution tips:

    • Verify that the page ID and metafield ID exist and are correct.
    • Ensure the API key credential has sufficient permissions.
    • Check network connectivity and API endpoint availability.
    • Enable "Continue On Fail" to handle errors gracefully in workflows.

Links and References

Discussion