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

Khách Hàng → Xóa Hàng Loạt

AI-generated

Overview

This node manages custom metafields on various resource types within the Sapo platform, specifically supporting operations like creating, retrieving, updating, deleting, counting, validating, and bulk deleting metafields. For the Khách Hàng (Customers) resource with the Xóa Hàng Loạt (Bulk Delete) operation, it allows users to delete multiple metafields associated with a specific customer resource ID based on optional filtering criteria.

Typical use cases include cleaning up or removing multiple custom fields from customer records in bulk, for example, when certain metadata is no longer relevant or needs to be reset across many entries. This can save time compared to deleting metafields one by one.

Properties

Name Meaning
ID Tài Nguyên The numeric ID of the customer resource whose metafields are targeted for bulk deletion.
Thông Tin Bổ Sung Additional optional filters to narrow down which metafields to bulk delete. Options include:
- Namespace: Filter metafields by their namespace string.
- Key: Filter metafields by their key string.
- Tạo Sau (Created After): Filter metafields created after this date/time.
- Tạo Trước (Created Before): Filter metafields created before this date/time.

Output

The output JSON contains the result of the bulk delete operation. It typically includes information about the success status or details of the deleted metafields. The exact structure depends on the underlying API response but generally confirms whether the bulk deletion was successful.

Example output snippet:

{
  "success": true
}

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Sapo API via an API authentication credential.
  • The node depends on the SapoApiBase class to interact with the metafields endpoints.
  • Proper configuration of the API credentials in n8n is necessary for authentication and authorization.

Troubleshooting

  • Common Issues:

    • Providing an invalid or non-existent customer resource ID will cause the operation to fail.
    • Incorrect filter values in "Thông Tin Bổ Sung" may result in no metafields being matched or deleted.
    • Network or authentication errors if the API key or credentials are misconfigured.

  • Error Messages:

    • Errors returned from the API will be surfaced as node execution errors unless "Continue On Fail" is enabled.
    • Typical error messages might include "Resource not found," "Unauthorized," or "Invalid parameters."

  • Resolutions:

    • Verify the customer ID exists and is correct.
    • Double-check additional filter fields for valid formats and values.
    • Ensure API credentials are correctly set up and have sufficient permissions.

Links and References

Discussion