diff --git a/en/cli/authenticate.mdx b/en/cli/authenticate.mdx index 4c6488ffa..1b5f4744d 100644 --- a/en/cli/authenticate.mdx +++ b/en/cli/authenticate.mdx @@ -7,6 +7,10 @@ You sign in through your browser, using the OAuth 2.0 device flow; `difyctl` nev ## Sign In + +On a self-hosted deployment, set both `OPENAPI_ENABLED` and `ENABLE_OAUTH_BEARER` to `true` before you sign in. See [Dify CLI and Programmatic API](/en/self-host/deploy/configuration/environments#dify-cli-and-programmatic-api) for the full variable reference. + + @@ -22,6 +26,7 @@ You sign in through your browser, using the OAuth 2.0 device flow; `difyctl` nev ! Copy this one-time code: WDJP-XKLM Open: https://cloud.dify.ai/device ``` + To skip the auto-open, pass `--no-browser`. diff --git a/en/cli/quick-start.mdx b/en/cli/quick-start.mdx index 72764d243..b986500db 100644 --- a/en/cli/quick-start.mdx +++ b/en/cli/quick-start.mdx @@ -5,6 +5,10 @@ description: Run your first Dify app from the command line in under 5 minutes Before you start, make sure `difyctl` is [installed](/en/cli/install). + +On a self-hosted deployment, set both `OPENAPI_ENABLED` and `ENABLE_OAUTH_BEARER` to `true` before you sign in. See [Dify CLI and Programmatic API](/en/self-host/deploy/configuration/environments#dify-cli-and-programmatic-api) for the full variable reference. + + ## Step 1: Sign In 1. Sign in to your Dify host. @@ -80,6 +84,7 @@ How you pass input depends on the app type. ```json {"summary":"Q3 revenue grew 14% YoY...","sections":["revenue","costs","outlook"]} ``` + diff --git a/en/cloud/use-dify/build/additional-features.mdx b/en/cloud/use-dify/build/additional-features.mdx index 4d1ee8701..ff086b563 100644 --- a/en/cloud/use-dify/build/additional-features.mdx +++ b/en/cloud/use-dify/build/additional-features.mdx @@ -35,8 +35,8 @@ You can insert variables into the opening message and suggested questions to per - - ![WebApp](/images/use-dify/workflow/conversation-opener-webapp.png) + + ![Web App](/images/use-dify/workflow/conversation-opener-webapp.png) diff --git a/en/cloud/use-dify/nodes/agent.mdx b/en/cloud/use-dify/nodes/agent.mdx index 4de469659..3f849c800 100644 --- a/en/cloud/use-dify/nodes/agent.mdx +++ b/en/cloud/use-dify/nodes/agent.mdx @@ -67,7 +67,7 @@ Define the Agent's role, goals, and context using natural language instructions. ### Execution Controls -**Maximum Iterations** sets a safety limit to prevent infinite loops. Configure based on task complexity - simple tasks need 3-5 iterations, while complex research might require 10-15. +**Max Iterations** sets a safety limit to prevent infinite loops. Configure based on task complexity - simple tasks need 3-5 iterations, while complex research might require 10-15. **Memory** controls how many previous messages the Agent remembers using TokenBufferMemory. Larger memory windows provide more context but increase token costs. This enables conversational continuity where users can reference previous actions. diff --git a/en/cloud/use-dify/nodes/human-input.mdx b/en/cloud/use-dify/nodes/human-input.mdx index 62b2435dd..e80f3dc36 100644 --- a/en/cloud/use-dify/nodes/human-input.mdx +++ b/en/cloud/use-dify/nodes/human-input.mdx @@ -27,10 +27,10 @@ Configure the following to define how the node requests and processes human inpu Choose the channel through which the request is delivered. Currently available methods: -- **Web app**: Displays the request form to the WebApp end user. Not available in workflows started by a Trigger. +- **Web app**: Displays the request form to the web app end user. Not available in workflows started by a Trigger. - External clients can drive the WebApp form lifecycle through the Service API. See [API Integration Flow](/en/api-reference/guides/human-input-flow). + External clients can drive the web app form lifecycle through the Service API. See [API Integration Flow](/en/api-reference/guides/human-input-flow). - **Email**: Sends a request link via email to specific workspace members, external email addresses, or every member of the workspace. Anyone with the link can respond, no Dify account required. @@ -51,7 +51,7 @@ Customize the form recipients see and interact with: Reference workflow variables to show dynamic content, such as AI-generated text for review or a file someone uploaded at an upstream Human Input node for approval. - In WebApp delivery, the form itself displays to end users. Any variables you reference render their values directly in the form, so **no Answer or Output node is needed before the Human Input node**. + In web app delivery, the form itself displays to end users. Any variables you reference render their values directly in the form, so **no Answer or Output node is needed before the Human Input node**. Reasoning models emit their thinking process alongside the final answer. Referencing the `text` output variable shows both by default. diff --git a/en/cloud/use-dify/nodes/trigger/plugin-trigger.mdx b/en/cloud/use-dify/nodes/trigger/plugin-trigger.mdx index ba041b3b1..dcce4e3bf 100644 --- a/en/cloud/use-dify/nodes/trigger/plugin-trigger.mdx +++ b/en/cloud/use-dify/nodes/trigger/plugin-trigger.mdx @@ -42,7 +42,7 @@ Dify supports two ways to create a subscription, depending on what the integrati - On Dify Cloud, many popular trigger plugins are pre-configured with default OAuth clients, so you can authorize in one click without registering your own OAuth application. To use your own OAuth application instead, choose **Custom**. + On Dify Cloud, many popular trigger integrations are pre-configured with default OAuth clients, so you can authorize in one click without registering your own OAuth application. To use your own OAuth application instead, choose **Custom**. **Default** diff --git a/en/cloud/use-dify/nodes/user-input.mdx b/en/cloud/use-dify/nodes/user-input.mdx index 0d056fca3..5e32c3d7d 100644 --- a/en/cloud/use-dify/nodes/user-input.mdx +++ b/en/cloud/use-dify/nodes/user-input.mdx @@ -138,13 +138,13 @@ Rather than maintain a separate workflow per product, you keep just one (with a - Use this when end users open the WebApp directly from its link. + Use this when end users open the web app directly from its link. 1. In the app's publishing panel, within the **Web App** section, click the gear icon next to **Launch**. ![Hidden Fields Pre-Fill Icon](/images/use-dify/workflow/hidden-field-config-icon.png) - 2. Fill in the hidden fields and click **Launch**. The WebApp opens with your values applied as URL query parameters; copy the URL from the address bar to share. + 2. Fill in the hidden fields and click **Launch**. The web app opens with your values applied as URL query parameters; copy the URL from the address bar to share. **To generate many links with different values**, use the same pattern to write more yourself, or have a system fill in the values automatically: @@ -158,7 +158,7 @@ Rather than maintain a separate workflow per product, you keep just one (with a - A support team using a CRM can add `?customerId={{customer.id}}` to the end of the WebApp URL in their ticket-response templates. + A support team using a CRM can add `?customerId={{customer.id}}` to the end of the web app URL in their ticket-response templates. The CRM substitutes the real customer ID when the rep sends the link, so the chatbot knows which customer it's talking to without having to ask. diff --git a/en/cloud/use-dify/publish/webapp/embedding-in-websites.mdx b/en/cloud/use-dify/publish/webapp/embedding-in-websites.mdx index 6df2c3ae9..b9c84ea38 100644 --- a/en/cloud/use-dify/publish/webapp/embedding-in-websites.mdx +++ b/en/cloud/use-dify/publish/webapp/embedding-in-websites.mdx @@ -81,7 +81,7 @@ window.difyChatbotConfig = { - In your Dify app, go to **Publish → Embed** to find your unique token. + In your Dify app, go to **Publish** > **Embed Into Site** to find your unique token. @@ -112,14 +112,15 @@ Embed your web app directly into your page content. This displays your app as an ### Why Use Iframe Embedding -- **Always visible** - Your web app is immediately accessible, not hidden behind a button -- **Full functionality** - Everything from your web app works identically in the iframe -- **Page integration** - Appears as native content, not an overlay -- **Simple setup** - Just HTML, no JavaScript configuration needed +- **Always visible**: Your web app is immediately accessible, not hidden behind a button +- **Full functionality**: Everything from your web app works identically in the iframe +- **Page integration**: Appears as native content, not an overlay +- **Simple setup**: Just HTML, no JavaScript configuration needed ### Customization Options **Size and Position**: + ```html