Workflows

​

Overview

Workflows in nuwacom automate recurring processes. Required steps are defined once, then executed in sequence. Agents, logic, integrations, and external tools can run within one workflow. A workflow can be described in chat. nuwacom then generates a multi-step workflow that connects actions, logic, and external systems. The visual editor keeps every step adjustable, extendable, and transparent. Suggested prompts provide a starting point for common workflow scenarios. They help explore recurring use cases and turn them into editable workflow structures.

​

Key benefits

• Automate recurring processes with defined steps.
• Combine agents, logic, integrations, and external tools in one workflow.
• Reuse results from earlier workflow steps in later steps.
• Add manual approvals before a workflow continues.
• Create reusable outputs such as documents, email drafts, designed documents, and slide decks.

​

When to use workflows

Workflows are suitable when tasks repeat regularly, follow a clear structure, or require several systems to work together. Typical use cases include creating and reviewing reports, monitoring incoming data, sending automated emails, processing customer inputs, conducting research, and generating summaries. Use tasks for ad hoc work in chat. Use workflows for recurring, automated processes with fixed steps.

---

​

Components of a workflow

​

Triggers

Triggers start a workflow. A workflow can start manually or automatically when a defined event occurs. Common trigger types include manual triggers, form submissions, and scheduled triggers. Scheduled workflows can create daily reports, weekly meeting summaries, or monthly data analyses.

​

Nodes

Nodes are the individual steps within a workflow. Each node performs one specific action. Typical node actions include running an agent, processing data, transforming data, calling an external API, sending an email, and applying logical conditions. Nodes can be connected to create simple automations or complex multi-step workflows.

​

Logic controls

Logic controls define how workflow steps are executed. They allow the workflow to adapt to incoming data. Supported controls include If/Else conditions, loops, and parallel steps. If/Else conditions define the next path. Loops repeat actions for multiple items. Parallel steps run tasks at the same time.

​

Agents

Agents can run as workflow steps. They can generate content, analyze data, summarize documents, perform research, and make decisions. Agent results can be passed to other agents. This enables multi-agent automations within one workflow. Example workflow: one agent creates a job description. A second agent reviews and refines it. The final result is sent by email.

​

Integrations

Integrations connect workflows with external tools and services. Examples include email services, external APIs through HTTP requests, and connected data systems. This allows workflows to move data between systems automatically.

​

Output

Workflow Output Nodes create reusable nuwacom content at the end of a workflow, including documents, email drafts, and slides. Outputs can be saved to the Knowledge Base, and optionally attach the result to a project.

---

​

Review and monitor workflows

Manual approval steps pause a workflow until a result is reviewed, approved, or rejected. The workflow view provides an overview of the current execution status and supports detailed analysis of individual runs. The workflow view also allows you to:

• Inspect results for individual steps.
• Identify and analyze errors.
• Review previous workflow runs.
• Verify how manual approval decisions affect the workflow.

---

​

How to create a workflow

​

Create the first version in chat

1. Open the chat.
2. Select the task Create workflow.
3. Describe what the workflow should do. Include the goal, the information to process, and the final action.
   Example prompt: „Create a workflow that helps me plan my daily tasks. Analyze my calendar and suggest suitable time slots based on availability and deadlines.”
4. Send the prompt.
5. Let nuwacom create the multi-step workflow automatically.

​

Review the workflow in the Workflow Builder

1. Open the workflow in the Workflow Builder.
2. Review the workflow structure on the canvas.
3. Check how the components are connected.
4. Review where logic, agents, or integrations are used.
5. Adjust missing steps or existing configurations.
6. Test the workflow before production use.

Testing verifies that all steps run correctly and that the results match the expected outcome.

​

Run the workflow

1. Click Run in the upper-right corner.
2. Follow the execution in the Run Progress panel and ceck the status of each step:
   • Green: completed
   • Purple: running
   • Grey: not started
   • Red: failed or cancelled
3. Expand a step to view details or error messages.
4. Review the results and confirm that all steps and outputs are correct.

Once the workflow has been successfully tested and reviewed, publish the version to make it available for production use.

​

Publish the workflow

1. Open the menu next to Draft.
2. Click Publish Version.

The workflow is now available for production use.

---

​

nuwacom Trigger

nuwacom-native workflow triggers start published workflows automatically when defined events occur inside nuwacom. They remove the need for manual launches, external webhooks, or third-party integrations. Examples include creating a meeting note or completing the processing of a Knowledge Base file. Trigger data becomes available to later workflow steps and AI agents.

​

Key benefits of nuwacom-native workflow triggers

• Start workflows as soon as the configured event occurs.
• Limit workflow runs to relevant events through filters.
• Provide agents with the data that triggered the workflow.
• Configure internal events without external connections.
• Display available trigger fields in the variable picker.

​

Supported use cases

• Start a published workflow when a new meeting note is created.
• Start a workflow when a Knowledge Base file finishes processing.
• Restrict a trigger to files added to a specific Knowledge Base folder.
• Pass event details to downstream workflow steps and AI agents.
• Reference trigger data through the built-in variable picker.

​

Example

A workflow can start automatically when a file finishes processing in a selected Knowledge Base folder. The workflow can then pass the file details to an AI agent for classification, summarization, or further processing.

---

​

nuwacom Outputs

Workflow Output Nodes create reusable nuwacom content automatically. A workflow can generate documents, email drafts, designed documents, or slide decks instead of ending with a text response. Generated content can be saved directly to the Knowledge Base and attached to a project. Workflow results remain available for later work and later workflow steps.

​

Key benefits of Workflow Output Nodes

• Create finished deliverables directly from workflow results.
• Reduce manual copying between tools.
• Apply consistent writing, formatting, and brand guidelines.
• Save outputs in the correct Knowledge Base folder or project.
• Reuse generated content in later workflow steps.
• Prevent unnecessary duplicates when rerunning an output step.

​

What Workflow Output Nodes can create

Workflow Output Nodes can create HTML documents, plain text documents, email drafts, slide decks, and designed documents using selected skills and bundled assets. The node can generate new content or save the output from an earlier step unchanged.

​

When to use Workflow Output Nodes

Workflow Output Nodes are suitable for recurring processes that produce reusable content. Relevant scenarios include summaries from structured workflow results, recurring documents, email drafts for review, slide decks from collected information, branded documents from standardized instructions, and project documentation.

​

Example

A workflow receives meeting notes from an earlier step. A Workflow Output Node turns the result into a structured HTML document.

---

​

FAQ