Skip to content

Commit b589e5f

Browse files
committed
workflow updates
1 parent 4165703 commit b589e5f

1 file changed

Lines changed: 8 additions & 10 deletions

File tree

docs/agent-studio/build-agents/building-workflows.mdx

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,35 +1,33 @@
11
---
22
title: Workflows
33
description: Automate any process by chaining pre-built components that interact with resources, transform data, and run logic—triggered by schedules, chat, API calls, or voice and other embodiments.
4-
keywords: [SmythOS, workflows, automation, components, no-code, orchestration]
4+
keywords: [SmythOS, workflows, automation, skills, skills, components, no-code, orchestration]
55
sidebar_position: 4
66
---
77

88
# Workflows
99

10-
A **workflow** in SmythOS is a self-contained sequence of **components**—modular blocks that query data, perform actions, transform inputs, and run logic. Workflows can execute on a schedule, in response to webhooks, via API calls, through chat interactions, or on any other supported embodiment (voice, batch, UI button).
10+
A **workflow** in SmythOS is a self-contained sequence of **components**—modular blocks that query data, perform actions, transform inputs, and run logic. Workflows can execute on a schedule, in response to webhooks, via API calls, through chat interactions, or on any other supported embodiment (voice, batch, UI button). Enable your agent to use workflows by linking them via an [Agent Skill](/docs/agent-studio/components/base/agent-skill).
1111

1212
---
1313

14-
## Assemble components that interact with data
14+
## Assemble components
1515

16-
Workflows consist of **components**. Each component can:
16+
Drag and drop components in the Workflow IDE, configure inputs, settings, and error paths, then connect them to define control flow. Each component can:
1717

1818
- **Query** a data source (e.g., database, spreadsheet, RAG search)
1919
- **Act** on external services (e.g., HTTP API, SaaS integration)
2020
- **Process** data (e.g., JavaScript code, math operations)
2121
- and much more. For more detailed list, refer to [components]
2222

23-
Drag and drop components in the Workflow IDE, configure inputs, settings, and error paths, then connect them to define control flow.
24-
2523
---
2624

2725
## Define control flow
2826

29-
Connections between components determine execution order and data passing:
27+
Connections between components determine execution order and data passing. Components can either be:
3028

31-
- **Sequential path**: one component after another.
32-
- **Branching**: parallel or conditional paths using the Branch component.
29+
- **Sequential**: one component after another.
30+
- **Branching**: parallel or conditional paths.
3331

3432
## Invoke via Agent or API
3533

@@ -44,7 +42,7 @@ curl -X POST \
4442
-d '{"orderId":1234,"amount":49.99}'
4543

4644
- **Agent Invocation**
47-
An agent orchestrates one or more workflows in response to chat, voice, or other embodiments. Within the agent’s workflow canvas, connect the Agent Skill to the start of a workflow.
45+
Connect the workflow to an Agent via the [Agent Skill Component](/docs/agent-studio/components/base/agent-skill) to enable agent orchestration. An agent can use one or more workflows in response to chat, voice, or other embodiments.
4846

4947
- **Task Invocation**
5048
Tasks can be triggered through scheduled runs or batch processing, allowing for automated execution of workflows at specified intervals or in bulk operations.

0 commit comments

Comments
 (0)