Open
Conversation
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
1 participant
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.