Open
Conversation
TC-MO
reviewed
Mar 3, 2026
Contributor
TC-MO
left a comment
There was a problem hiding this comment.
Few fixes necessary
- remove gerund from heading
- use italics for emphasis not bold
- imperative sentence instead of
we recommendstructure
|
|
||
| ### Set up a webhook endpoint | ||
|
|
||
| In Dify, navigate to **Plugins** from the top menu. Click on your plugin and lookf for **Endpoints** section. Select the **+** icon to create a new endpoint. Choose the **Workflow** or **Chatflow** application you want to trigger and give it a name. Select **Save** — Dify will generate two URLs. |
Contributor
There was a problem hiding this comment.
typo
Suggested change
| In Dify, navigate to **Plugins** from the top menu. Click on your plugin and lookf for **Endpoints** section. Select the **+** icon to create a new endpoint. Choose the **Workflow** or **Chatflow** application you want to trigger and give it a name. Select **Save** — Dify will generate two URLs. | |
| In Dify, navigate to **Plugins** from the top menu. Click on your plugin and look for **Endpoints** section. Select the **+** icon to create a new endpoint. Choose the **Workflow** or **Chatflow** application you want to trigger and give it a name. Select **Save** — Dify will generate two URLs. |
Comment on lines
+195
to
+198
| 1. **Define the dataset ID variable**: In your workflow's Input node, add an input variable named `resource__defaultDatasetId` to capture the dataset ID from the webhook payload. | ||
| 1. **Add the Get Dataset Items tool**: Add the **Get Dataset Items** Apify tool to your workflow. | ||
| 1. **Use the variable**: In the **Dataset ID** field of the Get Dataset Items tool, reference your input variable (e.g., `{{resource__defaultDatasetId}}`). | ||
| 1. **Process the data**: The tool retrieves all items from the dataset, which you can then process, transform, or send to other services in your workflow. |
Contributor
There was a problem hiding this comment.
Suggested change
| 1. **Define the dataset ID variable**: In your workflow's Input node, add an input variable named `resource__defaultDatasetId` to capture the dataset ID from the webhook payload. | |
| 1. **Add the Get Dataset Items tool**: Add the **Get Dataset Items** Apify tool to your workflow. | |
| 1. **Use the variable**: In the **Dataset ID** field of the Get Dataset Items tool, reference your input variable (e.g., `{{resource__defaultDatasetId}}`). | |
| 1. **Process the data**: The tool retrieves all items from the dataset, which you can then process, transform, or send to other services in your workflow. | |
| 1. _Define the dataset ID variable_: In your workflow's Input node, add an input variable named `resource__defaultDatasetId` to capture the dataset ID from the webhook payload. | |
| 1. _Add the Get Dataset Items tool_: Add the **Get Dataset Items** Apify tool to your workflow. | |
| 1. _Use the variable_: In the **Dataset ID** field of the Get Dataset Items tool, reference your input variable (e.g., `{{resource__defaultDatasetId}}`). | |
| 1. _Process the data_: The tool retrieves all items from the dataset, which you can then process, transform, or send to other services in your workflow. |
|
|
||
| When an Apify Actor run completes and triggers your Dify workflow, Apify sends a [JSON response object](https://docs.apify.com/api/v2/act-runs-post#responses) containing information about the completed run. This includes details like the run ID, Actor ID, dataset ID, and status. | ||
|
|
||
| #### Understanding nested data access |
Contributor
There was a problem hiding this comment.
Suggested change
| #### Understanding nested data access | |
| #### Understand nested data access |
|
|
||
| #### Scrape Single URL | ||
|
|
||
| Add the **Scrape Single URL** tool and enter the **URL** to scrape (for example, `https://docs.apify.com/`). Select the **Crawler type**, we recommend **Raw HTTP** for faster execution within Dify's timeout limits. Add an **Output** node and map its output variable to the result. |
Contributor
There was a problem hiding this comment.
Suggested change
| Add the **Scrape Single URL** tool and enter the **URL** to scrape (for example, `https://docs.apify.com/`). Select the **Crawler type**, we recommend **Raw HTTP** for faster execution within Dify's timeout limits. Add an **Output** node and map its output variable to the result. | |
| Add the **Scrape Single URL** tool and enter the **URL** to scrape (for example, `https://docs.apify.com/`). Select the **Crawler type**, use **Raw HTTP** for faster execution within Dify's timeout limits. Add an **Output** node and map its output variable to the result. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A new PR for dify docs based on the: #2037 with new screenshots and fixes from the PR comments.
We can close the old PR and keep this one.
Note
Low Risk
Documentation-only change adding a new integration guide; primary risk is broken links or outdated UI screenshots.
Overview
Adds new docs page
integrations/difydescribing how to connect Apify with Dify via theapify-integrationplugin.Covers authentication (API token/OAuth), using Apify as workflow actions (run Actor/task, scrape URL, fetch dataset/KV store), and setting up webhook triggers from Apify to Dify, including guidance on Dify’s flattened variable naming for nested webhook payload fields (e.g.,
resource__defaultDatasetId).Written by Cursor Bugbot for commit aba66ef. Configure here.