Workflow assistants
Workflow assistants are an advanced form of AI assistants. Instead of a fully open-ended conversation, the employee goes through a defined sequence of steps guided by AI. This makes it possible to standardize and automate complex, multi-step processes — consistently and repeatedly.
What is a workflow assistant?
A workflow assistant works based on a visual flowchart of nodes connected by arrows. Each node performs a specific task:
| Node type | Description |
|---|---|
| Start / End | Beginning and end point of the workflow |
| Evaluate | Analyzes the context and stores information in the workflow memory |
| Condition | Evaluates an expression and routes the flow in the right direction |
| LLM | Calls a language model for a specific task (optional: waits for input) |
| Approval | Asks a yes/no question and routes the flow based on the answer |
| Connect | Connects routes without an AI task or visible output |
| Subagent | Performs the same task in parallel for multiple items |
The workflow automatically saves its state after each step. When the employee provides input, the workflow picks up exactly where it left off — even after the browser has been closed.
How do I use a workflow assistant?
Start a new conversation and choose a workflow assistant from the list. The assistant automatically guides you through all steps. In some steps, the assistant waits for your response; in others, it continues on its own.
On the right side of the chat input, you will see the Workflow button. Click it to open a panel with all steps and their current status (waiting, active, done, waiting for input, skipped, error).
You can close the chat at any time and continue later. The workflow will resume from where you left off.
Example: In-depth research
The preset In-depth research is an example of a workflow assistant available to employees. It guides you through a thorough research process:
- Define topic — the AI asks for the research topic and desired depth
- Formulate search questions — the AI creates targeted search questions based on the topic
- Conduct research — the AI performs the research and gathers relevant information
- Generate report — the AI writes a structured research report
- Finalize — the employee reviews the report and can ask additional questions
Creating a workflow assistant
Open Assistants and choose the Workflow assistants tab. In the card at the top, click New workflow and choose Create or edit workflow with AI, Empty workflow, n8n workflow or a preset. Under Quick start, you can start a preset directly or choose Use as template.
You can also convert your own assistant: in the assistant card menu, choose Open as workflow. You will get a new, untitled draft; the original assistant remains unchanged. Review and test the proposed steps before publishing.
Workflow assistants, like regular assistants, can be shared with user groups and colleagues, also from the editor with the Share button in the toolbar. When shared with colleagues, AI-Corporate can automatically send an email notification so recipients know the workflow assistant is available.
Starting an n8n workflow
In addition to AI-driven workflow assistants, AI-Corporate can also start an n8n workflow via a webhook. An n8n workflow does not open a chat: without fields, the webhook is called directly; with fields, a form opens first. Administrators create this via Assistants → Workflow assistants → New workflow → n8n workflow.
Read the full explanation on the page n8n workflows.
General settings
When creating or editing a workflow, configure the following for the entire workflow in the settings panel:
- Model: The AI model used by all steps.
- Tools: Which tools are available (e.g. Records, Internet search). LLM steps can disable globally enabled tools per step.
- MCP servers: External integrations.
- Documents and images: Files that LLM steps can consult.
Creating a triage node
An evaluate node analyzes the user's input and stores structured values in memory (e.g. department, urgency). Configure:
- A system prompt describing what should be analyzed.
- The output schema: fields with name and type (
string,number,boolean,enum).
The stored values are available as state.fieldname in condition nodes.
Setting up a condition node
A condition node reads the workflow memory and routes the flow to the correct next step via CEL expressions:
| Desired behavior | Expression |
|---|---|
Field is true | state.approved == true |
| Field has a value | state.department == "sales" |
| Numeric threshold | state.priority > 3 |
Each branch has its own connection to the next node.
Using a connect node
A connect node does not perform an AI task itself. The node only passes the workflow on to the next step. Use this node to keep routes tidy, for example when one path skips a step and then reconnects to the main route.
A connect node must have at least one incoming and one outgoing connection. The node is not shown as a separate substantive step in the workflow progress.
Records in workflows
Enable the Records tool through the general settings and add an instruction in the system prompt of a step to save results. The employee sees the saved documents via the Records button (📄) in the toolbar.
Restoring a conversation
Are you not satisfied with the direction of the conversation? Using the restore button next to an earlier message, you can roll the workflow back to that point. All messages after that are deleted and the workflow resumes from that exact moment.
Restoring is permanent — deleted messages cannot be recovered.
Files and subagents in workflows
A workflow can ask the user to provide files, such as a source document, assessment rubric, contract, policy document, or completed form. The user can upload a new file or choose an existing file from File Management. Files added through a workflow form become available to the assistant in that chat, but are not automatically selected for regular chat questions.
New files are processed first before the workflow can continue reliably. If a required file is still being processed or has failed, the user must wait or reselect/upload the file.
The Subagent node performs the same task in parallel for multiple items. Use this when a workflow needs to process a list, for example one document, participant, employee, customer, case file, or form per execution. The subagent always receives the current item in an isolated context. Therefore, prompts should explicitly refer to the current item and avoid instructions that process multiple items at once.
Creating or editing a workflow with AI
Discuss your workflow with AI. Valid changes appear in the editor. Review and test the result before saving or publishing.