Conversation
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. |
There was a problem hiding this comment.
typo
| 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. |
| 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. |
There was a problem hiding this comment.
| 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 |
There was a problem hiding this comment.
| #### 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. |
There was a problem hiding this comment.
| 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. |
TC-MO
left a comment
There was a problem hiding this comment.
Two minor issues, otherwise LGTM
|
|
||
| With authentication set up, you can now add Apify tools to your applications. | ||
|
|
||
| ## Use Apify Tools in a Workflow |
There was a problem hiding this comment.
In headings I see Tools capitalized, in prose it's not, can we get it consistent?
|
|
||
| ### Set up a webhook endpoint | ||
|
|
||
| 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. |
There was a problem hiding this comment.
| 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. | |
| 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. |
|
@jakcinmarina is the integration live already? If so we can merge (rather I guess I , but need the confirmation :D) if not please let me know when it is supposed to so I can schedule merge |
Nope, not live yet. I will sync with Kuba and let you know :) @TC-MO |
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.