Skip to content

docs: dify docs#2254

Open
jakcinmarina wants to merge 1 commit intoapify:masterfrom
jakcinmarina:docs/dify-docs
Open

docs: dify docs#2254
jakcinmarina wants to merge 1 commit intoapify:masterfrom
jakcinmarina:docs/dify-docs

Conversation

@jakcinmarina
Copy link
Contributor

@jakcinmarina jakcinmarina commented Feb 13, 2026

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/dify describing how to connect Apify with Dify via the apify-integration plugin.

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.

@jakcinmarina jakcinmarina requested a review from TC-MO as a code owner February 13, 2026 16:08
Copy link
Contributor

@TC-MO TC-MO left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few fixes necessary

  • remove gerund from heading
  • use italics for emphasis not bold
  • imperative sentence instead of we recommend structure


### 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants