Skip to content

Commit d56b490

Browse files
RiskeyLclaude
RiskeyL
and
claude
committed
docs: add Start Node page, complete trigger rewrites, and apply review fixes
- Add Start Node overview page (en/zh/ja, cloud + self-host) explaining the User Input vs. Trigger choice; nest under a new Start group in docs.json with root page support - Trim Key Concepts to link to the new Start Node page instead of inlining the details - Complete Integration Trigger page rewrite (en/zh/ja) with localized UI strings, trigger integration naming, and subscription flow - Remove "## Introduction" headings from trigger, schedule-trigger, webhook-trigger, and user-input pages (en/zh/ja) - Apply review fixes: user-centric opening for tools.mdx, reframe auto-update sentence in plugins.mdx, bold Client ID/Secret, remove tautological sentence, fix "reusable/reuse" redundancy - Complete remaining API Extension to Custom Endpoint renames in api-extension, cloudflare-worker, and moderation pages - Update termbase_i18n.md to match glossary (Integration Trigger, Integrations, Custom Endpoint, Default Models, Logs/Annotations split) - Add redirects for deleted self-host build/mcp pages Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent c8a06a0 commit d56b490

43 files changed

Lines changed: 485 additions & 520 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs.json‎

Lines changed: 89 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -45,14 +45,20 @@
4545
"group": "Nodes",
4646
"expanded": false,
4747
"pages": [
48-
"en/cloud/use-dify/nodes/user-input",
4948
{
50-
"group": "Trigger",
49+
"group": "Start",
50+
"root": "en/cloud/use-dify/nodes/start",
5151
"pages": [
52-
"en/cloud/use-dify/nodes/trigger/overview",
53-
"en/cloud/use-dify/nodes/trigger/schedule-trigger",
54-
"en/cloud/use-dify/nodes/trigger/plugin-trigger",
55-
"en/cloud/use-dify/nodes/trigger/webhook-trigger"
52+
"en/cloud/use-dify/nodes/user-input",
53+
{
54+
"group": "Trigger",
55+
"root": "en/cloud/use-dify/nodes/trigger/overview",
56+
"pages": [
57+
"en/cloud/use-dify/nodes/trigger/schedule-trigger",
58+
"en/cloud/use-dify/nodes/trigger/plugin-trigger",
59+
"en/cloud/use-dify/nodes/trigger/webhook-trigger"
60+
]
61+
}
5662
]
5763
},
5864
"en/cloud/use-dify/nodes/llm",
@@ -509,15 +515,21 @@
509515
"group": "Nodes",
510516
"expanded": false,
511517
"pages": [
512-
"en/self-host/use-dify/nodes/user-input",
513518
{
514-
"group": "Trigger",
519+
"group": "Start",
515520
"pages": [
516-
"en/self-host/use-dify/nodes/trigger/overview",
517-
"en/self-host/use-dify/nodes/trigger/schedule-trigger",
518-
"en/self-host/use-dify/nodes/trigger/plugin-trigger",
519-
"en/self-host/use-dify/nodes/trigger/webhook-trigger"
520-
]
521+
"en/self-host/use-dify/nodes/user-input",
522+
{
523+
"group": "Trigger",
524+
"pages": [
525+
"en/self-host/use-dify/nodes/trigger/schedule-trigger",
526+
"en/self-host/use-dify/nodes/trigger/plugin-trigger",
527+
"en/self-host/use-dify/nodes/trigger/webhook-trigger"
528+
],
529+
"root": "en/self-host/use-dify/nodes/trigger/overview"
530+
}
531+
],
532+
"root": "en/self-host/use-dify/nodes/start"
521533
},
522534
"en/self-host/use-dify/nodes/llm",
523535
"en/self-host/use-dify/nodes/knowledge-retrieval",
@@ -934,15 +946,21 @@
934946
"group": "节点",
935947
"expanded": false,
936948
"pages": [
937-
"zh/cloud/use-dify/nodes/user-input",
938949
{
939-
"group": "触发器",
950+
"group": "开始",
940951
"pages": [
941-
"zh/cloud/use-dify/nodes/trigger/overview",
942-
"zh/cloud/use-dify/nodes/trigger/schedule-trigger",
943-
"zh/cloud/use-dify/nodes/trigger/plugin-trigger",
944-
"zh/cloud/use-dify/nodes/trigger/webhook-trigger"
945-
]
952+
"zh/cloud/use-dify/nodes/user-input",
953+
{
954+
"group": "触发器",
955+
"pages": [
956+
"zh/cloud/use-dify/nodes/trigger/schedule-trigger",
957+
"zh/cloud/use-dify/nodes/trigger/plugin-trigger",
958+
"zh/cloud/use-dify/nodes/trigger/webhook-trigger"
959+
],
960+
"root": "zh/cloud/use-dify/nodes/trigger/overview"
961+
}
962+
],
963+
"root": "zh/cloud/use-dify/nodes/start"
946964
},
947965
"zh/cloud/use-dify/nodes/llm",
948966
"zh/cloud/use-dify/nodes/knowledge-retrieval",
@@ -1398,15 +1416,21 @@
13981416
"group": "节点",
13991417
"expanded": false,
14001418
"pages": [
1401-
"zh/self-host/use-dify/nodes/user-input",
14021419
{
1403-
"group": "触发器",
1420+
"group": "开始",
14041421
"pages": [
1405-
"zh/self-host/use-dify/nodes/trigger/overview",
1406-
"zh/self-host/use-dify/nodes/trigger/schedule-trigger",
1407-
"zh/self-host/use-dify/nodes/trigger/plugin-trigger",
1408-
"zh/self-host/use-dify/nodes/trigger/webhook-trigger"
1409-
]
1422+
"zh/self-host/use-dify/nodes/user-input",
1423+
{
1424+
"group": "触发器",
1425+
"pages": [
1426+
"zh/self-host/use-dify/nodes/trigger/schedule-trigger",
1427+
"zh/self-host/use-dify/nodes/trigger/plugin-trigger",
1428+
"zh/self-host/use-dify/nodes/trigger/webhook-trigger"
1429+
],
1430+
"root": "zh/self-host/use-dify/nodes/trigger/overview"
1431+
}
1432+
],
1433+
"root": "zh/self-host/use-dify/nodes/start"
14101434
},
14111435
"zh/self-host/use-dify/nodes/llm",
14121436
"zh/self-host/use-dify/nodes/knowledge-retrieval",
@@ -1823,15 +1847,21 @@
18231847
"group": "ノード",
18241848
"expanded": false,
18251849
"pages": [
1826-
"ja/cloud/use-dify/nodes/user-input",
18271850
{
1828-
"group": "トリガー",
1851+
"group": "開始",
18291852
"pages": [
1830-
"ja/cloud/use-dify/nodes/trigger/overview",
1831-
"ja/cloud/use-dify/nodes/trigger/schedule-trigger",
1832-
"ja/cloud/use-dify/nodes/trigger/plugin-trigger",
1833-
"ja/cloud/use-dify/nodes/trigger/webhook-trigger"
1834-
]
1853+
"ja/cloud/use-dify/nodes/user-input",
1854+
{
1855+
"group": "トリガー",
1856+
"pages": [
1857+
"ja/cloud/use-dify/nodes/trigger/schedule-trigger",
1858+
"ja/cloud/use-dify/nodes/trigger/plugin-trigger",
1859+
"ja/cloud/use-dify/nodes/trigger/webhook-trigger"
1860+
],
1861+
"root": "ja/cloud/use-dify/nodes/trigger/overview"
1862+
}
1863+
],
1864+
"root": "ja/cloud/use-dify/nodes/start"
18351865
},
18361866
"ja/cloud/use-dify/nodes/llm",
18371867
"ja/cloud/use-dify/nodes/knowledge-retrieval",
@@ -2279,15 +2309,21 @@
22792309
"group": "ノード",
22802310
"expanded": false,
22812311
"pages": [
2282-
"ja/self-host/use-dify/nodes/user-input",
22832312
{
2284-
"group": "トリガー",
2313+
"group": "開始",
22852314
"pages": [
2286-
"ja/self-host/use-dify/nodes/trigger/overview",
2287-
"ja/self-host/use-dify/nodes/trigger/schedule-trigger",
2288-
"ja/self-host/use-dify/nodes/trigger/plugin-trigger",
2289-
"ja/self-host/use-dify/nodes/trigger/webhook-trigger"
2290-
]
2315+
"ja/self-host/use-dify/nodes/user-input",
2316+
{
2317+
"group": "トリガー",
2318+
"pages": [
2319+
"ja/self-host/use-dify/nodes/trigger/schedule-trigger",
2320+
"ja/self-host/use-dify/nodes/trigger/plugin-trigger",
2321+
"ja/self-host/use-dify/nodes/trigger/webhook-trigger"
2322+
],
2323+
"root": "ja/self-host/use-dify/nodes/trigger/overview"
2324+
}
2325+
],
2326+
"root": "ja/self-host/use-dify/nodes/start"
22912327
},
22922328
"ja/self-host/use-dify/nodes/llm",
22932329
"ja/self-host/use-dify/nodes/knowledge-retrieval",
@@ -3712,6 +3748,18 @@
37123748
{
37133749
"source": "/",
37143750
"destination": "/en/home"
3751+
},
3752+
{
3753+
"source": "/en/self-host/use-dify/build/mcp",
3754+
"destination": "/en/self-host/use-dify/workspace/tools"
3755+
},
3756+
{
3757+
"source": "/zh/self-host/use-dify/build/mcp",
3758+
"destination": "/zh/self-host/use-dify/workspace/tools"
3759+
},
3760+
{
3761+
"source": "/ja/self-host/use-dify/build/mcp",
3762+
"destination": "/ja/self-host/use-dify/workspace/tools"
37153763
}
37163764
],
37173765
"integrations": {

‎en/cloud/use-dify/nodes/start.mdx‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
title: Start Node
3+
description: Choose how your workflow begins, on demand or automatically
4+
---
5+
6+
When you create a new workflow, you choose a start node that decides whether the workflow waits for someone to run it or runs on its own.
7+
8+
## User Input
9+
10+
Use [User Input](/en/cloud/use-dify/nodes/user-input) when someone (or an API call) should kick off the workflow and supply information it needs. You define input fields for text, numbers, files, and other data, and downstream nodes reference those values.
11+
12+
Only User Input workflows can be published as web apps, MCP servers, backend service APIs, or reused as tools in other Dify apps.
13+
14+
<Info>
15+
Chatflows always start with User Input. Only Workflows can use triggers.
16+
</Info>
17+
18+
## Trigger
19+
20+
Use a [trigger](/en/cloud/use-dify/nodes/trigger/overview) when the workflow should run automatically, without anyone invoking it. Three types are available:
21+
22+
- **[Schedule Trigger](/en/cloud/use-dify/nodes/trigger/schedule-trigger)**: runs at specified times or intervals.
23+
- **[Integration Trigger](/en/cloud/use-dify/nodes/trigger/plugin-trigger)**: runs when an event occurs in an external system, via a subscription through a trigger integration.
24+
- **[Webhook Trigger](/en/cloud/use-dify/nodes/trigger/webhook-trigger)**: runs when the workflow receives an HTTP request from an external system.
25+
26+
## Switch Between Start Nodes
27+
28+
User Input and triggers are mutually exclusive on a canvas. To switch, right-click the current start node and select **Change Node**, or delete it and add a new one.

‎en/cloud/use-dify/nodes/trigger/overview.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ sidebarTitle: Overview
1111

1212
A trigger is a type of Start node that lets your workflow run automatically on a schedule or in response to events from external systems (such as GitHub, Gmail, or your own internal systems), rather than waiting for active initiation from a user or an API call.
1313

14-
Triggers are ideal for automating repetitive tasks or integrating your workflow with third-party applications to achieve automatic data synchronization and processing.
14+
Use triggers to automate repetitive tasks or synchronize data with third-party applications.
1515

1616
A workflow can have multiple triggers running in parallel. You can also build several independent workflows on the same canvas, each starting with its own triggers.
1717

‎en/cloud/use-dify/workspace/readme.mdx‎

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -36,10 +36,6 @@ Applications you build can use any model providers configured in the workspace,
3636

3737
Workspace roles determine access across all resources:
3838
- **Owners** control billing, model providers, and workspace settings
39-
- **Admins** manage team members and configure models/plugins
39+
- **Admins** manage team members and configure models/plugins
4040
- **Editors** build applications and manage knowledge bases
41-
- **Members** use published applications
42-
43-
## Workspace Navigation
44-
45-
Dify organizes everything around the workspace concept. The main navigation shows Apps, Knowledge, and Tools available in your workspace. Settings contains workspace-wide configurations: Members, Model Providers, Plugins, Billing, and personal Account settings.
41+
- **Members** use published applications

‎en/cloud/use-dify/workspace/tools.mdx‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,7 @@ sidebarTitle: Tools
44
description: Manage tools that enable LLMs to interact with external services and APIs
55
---
66

7-
Dify tools enable LLMs to interact with external services and APIs, so they can access real-time data and perform actions (e.g., web searches, database queries, or content processing).
8-
9-
Each tool has a clear interface: what inputs it accepts, what action it performs, and what output it returns. This helps LLMs decide when and how to call a tool based on user requests.
7+
Add tools to your apps so the LLM can reach external services and APIs for real-time data, web searches, database queries, or content processing.
108

119
Use tools in:
1210

‎en/learn/key-concepts.mdx‎

Lines changed: 3 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -30,24 +30,13 @@ Build workflow apps to handle single-turn tasks. The webapp interface and API pr
3030
Underneath it all, workflow forms the basis for all other app types in Dify.
3131
</Info>
3232

33-
You can specify how and when to start your workflow. There are two types of Start nodes:
34-
35-
- **[User Input](/en/cloud/use-dify/nodes/user-input)**: Direct user interaction or API call invokes the app.
36-
37-
- **[Trigger](/en/cloud/use-dify/nodes/trigger/overview)**: The application runs automatically on a schedule or in response to a specific third-party event.
38-
39-
User Input and Trigger Start nodes are mutually exclusive—they cannot be used on the same canvas. To switch between them, right-click the current start node > **Change Node**. Alternatively, delete the current start node and add a new one.
40-
41-
<Note>
42-
Only workflows started by User Input can be published as standalone web apps or MCP servers, exposed through backend service APIs, or used as tools in other Dify applications.
43-
</Note>
44-
33+
Every workflow begins with a [start node](/en/cloud/use-dify/nodes/start): either User Input (on-demand, triggered by a user or API call) or a Trigger (automatic, on a schedule or in response to external events).
4534

4635
### Chatflow
4736

48-
Chatflow is a special type of workflow app that gets triggered at every turn of a conversation. Other than workflow features, chatflow comes with the ability to store and update custom conversation-specific variables, enable memory in LLM nodes, and stream formatted text, images, and files at different points throughout the chatflow run.
37+
Chatflow is a special type of workflow app that gets triggered at every turn of a conversation. Other than workflow features, chatflow comes with the ability to store and update custom conversation-specific variables, enable memory in LLM nodes, and stream formatted text, images, and files at different points throughout the chatflow run.
4938

50-
Unlike workflow, chatflow can't use [Trigger](/en/cloud/use-dify/nodes/trigger/overview) to start.
39+
Chatflows always start with User Input.
5140

5241
### Dify DSL
5342

‎en/self-host/use-dify/nodes/start.mdx‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
title: Start Node
3+
description: Choose how your workflow begins, on demand or automatically
4+
---
5+
6+
When you create a new workflow, you choose a start node that decides whether the workflow waits for someone to run it or runs on its own.
7+
8+
## User Input
9+
10+
Use [User Input](/en/self-host/use-dify/nodes/user-input) when someone (or an API call) should kick off the workflow and supply information it needs. You define input fields for text, numbers, files, and other data, and downstream nodes reference those values.
11+
12+
Only User Input workflows can be published as web apps, MCP servers, backend service APIs, or reused as tools in other Dify apps.
13+
14+
<Info>
15+
Chatflows always start with User Input. Only Workflows can use triggers.
16+
</Info>
17+
18+
## Trigger
19+
20+
Use a [trigger](/en/self-host/use-dify/nodes/trigger/overview) when the workflow should run automatically, without anyone invoking it. Three types are available:
21+
22+
- **[Schedule Trigger](/en/self-host/use-dify/nodes/trigger/schedule-trigger)**: runs at specified times or intervals.
23+
- **[Integration Trigger](/en/self-host/use-dify/nodes/trigger/plugin-trigger)**: runs when an event occurs in an external system, via a subscription through a trigger integration.
24+
- **[Webhook Trigger](/en/self-host/use-dify/nodes/trigger/webhook-trigger)**: runs when the workflow receives an HTTP request from an external system.
25+
26+
## Switch Between Start Nodes
27+
28+
User Input and triggers are mutually exclusive on a canvas. To switch, right-click the current start node and select **Change Node**, or delete it and add a new one.

0 commit comments

Comments
 (0)