Skip to main content

Chat: turn a conversation into a workflow

When a conversation has done something you will want to repeat, ask the agent in the composer to make it a workflow; there is no button for it. Read this once the chat has worked through the steps you want to keep.

Steps​

  1. Type a request such as Convert this to a workflow and press Enter. Add what you want changed: a step to leave out, a name to use.
  2. The agent runs it like any turn. When the workflow exists, a WORKFLOW CREATED tile appears in the thread with the workflow's name and a line such as "v1 · 4 steps · 3 connections" (saved version, steps, dependencies).
  3. Click Open workflow. Studio loads the workflow's view screen in the Workflows area as a full page load, with its versions, Activate and Run now.
  4. Click Create Version in Workflow Versions to open the builder, then check each node's objective against what the chat did, turn on approval where you need sign-off, expose the run parameters you want to vary, and save; each save is a new version. See Workflows: build.
  5. Activate the version, then run or schedule it and follow it from the Inbox. Until a version is active the workflow does nothing. See Workflows: run, schedule, approve.

What you should see​

The tile stays in the conversation, saved with the agent's message, one per workflow created. The version on it is the one saved at creation; later edits create versions in the Workflows area and the tile does not update.

Notes​

  • There is no reverse path: a workflow cannot be run, mentioned or picked from chat. Workflows run from the Workflows area and, on a governed deployment, from outside through programmatic access.
  • Steps you cancelled in the chat, and the copies made when a step was created again, go into the workflow too, unless you name them in what to leave out. Delete any extra step in the builder.
  • What you told a step during the chat, such as a Send back note, is not carried into its objective, and a step you re-instructed keeps only its last instruction. Add what the step needs to its objective in the builder before you activate.
  • Research steps are not tied to the periods the chat used, so a run can return different years or a different table layout. Put an as-of date in the objective or make it a run parameter.
  • The agent decides the steps and connections from the plan it ran. A workflow run works in its own folder, not the conversation's, so a step that relied on a chat file may fail: read the failing node in the run detail and add the input as a run parameter or an earlier step.
  • No tile appeared: the agent answered without creating one. Ask again plainly, for example "create a workflow with the steps you just ran".
  • A tile restored after a reload shows steps but no connections; the connections are in the builder. Open workflow landing on the Workflows list means the workflow was deleted; search by name.