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

Bài Viết → Xóa

AI-generated

Overview

This node manages custom metafields on various resource types within the Sapo platform, such as articles, blogs, collections, customers, orders, pages, products, and product variants. Specifically, for the Bài Viết (Articles) resource with the Xóa (Delete) operation, it deletes a specified custom metafield from an article.

Common scenarios include:

  • Removing obsolete or incorrect custom metadata fields from articles.
  • Cleaning up metafields that are no longer needed after content updates.
  • Automating maintenance of article metadata in bulk workflows.

Example use case:

  • You have an article with a custom metafield storing outdated promotional information. Using this node, you can delete that metafield by specifying the article ID and the metafield ID to keep your data clean.

Properties

Name Meaning
ID Tài Nguyên The numeric ID of the article (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 article.

Output

The output JSON contains a single field indicating success:

{
  "success": true
}

This confirms that the metafield was successfully deleted from the article.

No binary data is output by this operation.

Dependencies

  • Requires an active connection to the Sapo API via an API key credential configured in n8n.
  • The node depends on the internal SapoApiBase class to interact with the Sapo metafields API endpoints.
  • Proper permissions on the Sapo account to delete metafields on articles are necessary.

Troubleshooting

  • Error: Invalid or missing resource ID or metafield ID
    Ensure that both the article ID and metafield ID are correctly provided and correspond to existing entities in Sapo.

  • API authentication errors
    Verify that the API key credential is valid and has sufficient permissions.

  • Metafield not found or already deleted
    If the metafield ID does not exist for the given article, the deletion will fail. Confirm the IDs before running the node.

  • Network or API downtime issues
    Temporary connectivity problems may cause failures; retrying later might resolve these.

If the node is set to continue on failure, errors will be returned in the output JSON under an error field with the error message.

Links and References

Discussion