Workflows

Describe the workflow you want and Mothership builds it. Reference an existing workflow and Mothership reads its current structure before editing, so you do not need to restate the canvas.

Creating Workflows

Give Mothership the trigger, the work to perform, any integrations involved, and the expected output:

• "Build a workflow that takes a URL, scrapes the page, summarizes it, and sends the summary to Slack"
• "Create a webhook workflow that extracts invoice data from a PDF and writes it to the billing table"
• "Build a lead enrichment workflow that takes an email, looks up the company, scores the fit, and writes the record to the leads table"

Mothership creates the workflow, chooses appropriate native blocks, wires the connections, and opens the canvas in the resource panel.

Editing Existing Workflows

Open a workflow with @workflow-name, the + menu, or the resource panel, then describe the change:

• "Add a condition that routes low-confidence records to manual review"
• "Replace the summarizer model with a faster model"
• "Remove the function block and connect the email parser to the issue writer"

Mothership should preserve what already works, make the smallest safe edit, and validate the resulting workflow shape.

Running and Debugging

Ask Mothership to run a workflow with test inputs or inspect a failed run:

• "Run the invoice processor with this PDF"
• "Show me the last 10 runs of the CRM sync"
• "Why did the extractor block fail yesterday?"
• "Debug the last failed run and fix the workflow"

It can read execution summaries, block outputs, errors, and timing before proposing or applying a fix.

Deploying

Mothership can deploy workflows as:

Ask: "Deploy the invoice workflow as an API and generate an API key."

Organizing

Mothership can rename workflows, create folders, move workflows between folders, and clean up old resources:

• "Create a folder called Data Pipelines"
• "Move the billing workflow into Finance"
• "Rename test_v2 to lead-scorer"
• "Delete the old prototype workflow"