create_workflow. Requires Editor, Admin, or Owner in the applicable workspace and a connected OAuth session.
Accepts the complete supported TypeScript authoring source in code. Start from code returned by get_workflow, change its workflow name and desired behavior, and submit the full source. The name in that source is required. This tool parses the source; it is not a general TypeScript execution service. For a fresh agent without code, use create_workflow_from_template or create_single_prompt_agent.
Success has created: true, lifecycle draft, and version 1 published for the stored snapshot. Failures include parse_error, validation_error, graph_validation, missing_name, and trigger_path_conflict. Correct the full source before retrying. The tool does not call a model/provider or publish the agent; URL checks may resolve hostnames.
The example below is complete authoring text for a two-node agent. Send it as the code string; Agent Builder parses Workflow, startCall, and endCall directly. You do not need to install an SDK or execute this text locally.
Arguments
Example arguments
Replace sample resource IDs with IDs returned in your selected workspace.Result and errors
The schema below describes MCPstructuredContent, including the result wrapper where present. Your client may also display a text representation. Read success flags and structured errors before continuing; transport success alone does not prove the operation succeeded. Authentication, missing membership, and insufficient role can fail before a tool result is produced. See troubleshooting.
Effect: Changes state. Retry: Do not blindly repeat successful calls. Discovery annotations describe behavior; they do not grant permission or replace confirmation for consequential actions.
Input schema
Input schema
Result schema
Result schema