Delete one record
Open the record (a project’s Datasets tab → a dataset → the eye icon on a row), choose Delete record, typedelete and confirm. Developers, admins and owners can do this.
Deleting a record also deletes every copy Hookie keeps of it:
- its raw submission, the body exactly as it arrived. If that submission was routed into several records, the others keep their own data;
- its deliveries, replays included, with the responses your destinations returned;
- deliveries held for it because the monthly allowance was used up;
- the workflow runs it started, with their step log and the AI calls they made. A run that is still going is stopped first;
- the output of AI triggers that ran on it. A trigger run that had not started yet will not run.
hookie:write can do the same with the delete_record tool. It is marked destructive, so your MCP client asks before running it.
Purge a dataset
On a project’s Datasets tab, open the menu on a dataset’s row, choose Purge dataset and type the dataset’s name. Owners and admins can do this. A purge deletes every record in the dataset received up to that moment, each with the copies listed above. Records that arrive while it runs are new data and are kept. A small dataset is gone before the dialog closes; a large one is deleted in the background, normally within minutes, and the dataset’s record count falls as it goes.200 with "status": "done", or 202 with "status": "running" and records_remaining. GET the same path to follow it. There is no MCP tool for this: a purge has to be typed out by a person.
Export all data
Settings → Export & closure → Export all data downloads one file with everything the workspace holds: projects, endpoints, rules, keys, destinations, sources, triggers, workflows, members, every stored record and raw submission, delivery history, workflow and AI runs, and the audit log. Owners and admins can export. The file is JSON Lines: one JSON object per line.end line is incomplete: download it again.
Secrets are never exported, not even encrypted: signing secrets, database and WebSocket credentials, Broadcast Logs keys, key and token hashes, and the secret part of each endpoint URL are left out. The header’s
omitted_columns lists exactly which fields.Close the workspace
Settings → Export & closure → Close workspace, then type the workspace’s slug. Only the owner can close a workspace, and only from the console: a connected agent cannot. Closing does three things:1
Cancels the subscription, now
A paid plan is cancelled in Stripe immediately, so nothing more is charged. If Stripe cannot cancel it, nothing else happens and the console says so.
2
Suspends the workspace, now
Endpoints and ingest keys answer
403 with reason: "workspace_suspended", nothing is delivered, schedules and sources stop, and settings are read-only. Members can still sign in, read everything and export.3
Deletes everything after 14 days
Every project, record, raw submission, delivery, workflow run, AI call, setting, secret, key and membership is permanently deleted. The audit log is kept for its own retention (at least a year), and the workspace’s name is removed.