You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/agent-studio/build-agents/building-workflows.mdx
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,35 +1,33 @@
1
1
---
2
2
title: Workflows
3
3
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.
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).
11
11
12
12
---
13
13
14
-
## Assemble components that interact with data
14
+
## Assemble components
15
15
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:
17
17
18
18
-**Query** a data source (e.g., database, spreadsheet, RAG search)
19
19
-**Act** on external services (e.g., HTTP API, SaaS integration)
20
20
-**Process** data (e.g., JavaScript code, math operations)
21
21
- and much more. For more detailed list, refer to [components]
22
22
23
-
Drag and drop components in the Workflow IDE, configure inputs, settings, and error paths, then connect them to define control flow.
24
-
25
23
---
26
24
27
25
## Define control flow
28
26
29
-
Connections between components determine execution order and data passing:
27
+
Connections between components determine execution order and data passing. Components can either be:
30
28
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.
33
31
34
32
## Invoke via Agent or API
35
33
@@ -44,7 +42,7 @@ curl -X POST \
44
42
-d '{"orderId":1234,"amount":49.99}'
45
43
46
44
- **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.
48
46
49
47
- **Task Invocation**
50
48
Tasks can be triggered through scheduled runs or batch processing, allowing forautomated execution of workflows at specified intervals orin bulk operations.
0 commit comments