Skip to main content
Glama

Writ Cloud

Save a session as a workflow

writ_browser_save
Destructive

Saves the open browser session as a clean, replayable workflow and closes the browser. Everything composed with writ_browser_compose is materialized: named api functions become api_call steps with the auth function first, declared inputs become the workflow's parameters, explicit steps land at their position. The saved workflow is active immediately: it runs on demand through writ_run_workflow (function_name calls one function) or its own run_ tool (writ_pin_workflow_tool) at zero AI cost, can be scheduled with writ_set_schedule, exposed as a REST endpoint with writ_expose_workflow_api, and documented at GET /api/v1/workflows/{id}/api-docs. A session bound to a build (writ_website_to_api guided) settles that build. The save is refused, with the reasons, when a step or function references something no run could resolve; the browser then stays open. A workflow is only as sound as the task's run on the live page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoShort workflow name (defaults to the goal).
keep_openNoLeaves the browser open after saving (default false: saving closes it).
session_idYes
descriptionNo
allow_no_dataNoSaves a workflow that yields no data (navigation/actions only) on purpose. Off by default: a save with no data step and no defined function is refused for an API build (no define_function or extract yet) and warned for a task recording: such a workflow runs green and returns nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.