openclaw - 💡(How to fix) Fix [Feature Request] feishu_bitable: native attachment upload and record deletion support [1 participants]

Fix Plan

To address the issue, we will implement two new tools: feishu_bitable_upload_attachment and feishu_bitable_delete_record.

Step 1: Implement feishu_bitable_upload_attachment Tool

• Create a new function that takes a local file path and uploads the file to Bitable using the /open-apis/drive/v1/medias/upload_all API.
• Return the file_token from the API response.

Example code:

import requests

def feishu_bitable_upload_attachment(file_path, access_token):
    url = "https://open.feishu.cn/open-apis/drive/v1/medias/upload_all"
    headers = {"Authorization": f"Bearer {access_token}"}
    params = {"parent_type": "bitable_file"}
    files = {"file": open(file_path, "rb")}
    response = requests.post(url, headers=headers, params=params, files=files)
    return response.json()["data"]["media_token"]

Step 2: Implement feishu_bitable_delete_record and feishu_bitable_batch_delete_records Tools

• Create a new function that takes a record ID and deletes the record using the Bitable API.
• Create another function that takes a list of record IDs and deletes the records in batch.

Example code:

import requests

def feishu_bitable_delete_record(record_id, access_token):
    url = f"https://open.feishu.cn/open-apis/bitable/v1/records/{record_id}"
    headers = {"Authorization": f"Bearer {access_token}"}
    response = requests.delete(url, headers=headers)
    return response.status_code == 200

def feishu_bitable_batch_delete_records(record_ids, access_token):
    url = "https://open.feishu.cn/open-apis/bitable/v1/records/batch_delete"
    headers = {"Authorization": f"Bearer {access_token}"}
    data = {"record_ids": record_ids}
    response = requests.post(url, headers=headers, json=data)
    return response.status_code == 200

Verification

To verify the fix, use the new tools to upload an attachment and delete a record. Check the API responses and the Bitable UI to ensure the operations were successful.

Extra Tips

• Make sure to handle errors and exceptions properly in the new tools.
• Consider adding logging and monitoring to track the usage and performance of the new tools.
• Update the documentation and user guides to reflect the new tools and their usage.