Skip to content
5 changes: 5 additions & 0 deletions en/cli/authenticate.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ You sign in through your browser, using the OAuth 2.0 device flow; `difyctl` nev

## Sign In

<Note>
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.
</Note>

<Steps>
<Step title="Run the login command">

Expand All @@ -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
```

<Tip>
To skip the auto-open, pass `--no-browser`.
</Tip>
Expand Down
5 changes: 5 additions & 0 deletions en/cli/quick-start.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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).

<Note>
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.
</Note>

## Step 1: Sign In

1. Sign in to your Dify host.
Expand Down Expand Up @@ -80,6 +84,7 @@ How you pass input depends on the app type.
```json
{"summary":"Q3 revenue grew 14% YoY...","sections":["revenue","costs","outlook"]}
```

</Tab>
</Tabs>

Expand Down
4 changes: 2 additions & 2 deletions en/cloud/use-dify/build/additional-features.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,8 @@ You can insert variables into the opening message and suggested questions to per
</Frame>
</Column>
<Column>
<Frame caption="WebApp">
![WebApp](/images/use-dify/workflow/conversation-opener-webapp.png)
<Frame caption="Web App">
![Web App](/images/use-dify/workflow/conversation-opener-webapp.png)
</Frame>
</Column>
</Columns>
Expand Down
2 changes: 1 addition & 1 deletion en/cloud/use-dify/nodes/agent.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
6 changes: 3 additions & 3 deletions en/cloud/use-dify/nodes/human-input.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<Info>
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).
</Info>

- **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.
Expand All @@ -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**.

<Tip>
Reasoning models emit their thinking process alongside the final answer. Referencing the `text` output variable shows both by default.
Expand Down
2 changes: 1 addition & 1 deletion en/cloud/use-dify/nodes/trigger/plugin-trigger.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ Dify supports two ways to create a subscription, depending on what the integrati

<Tabs>
<Tab title="OAuth (Automatic)">
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**

Expand Down
6 changes: 3 additions & 3 deletions en/cloud/use-dify/nodes/user-input.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -138,13 +138,13 @@ Rather than maintain a separate workflow per product, you keep just one (with a
<Tabs>
<Tab title="Shareable Link">

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**.
<Frame>
![Hidden Fields Pre-Fill Icon](/images/use-dify/workflow/hidden-field-config-icon.png)
</Frame>
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:

Expand All @@ -158,7 +158,7 @@ Rather than maintain a separate workflow per product, you keep just one (with a
</Note>

<Accordion title="Example: A CRM Auto-Fills the Customer ID">
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.
</Accordion>
Expand Down
46 changes: 26 additions & 20 deletions en/cloud/use-dify/publish/webapp/embedding-in-websites.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ window.difyChatbotConfig = {

<Steps>
<Step title="Get your embed token">
In your Dify app, go to **PublishEmbed** to find your unique token.
In your Dify app, go to **Publish** > **Embed Into Site** to find your unique token.
</Step>

<Step title="Add the script">
Expand Down Expand Up @@ -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
<iframe
src="https://udify.app/chatbot/YOUR_APP_TOKEN"
Expand All @@ -130,6 +131,7 @@ Embed your web app directly into your page content. This displays your app as an
```

**Responsive Design**:

```html
<div style="position: relative; width: 100%; height: 0; padding-bottom: 75%;">
<iframe
Expand Down Expand Up @@ -160,21 +162,7 @@ Embed your web app directly into your page content. This displays your app as an
</Accordion>
</AccordionGroup>

## Troubleshooting

**Widget not appearing**:
- Verify your app token matches what's shown in Dify's Publish → Embed section
- Check that configuration loads before the embed script
- Look for JavaScript errors in browser console

**Iframe not loading**:
- Confirm the web app URL includes your correct token
- Ensure your site allows iframe content (check Content Security Policy)
- Both your site and Dify app should use HTTPS

<Warning>
Your web app must be published before embedding. If you update your app configuration, republish to see changes in embedded versions.
</Warning>
## Advanced Configuration

You can override the default button style using CSS variables or the `containerProps` option. Apply these methods based on CSS specificity to achieve your desired customizations.

Expand Down Expand Up @@ -277,3 +265,21 @@ Note: When using the embed.js script to create an iframe, each input value will

For example, the URL with processed input values will look like this:
`http://localhost/chatbot/{token}?name=H4sIAKUlmWYA%2FwWAIQ0AAACDsl7gLuiv2PQEUNAuqQUAAAA%3D`

## Troubleshooting

**Widget not appearing**:

- Verify your app token matches what's shown in Dify's **Publish** > **Embed Into Site** section
- Check that configuration loads before the embed script
- Look for JavaScript errors in browser console

**Iframe not loading**:

- Confirm the web app URL includes your correct token
- Ensure your site allows iframe content (check Content Security Policy)
- Both your site and Dify app should use HTTPS

<Warning>
Your web app must be published before embedding. If you update your app configuration, republish to see changes in embedded versions.
</Warning>
8 changes: 4 additions & 4 deletions en/cloud/use-dify/publish/webapp/web-app-access.mdx
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
---
title: Access Control
description: Control who can use your published web apps with four access levels, from specific members to public access
tag: "ENTERPRISE"
---

Expand All @@ -11,7 +12,7 @@ Only Workspace Owner, Admin, and Editor roles can create and publish web apps.

## Access Permission Types

Configure access from the StudioWeb App Access Permissions, or from the Publish panel when editing your app.
Configure access from **Studio** > **Web App Access Control**, or from the Publish panel when editing your app.

Dify Enterprise offers four access levels:

Expand All @@ -31,7 +32,7 @@ If you upgraded from Dify Enterprise v2.7.x or earlier with Web App SSO enabled,

### Specific Members Within Platform

**Default setting for new apps.** Restricts access to chosen groups or individual members within your workspace. Perfect for department-specific tools or sensitive data applications.
**Default setting for new apps**. Restricts access to chosen groups or individual members within your workspace. Perfect for department-specific tools or sensitive data applications.

<Warning>
Without any groups or members selected, nobody can access your app—including you.
Expand Down Expand Up @@ -80,7 +81,7 @@ If this option is disabled, ask your Dify administrator to configure Web App Ext

### Anyone

**No authentication required.** Anyone with the URL can access your app immediately. Use for public demos, customer tools, or open resources.
**No authentication required**. Anyone with the URL can access your app immediately. Use for public demos, customer tools, or open resources.

## Find Your Apps

Expand All @@ -90,7 +91,6 @@ Team members see all accessible apps in the workspace Explorer page:
![Team Members See All Accessible Apps in the Workspace Explorer Page](https://assets-docs.dify.ai/2025/04/44a22b6f66f80eae805a307388e5b3e9.png)
</Frame>


## Common Questions

<AccordionGroup>
Expand Down
10 changes: 5 additions & 5 deletions en/cloud/use-dify/publish/webapp/web-app-settings.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ Make your web app look professional and recognizable:
<Card title="Language Settings" icon="globe">
Configure interface language for your target audience
</Card>
<Card title="Legal Pages" icon="scale">
<Card title="Legal Pages" icon="scale-balanced">
Add copyright information and privacy policy links for compliance
</Card>
</CardGroup>
Expand Down Expand Up @@ -60,7 +60,7 @@ Web apps are public by default. Anyone with the URL can open them, which works w

## Feature Inheritance

Your web app automatically includes features you've enabled in your application configuration:
Your web app automatically includes features you've enabled in your app configuration:

**Interactive Features**:
- Conversation openers and suggested follow-ups
Expand All @@ -81,16 +81,16 @@ Disabling features in your app configuration immediately removes them from the p

## App Types and Behavior

Your web app automatically adapts its interface based on your application type:
Your web app automatically adapts its interface based on your app type:

<Tabs>
<Tab title="Chat Applications">
<Tab title="Chat Apps">
**Interface**: Conversation-style with message history
**Features**: Persistent sessions, conversation management, real-time responses
**Best for**: Customer support, consulting tools, interactive assistants
</Tab>

<Tab title="Workflow Applications">
<Tab title="Workflow Apps">
**Interface**: Form-based with result display
**Features**: Single runs, batch processing, result saving
**Best for**: Content generation, data processing, analysis tools
Expand Down
40 changes: 22 additions & 18 deletions en/cloud/use-dify/publish/webapp/workflow-webapp.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -42,16 +42,18 @@ The default mode for Workflow apps handles individual requests with real-time pr
</Frame>

**User Experience**:
1. **Fill input form** - Users provide parameters based on your workflow's start variables
2. **Click run** - The workflow executes with real-time progress indication
3. **View results** - Output appears with immediate access to copy, save, and feedback options
4. **Take actions** - Users can save important results, provide feedback, or generate similar outputs

1. **Fill input form**: Users provide parameters based on your workflow's start variables
2. **Click run**: The workflow executes with real-time progress indication
3. **View results**: Output appears with immediate access to copy, save, and feedback options
4. **Take actions**: Users can save important results, provide feedback, or generate similar outputs

Each result includes built-in actions:
- **Copy** - One-click copying to clipboard for easy sharing
- **Save** - Store results in the app's saved items for later access
- **Feedback** - Like/dislike ratings to help improve your workflow
- **More like this** - Generate variations based on the current result (if enabled)

- **Copy**: One-click copying to clipboard for easy sharing
- **Save**: Store results in the app's saved items for later access
- **Feedback**: Like/dislike ratings to help improve your workflow
- **More like this**: Generate variations based on the current result (if enabled)

## Batch Processing

Expand All @@ -65,7 +67,7 @@ Perfect for tasks like generating content for multiple topics, processing custom

<Steps>
<Step title="Switch to batch mode">
Click the "Run Batch" tab to access batch processing features.
Click the **Run Batch** tab to access batch processing features.

<Frame>
![Batch Run Tab Interface](https://assets-docs.dify.ai/dify-enterprise-mintlify/en/guides/application-publishing/launch-your-webapp-quickly/c8381ab7fad14a54c86835dc4b1b6b5d.png)
Expand Down Expand Up @@ -95,10 +97,10 @@ Perfect for tasks like generating content for multiple topics, processing custom

### Batch Processing Benefits

- **Parallel execution** - Multiple workflow runs happen simultaneously
- **Progress tracking** - Real-time updates on completion status
- **Bulk export** - Download all results as a CSV file when finished
- **Error handling** - Failed items are clearly marked with error details
- **Parallel execution**: Multiple workflow runs happen simultaneously
- **Progress tracking**: Real-time updates on completion status
- **Bulk export**: Download all results as a CSV file when finished
- **Error handling**: Failed items are clearly marked with error details

<Warning>
CSV files must use Unicode encoding to prevent import failures. When saving from Excel or similar tools, explicitly select "Unicode (UTF-8)" encoding.
Expand All @@ -115,8 +117,9 @@ Workflow apps include comprehensive result management to help users organize and
</Frame>

**How saving works**:
- Users click "Save" on any result they want to keep
- Saved items appear in the dedicated "Saved" tab

- Users click **Save** on any result they want to keep
- Saved items appear in the dedicated **Saved** tab
- Each saved result includes the original inputs and full outputs
- Users can organize saved results and access them anytime

Expand All @@ -126,18 +129,19 @@ Saved results persist across user sessions, making Workflow apps useful for buil

### Generate Variations

When you enable "More like this" in your workflow settings, users can generate variations of successful results:
When you enable **More like this** in your workflow settings, users can generate variations of successful results:

<Frame>
![More Like This Feature](https://assets-docs.dify.ai/dify-enterprise-mintlify/en/guides/application-publishing/launch-your-webapp-quickly/65fb111d8e89a8f7b761859265e42f0a.png)
</Frame>

**How it works**:

1. User gets a result they like
2. They click "More like this" to generate similar outputs
2. They click **More like this** to generate similar outputs
3. The workflow runs again with slight variations to produce different but related results
4. Users can iterate until they find the perfect output

<Tip>
"More like this" works especially well for creative workflows like content generation, where users want to explore different approaches to the same topic.
**More like this** works especially well for creative workflows like content generation, where users want to explore different approaches to the same topic.
</Tip>
2 changes: 1 addition & 1 deletion en/cloud/use-dify/workspace/app-management.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Managing your apps well is crucial for productive AI development. Dify provides
<Card title="Duplicate & Template" icon="copy">
Create variations or use existing apps as templates for new projects
</Card>
<Card title="Import & Export" icon="arrows-exchange">
<Card title="Import & Export" icon="right-left">
Share apps between workspaces using Dify's DSL format
</Card>
<Card title="Lifecycle Management" icon="recycle">
Expand Down
Loading
Loading