diff --git a/sources/platform/integrations/images/dify-configure-actor-run.png b/sources/platform/integrations/images/dify-configure-actor-run.png
new file mode 100644
index 000000000..51715f1fc
Binary files /dev/null and b/sources/platform/integrations/images/dify-configure-actor-run.png differ
diff --git a/sources/platform/integrations/images/dify-configure-end-node.png b/sources/platform/integrations/images/dify-configure-end-node.png
new file mode 100644
index 000000000..db1f09378
Binary files /dev/null and b/sources/platform/integrations/images/dify-configure-end-node.png differ
diff --git a/sources/platform/integrations/images/dify-connection-popup.png b/sources/platform/integrations/images/dify-connection-popup.png
new file mode 100644
index 000000000..86575e753
Binary files /dev/null and b/sources/platform/integrations/images/dify-connection-popup.png differ
diff --git a/sources/platform/integrations/images/dify-connection-success.png b/sources/platform/integrations/images/dify-connection-success.png
new file mode 100644
index 000000000..c08daefcb
Binary files /dev/null and b/sources/platform/integrations/images/dify-connection-success.png differ
diff --git a/sources/platform/integrations/images/dify-dataset-input.png b/sources/platform/integrations/images/dify-dataset-input.png
new file mode 100644
index 000000000..c07114531
Binary files /dev/null and b/sources/platform/integrations/images/dify-dataset-input.png differ
diff --git a/sources/platform/integrations/images/dify-dataset-succeded.png b/sources/platform/integrations/images/dify-dataset-succeded.png
new file mode 100644
index 000000000..bad1decac
Binary files /dev/null and b/sources/platform/integrations/images/dify-dataset-succeded.png differ
diff --git a/sources/platform/integrations/images/dify-define-input-variable.png b/sources/platform/integrations/images/dify-define-input-variable.png
new file mode 100644
index 000000000..aefbf1a02
Binary files /dev/null and b/sources/platform/integrations/images/dify-define-input-variable.png differ
diff --git a/sources/platform/integrations/images/dify-input-variable-webhook-succeded.png b/sources/platform/integrations/images/dify-input-variable-webhook-succeded.png
new file mode 100644
index 000000000..15cb3f8e5
Binary files /dev/null and b/sources/platform/integrations/images/dify-input-variable-webhook-succeded.png differ
diff --git a/sources/platform/integrations/images/dify-input-variable-webhook.png b/sources/platform/integrations/images/dify-input-variable-webhook.png
new file mode 100644
index 000000000..39c0e565f
Binary files /dev/null and b/sources/platform/integrations/images/dify-input-variable-webhook.png differ
diff --git a/sources/platform/integrations/images/dify-key-value-input.png b/sources/platform/integrations/images/dify-key-value-input.png
new file mode 100644
index 000000000..b73c963f1
Binary files /dev/null and b/sources/platform/integrations/images/dify-key-value-input.png differ
diff --git a/sources/platform/integrations/images/dify-key-value-succeded.png b/sources/platform/integrations/images/dify-key-value-succeded.png
new file mode 100644
index 000000000..8907f1349
Binary files /dev/null and b/sources/platform/integrations/images/dify-key-value-succeded.png differ
diff --git a/sources/platform/integrations/images/dify-ready-actor-flow.png b/sources/platform/integrations/images/dify-ready-actor-flow.png
new file mode 100644
index 000000000..13a5ffeeb
Binary files /dev/null and b/sources/platform/integrations/images/dify-ready-actor-flow.png differ
diff --git a/sources/platform/integrations/images/dify-scrape-input.png b/sources/platform/integrations/images/dify-scrape-input.png
new file mode 100644
index 000000000..c9b921e2c
Binary files /dev/null and b/sources/platform/integrations/images/dify-scrape-input.png differ
diff --git a/sources/platform/integrations/images/dify-scrape-succeded.png b/sources/platform/integrations/images/dify-scrape-succeded.png
new file mode 100644
index 000000000..7ae5e3120
Binary files /dev/null and b/sources/platform/integrations/images/dify-scrape-succeded.png differ
diff --git a/sources/platform/integrations/images/dify-task-input.png b/sources/platform/integrations/images/dify-task-input.png
new file mode 100644
index 000000000..8b67ebdc2
Binary files /dev/null and b/sources/platform/integrations/images/dify-task-input.png differ
diff --git a/sources/platform/integrations/images/dify-task-succeded.png b/sources/platform/integrations/images/dify-task-succeded.png
new file mode 100644
index 000000000..5903da7d2
Binary files /dev/null and b/sources/platform/integrations/images/dify-task-succeded.png differ
diff --git a/sources/platform/integrations/images/dify-trigger-apify-console.png b/sources/platform/integrations/images/dify-trigger-apify-console.png
new file mode 100644
index 000000000..dcd52c85b
Binary files /dev/null and b/sources/platform/integrations/images/dify-trigger-apify-console.png differ
diff --git a/sources/platform/integrations/images/dify-trigger-query.png b/sources/platform/integrations/images/dify-trigger-query.png
new file mode 100644
index 000000000..a32ccad51
Binary files /dev/null and b/sources/platform/integrations/images/dify-trigger-query.png differ
diff --git a/sources/platform/integrations/images/dify-trigger-succeded.png b/sources/platform/integrations/images/dify-trigger-succeded.png
new file mode 100644
index 000000000..802570999
Binary files /dev/null and b/sources/platform/integrations/images/dify-trigger-succeded.png differ
diff --git a/sources/platform/integrations/images/dify-trigger-url.png b/sources/platform/integrations/images/dify-trigger-url.png
new file mode 100644
index 000000000..fdd6cddd3
Binary files /dev/null and b/sources/platform/integrations/images/dify-trigger-url.png differ
diff --git a/sources/platform/integrations/images/dify-trigger-webhook.png b/sources/platform/integrations/images/dify-trigger-webhook.png
new file mode 100644
index 000000000..c4cffa528
Binary files /dev/null and b/sources/platform/integrations/images/dify-trigger-webhook.png differ
diff --git a/sources/platform/integrations/images/dify-trigger-workflow.png b/sources/platform/integrations/images/dify-trigger-workflow.png
new file mode 100644
index 000000000..7af1d8d3d
Binary files /dev/null and b/sources/platform/integrations/images/dify-trigger-workflow.png differ
diff --git a/sources/platform/integrations/images/dify-workflow-create.png b/sources/platform/integrations/images/dify-workflow-create.png
new file mode 100644
index 000000000..d1c7a5650
Binary files /dev/null and b/sources/platform/integrations/images/dify-workflow-create.png differ
diff --git a/sources/platform/integrations/images/dify-workflow-input-variable.png b/sources/platform/integrations/images/dify-workflow-input-variable.png
new file mode 100644
index 000000000..8be9beb38
Binary files /dev/null and b/sources/platform/integrations/images/dify-workflow-input-variable.png differ
diff --git a/sources/platform/integrations/images/dify-workflow-input.png b/sources/platform/integrations/images/dify-workflow-input.png
new file mode 100644
index 000000000..f71c4b9b3
Binary files /dev/null and b/sources/platform/integrations/images/dify-workflow-input.png differ
diff --git a/sources/platform/integrations/images/dify-workflow-publish.png b/sources/platform/integrations/images/dify-workflow-publish.png
new file mode 100644
index 000000000..259303c01
Binary files /dev/null and b/sources/platform/integrations/images/dify-workflow-publish.png differ
diff --git a/sources/platform/integrations/images/dify-workflow-start.png b/sources/platform/integrations/images/dify-workflow-start.png
new file mode 100644
index 000000000..da84a56cb
Binary files /dev/null and b/sources/platform/integrations/images/dify-workflow-start.png differ
diff --git a/sources/platform/integrations/images/dify-workflow-with-input-variable.png b/sources/platform/integrations/images/dify-workflow-with-input-variable.png
new file mode 100644
index 000000000..3067594ec
Binary files /dev/null and b/sources/platform/integrations/images/dify-workflow-with-input-variable.png differ
diff --git a/sources/platform/integrations/workflows-and-notifications/dify.md b/sources/platform/integrations/workflows-and-notifications/dify.md
new file mode 100644
index 000000000..768514d74
--- /dev/null
+++ b/sources/platform/integrations/workflows-and-notifications/dify.md
@@ -0,0 +1,183 @@
+---
+title: Dify integration
+description: Connect Apify with Dify to automate workflows by running Actors, extracting data, and responding to Apify events.
+sidebar_label: Dify
+sidebar_position: 7
+slug: /integrations/dify
+---
+
+**Connect Apify with Dify to automate workflows by running Actors, extracting structured data, and responding to Actor or task events.**
+
+---
+
+[Dify](https://dify.ai/) is an intuitive LLM application development platform for creating and operating AI-native apps. With the Apify integration for Dify, you can connect Apify Actors and storage to your Dify Workflows and Chatflows. You can run scrapers, extract data, and trigger workflows based on Apify events.
+
+In this guide, you'll learn how to set up authentication and incorporate the Apify plugin into your Dify applications as either a tool (action) or a trigger.
+
+## Prerequisites
+
+Before you begin, make sure you have:
+
+- An [Apify account](https://console.apify.com/)
+- A [Dify account](https://dify.ai/) (self‑hosted or cloud)
+
+## Authentication
+
+To connect your Apify account, you need to configure the plugin with your Apify API token.
+
+1. In Dify, navigate to **Plugins** from the top menu.
+2. Click on the **Install plugin → Marketplace**
+3. Find the **apify-integration** plugin and install it.
+4. Return back to the **Plugins** page. There will be our plugin. 
+6. Open the plugin window and click on the **Add API Key**.
+5. In the pop-up menu, paste your Apify API token. You can find it in the [Apify Console](https://console.apify.com/settings/integrations).
+4. Click **Save**.
+
+![Apify Auth in Dify](../images/dify-connection-popup.png)
+
+A green indicator light confirms that your credentials are correct.
+
+![Apify Auth in Dify](../images/dify-connection-success.png)
+
+With authentication set up, you can now add Apify tools to your applications.
+
+## Using Apify Tools in a Workflow
+
+Start by creating a workflow in Dify, then add Apify tools to handle tasks like running Actors or fetching data.
+
+1. In the Dify Studio, create a new **Workflow** application.
+2. Choose **Create from Blank**.
+3. Click the **+** icon on the **Start** node and select an Apify tool to add it to your board.
+
+![Adding an Apify Tool in Dify](../images/dify-workflow-create.png)
+![Adding an Apify Tool in Dify](../images/dify-workflow-start.png)
+
+### Use Apify as an action
+
+Actions allow you to perform operations like running an Actor within a workflow. For instance, you could trigger a scraper and then use its results in subsequent steps.
+
+#### Run an Actor
+
+1. Add the **Run Actor** tool to your workflow.
+2. Configure it:
+    - **Actor ID**: The unique ID of the Actor to run. For example, `2Mdma1N6Fd0y3QEjR` for the Google Maps Scraper.
+    - **JSON body for input**: The JSON input for the Actor run.
+      ```json
+      {
+        "language": "en",
+        "locationQuery": "New York, USA",
+        "maxCrawledPlacesPerSearch": 50,
+        "searchStringsArray": [ "restaurant" ],
+        "skipClosedPlaces": false
+      }
+      ```
+    - **Wait for finish**: Select `True` to make the workflow wait for the run to complete.
+![Adding an Apify Tool in Dify](../images/dify-configure-actor-run.png)
+3. Configure an **End** node and configure its output variable to use the `json` result from the **Run Actor** node.
+
+![Run Actor Node Configuration](../images/dify-configure-end-node.png)
+
+After that we can start the workflow and see the results.
+
+![Run Actor Node Configuration](../images/dify-ready-actor-flow.png)
+
+#### Run an Actor task
+
+1. Add the **Run Actor task** tool to your workflow.
+2. Enter the **Task ID** you want to execute (e.g., `FThsabHGXorVhWbPV`).
+3. Add an **End** node and map its output variable to the `json` result from this tool.
+
+![Run Actor Task Node](../images/dify-task-input.png)
+![Run Actor Task Node](../images/dify-task-succeded.png)
+
+#### Scrape Single URL
+
+1. Add the **Scrape Single URL** tool.
+2. Enter the **URL** to scrape (e.g., `https://docs.apify.com/`).
+3. Select the **Crawler type**. **Raw HTTP** is recommended for speed to work within Dify's timeout limits.
+4. Add an **End** node and map its output variable to the `json` result.
+
+![Scrape Single URL Node](../images/dify-scrape-input.png)
+![Scrape Single URL Node](../images/dify-scrape-succeded.png)
+
+#### Get Dataset Items
+
+1. Add the **Get Dataset Items** tool.
+2. Enter the **Dataset ID** to retrieve items from. (e.g., `58S2Um7hSXWYghZhn`)
+3. Add an **End** node and map its output to the tool's `json` result.
+
+![Get Dataset Items Node](../images/dify-dataset-input.png)
+![Get Dataset Items Node](../images/dify-dataset-succeded.png)
+
+#### Get Key-Value Store
+
+1. Add the **Get Key-Value Store** tool.
+2. Enter the **Store ID** and **Key** for the record you want to retrieve. (e.g., Store ID `fC0qZmL5RWIxoJG8z`, Record Key `INPUT`)
+3. Add an **End** node and map its output to the tool's `json` result.
+
+![Get Key-Value Store Node](../images/dify-key-value-input.png)
+![Get Key-Value Store Node](../images/dify-key-value-succeded.png)
+
+## Use Apify as a trigger
+
+Triggers let your Dify application respond automatically to events in Apify, such as when an Actor run finishes. This is ideal for creating event-driven automations.
+
+1. In your Dify app, go to **Overview** > **Endpoints**.
+2. Click the **+** icon to create a new endpoint.
+3. Select the **Workflow** or **Chatflow** application you want to trigger and give it a name.
+4. **Save** the endpoint. Dify will generate two URLs.
+
+![Create Dify Endpoint](../images/dify-workflow-input.png)
+![Create Dify Endpoint](../images/dify-trigger-url.png)
+
+5. Copy the URL that corresponds to your application type (Workflow or Chatflow).
+6. In the Apify Console, open the Actor you want to use as a trigger.
+7. Go to the **Integrations** tab and select the **HTTP webhook** option.
+8. Paste the Dify endpoint URL.
+9. Under **Events**, select **Run succeeded**.
+10. **Save** the integration.
+
+![Create Dify Endpoint](../images/dify-trigger-webhook.png)
+![Create Dify Endpoint](../images/dify-trigger-apify-console.png)
+
+> **IMPORTANT: Publish Required**
+> A Dify Workflow or Chatflow **must be published** for the webhook trigger to work. If the application is not published, the webhook will fail.
+> ![Create Dify Endpoint](../images/dify-workflow-publish.png)
+
+To confirm that your webhook is working, you can create a simple workflow that catches the incoming data from Apify and sends it to a third-party request catcher like [Webhook.site](https://webhook.site/). This provides an easy way to inspect the data we send.
+![Create Dify Endpoint](../images/dify-trigger-workflow.png)
+
+Now we can start the Actor in the Apify Console and it will trigger our workflow.
+
+![Create Dify Endpoint](../images/dify-trigger-succeded.png)
+
+The setup for a Chatflow is nearly the same. The only differences are to select your Chatflow app instead of a Workflow and to copy the specific Chatflow endpoint URL.
+
+> **Chatflow Trigger Requirement**
+> Also, when triggering a **Chatflow**, you **must** provide a **Payload template** in the Apify webhook settings. This template needs a `query` field to serve as the first message to the chatflow.
+> ![Chatflow Payload Template](../images/dify-trigger-query.png)
+
+### Accessing Apify Data in Dify
+When an event in Apify triggers your Dify endpoint, Apify sends a detailed nested response [JSON object](https://docs.apify.com/api/v2/act-runs-post#responses) containing information about the event. We can use this data to power our workflow.
+
+Dify cannot directly use nested syntax like `resource.id` in its variable system. Instead, it requires you to access nested properties using a flattened format (`resource__id`), where each level of nesting is represented by a double underscore (`__`).
+
+To work with a nested property in your workflow, you must first define it as an input variable in your workflow's Start node by clicking `+`.
+
+![Chatflow Payload Template](../images/dify-workflow-input-variable.png)
+
+![Chatflow Payload Template](../images/dify-define-input-variable.png)
+
+![Chatflow Payload Template](../images/dify-workflow-with-input-variable.png)
+
+We can also use that variable inside a JSON object we send and see the results.
+
+![Chatflow Payload Template](../images/dify-input-variable-webhook.png)
+
+![Chatflow Payload Template](../images/dify-input-variable-webhook-succeded.png)
+
+## Troubleshooting
+
+- Ensure your JSON inputs in fields are valid and properly formatted.
+
+If you have any questions or need help, feel free to reach out to us on our [developer community on Discord](https://discord.com/invite/jyEM2PRvMU).