Describe the workflow you want and Chat builds it. Reference an existing workflow and Chat reads its current structure before editing, so you do not need to restate the canvas.
Creating Workflows
Give Chat 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"
Chat creates the workflow, chooses appropriate native blocks, wires the connections, and opens the canvas in the resource panel.
Chat then checks the saved workflow and, when a test run is safe, runs the draft and reports the result. A run executes every block it reaches for real. A test run is safe when every account it needs is connected and nothing in the workflow changes anything, inside the workspace or outside it: no table row, document, file, knowledge base entry or memory written or deleted, no message or email sent, no request other than a GET, and no other workflow started. Otherwise Chat does not run it, and says what it could not test and what to connect or provide first.
SteelEngine enforces this before a draft runs. The run checks each enabled block in the copy of the draft it is about to execute. If any block could change something, Chat cannot run the draft on its own: the run pauses for your approval, and the prompt says that the run is real. Ask Chat to test the workflow when you want that run. A block counts as changing nothing only when that is certain, so a block the check cannot classify also pauses the run. An integration step counts as a read only when its operation is verified as read-only. A name such as Get or List is not enough, because some of those operations save a file. SteelEngine's own table, knowledge base and memory reads count; parsing a file does not, because it stores the file. Running a deployed workflow is not affected.
Your approval applies to the saved workflow and its variables when Chat asked. For a partial run, it also applies to the cached inputs from the selected execution. If any of that data changes before the run starts, Chat needs a new approval. Answer a pending approval in the thread where it appeared. If the response fails after you answer, Retry sends your answer again instead of starting the turn over. Retrying a pending approval uses the same execution ID. It picks up a run that already started, and it finishes starting a run whose first attempt stopped part-way.
Chat asks for approval to run drafts containing Function blocks because their custom code can have side effects. For simple data transformations, native blocks such as JSON Mapper can run automatically when the rest of the draft is safe.
On a source-control branch, Chat does not test its changes, because a run executes the main draft or the deployed version, not the branch copy.
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"
Chat should preserve what already works, make the smallest safe edit, and validate the resulting workflow shape.
Running and Debugging
Ask Chat 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.
Workflow metadata reads can include the saved workflow document, including block configuration and code. For a particular failure, attach the execution log so Chat receives that execution's ID. After you undeploy a workflow, its draft and deployment history remain available, but it has no active deployed state until you deploy again.
Resuming a Paused Workflow
Ask Chat to list a workflow's pending Human in the Loop approvals, then identify the execution and approval you want to resume. A resume must belong to that workflow and execution; an approval from another run cannot be used in its place. If a run has multiple pause points, name the one you intend to answer.
Chat asks for your approval before it resumes a run. The prompt shows the answer Chat will give to the waiting step. Your approval covers that one step: if someone answers it first, nothing is resumed. Chat submits the answer shown in the prompt or nothing. If a different answer from someone else is already waiting to be carried out for that step, Chat leaves it in place and tells you. When several steps of the run are waiting, Chat must name one before it can ask you.
Approval summaries include the display data, form, and status without exposing the saved execution snapshot. For direct review, open the approval from Notifications → Waiting on you. Once decided, the review shows the decision, who submitted it, and when.
Deploying
Chat can deploy workflows as:
| Deployment type | What it creates |
|---|---|
| API | A callable HTTP endpoint |
| Hosted Chat | A generated chat interface for one workflow |
| MCP tool | A workflow exposed as an MCP tool |
| A2A agent | A workflow published as an agent other agents can call (see A2A Agents) |
Ask: "Deploy the invoice workflow as an API and generate an API key." Deploying, redeploying, and reverting to an earlier deployment version each ask for your approval in the thread.
Hosted Chat provides a simple interface for one Workflow. Use Apps when you need a customizable, multi-page dashboard, portal, or internal tool that combines data views and multiple Workflow actions.
Organizing
Chat 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"