Agents
Convert to workflow
Move an AI agent onto the workflow canvas when you need steps, branches or services the agent form does not offer.
An agent covers the common case: a chat, one AI Agent step and an answer. When you need more, for example a second model call, a step that runs before the agent, or an API request after it, you move the agent to the canvas as a workflow.
What an agent can hold#
Under the form, an agent is a graph of a chat trigger, one AI Agent step and a Chat Output, plus any triggers and welcome-block widgets you added in the builder. The builder only opens a flow that still has that shape. Anything else is a workflow and opens on the canvas.
Convert an agent#
- Open the agent.
- Click More actions (the three dots) in the top bar and choose Convert to workflow. The menu item is available in edit mode.
- Read the dialog: “This agent will open on the flow canvas from now on, where you can add and rewire nodes. Its settings stay as they are.”
- Click Convert to workflow.
FlowHunt saves any pending edit first, then converts both the draft and, if one exists, the published version. When it finishes you land on the canvas, and the flow moves from the Agents list to the Workflows list. Its chatbots, schedules, integrations, sessions and version history stay attached because it is the same flow.
The builder cannot convert it back
Nothing in the product turns a workflow back into an agent. Convert only when you need the canvas. The workflow keeps working as it did, and you can add and rewire steps from now on.
When the builder tells you to convert#
Sometimes an agent opens with this message: “This flow is tagged as an agent but its nodes no longer match the agent form, so there is nothing here to edit. Convert it to a workflow to open it on the canvas.” It means the graph holds a step the form has no field for, for example after someone edited the flow on the canvas or imported a file with extra steps. The Convert to workflow button on that screen does the same conversion as the menu item.
Agents that move on their own#
Flows built before agents existed were sorted when agents arrived. A flow that is exactly one chat trigger, one agent step and a chat output (plus widgets and triggers) appears in Agents. Every other flow stays in Workflows. If a flow you built on the canvas now sits under Agents and you want the canvas back, use Convert to workflow.
What changes after converting#
- Open it from Workflows in the sidebar. Opening its old agent link also lands on the canvas.
- The agent settings you had are now step settings on the canvas. The AI Agent step lists each field.
- The test chat, Preferences tab and the session list of the builder are gone. On the canvas you test with the workflow’s own playground. See testing and run logs.
If something goes wrong#
- If Convert to workflow is greyed out, a save or an earlier conversion is still running, or your role cannot change the flow.
- If the conversion fails, an error message says the update failed. Reload the page, check whether the flow is listed under Agents or Workflows, and run the conversion again if it is still an agent.