The Scenario
The handoff email from the RevOps analyst who left last month included a single line: "there's a cleanup sheet somewhere with the cancelled Leexi events that need to be removed, I never got to it." You found it. Eighty-three event UUIDs in Column A — cancelled calls, duplicates, test events created during an integration experiment. They're cluttering the workspace and your new Leexi admin has no idea where they came from.
Someone told you this would take twenty minutes. They've never deleted 83 things in a web UI one at a time.
The bad version:
- Open Leexi, navigate to the meeting events section, search for the first UUID, open the event, click delete, confirm
- Return to the sheet, find the next UUID, switch back to Leexi, search again
- Realize at event 40 that Leexi's search doesn't accept UUIDs in the format you have — you need to adapt the lookup midstream
The person who built the cleanup sheet is gone. The context for why these 83 events exist is gone. What's left is the work.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent that lives inside your Google Sheet. It reads the UUID list in Column A, calls the Leexi delete endpoint for each one, and writes the result — "deleted" or the error — back into Column B.
Delete every Leexi meeting event whose UUID appears in Column A of this sheet — there are about 80 rows — and write 'deleted' or the error into Column B
What You Get
- Column B: "deleted" for every successfully removed event
- Column B: the API error message for any UUID that fails (event not found, already deleted, permission error)
- All 83 rows processed in one pass — no manual tracking of which ones are done
What If the Data Is Not Quite Ready
Some UUIDs in Column A have formatting issues — extra spaces or line breaks from a paste
Delete Leexi events for each UUID in Column A, trim whitespace before calling the API, write 'deleted' into Column B or the error if deletion fails
You only want to delete rows where Column C says "Cancelled" — other rows should be skipped
The sheet has 120 rows but only rows marked Cancelled should be removed. Others might still be valid.
Delete Leexi meeting events only for rows where Column C says 'Cancelled' — use the UUID from Column A, write 'deleted' or the error into Column D, leave all other rows untouched
You want to log the deletion timestamp alongside the result
The compliance team wants a record of when each event was removed, not just whether it was.
Delete each Leexi event UUID in Column A, write 'deleted' or the error into Column B, and write the current timestamp in ISO format into Column C for every row that was successfully deleted
Trim UUIDs, filter to Cancelled rows, delete, and log results with timestamps — one pass
For all rows where Column C says 'Cancelled', trim whitespace from the UUID in Column A, delete the corresponding Leexi meeting event, write 'deleted' or the error into Column D, and write the deletion timestamp into Column E for successful deletions
One pass. The workspace is clean. The log is there for the compliance team.
Try It
Get the 7-day free trial of SheetXAI and open your cleanup sheet, then ask it to process the full UUID list against Leexi in one pass. For creating new events from a schedule, see Bulk Create Leexi Meeting Events From a Google Sheet, or return to the Leexi overview.