delete_flow

delete_flow

Delete one of this session's flows.

MCP tool	delete_flow
HTTP	POST /flows/delete

Deleting one that is not there is not an error. A flow in the shared global library is not yours to delete — every session runs those, so one vanishing mid-run would break somebody else's work — and asking is refused rather than silently ignored.

Parameters

Name	Type	Required	Default	Notes
session	string	no	—	Whose library to write to. Needed unless the request names a session another way, with the X-Session-Key header: the shared 'global' library is read-only, so a write that resolves to it is refused rather than defaulted.
name	string	yes	—

Returns

Field	Type	Notes
deleted	boolean	False when there was no such flow, which is not an error.
session	string
name	string

Errors

Status	Means
400	The request cannot succeed as sent — an unusable name, a flow that does not exist, a document that would not run, or a write aimed at the read-only shared library. Do not retry it unchanged.
401	Missing or wrong bearer token.
500	Something failed that this server did not expect.

Over MCP the same failures arrive as a tool error.

Example

MCP

delete_flow(name="…")

HTTP

curl -X POST $SELENIUM_FLOW/flows/delete \
  -H "Authorization: Bearer $TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{
    "session_id": "…",
    "name": "…"
  }'

---

← All actions · Installing · Deployment