Choosing a Dify plugin type
Deciding between tool, model, agent strategy, extension, datasource and trigger plugins for an internal integration, and when an OpenAPI tool or custom endpoint avoids writing a plugin at all.
Dify plugins and custom tools
Extending a self-hosted Dify with plugins and custom tools: choosing the plugin type, building and distributing private plugins, and operating the plugin daemon.
Building a custom Dify model provider plugin
Making an internal model gateway or fine-tuned model selectable in Dify through a model plugin: model types it can expose, credential schema and why model plugins cannot bundle tools.
Building a Dify tool plugin with OAuth
Writing a tool plugin that calls an internal system on behalf of users with OAuth, packaging it as .difypkg and handling credentials per workspace.
Building a Dify datasource plugin for internal systems
Indexing documents from a document management system, wiki or file share that has no official plugin, by writing a datasource plugin for knowledge pipelines.
Building a Dify trigger plugin for event-driven workflows
Starting Dify workflows from events in ticketing, CRM or monitoring systems with a custom trigger plugin, and the public trigger endpoint it depends on.
Private Dify plugin distribution
Choosing between Marketplace, GitHub and local .difypkg distribution for internal plugins, versioning releases, and signing packages so production keeps signature checks on.
Dify custom tools from OpenAPI specifications
Turning an internal REST API into a Dify tool by importing its OpenAPI or Swagger schema, handling authentication, and reaching internal hosts through the SSRF proxy allowlist.
Publishing Dify workflows as reusable tools
Wrapping a workflow that starts with a User Input node as a tool other apps call, why chatflows cannot be tools, and version effects when the source workflow changes.
Dify custom endpoints for moderation and external data
Plugging in your own moderation or external data API through Dify's custom endpoint contract: bearer key validation, the ping check and where these hooks run in an app.
Operating the Dify plugin daemon
Running the plugin daemon in production: timeouts, package and file size limits, model schema caches, remote debugging ports and the shared inner API key with the API service.
Dify plugin installation policy on Enterprise
Controlling plugin risk across many workspaces: allowing all, official and partner, or Marketplace-only plugins, and installing one approved version in every current and future workspace.
