Compatible (BYOK)

Use Dify with GlideflowAI.

A workflow platform for building and operating LLM applications. Connect it through GlideflowAI's OpenAI-compatible API with a key you control.

Get a key

What this connection is for

Dify is an application platform for assembling prompt apps, chat experiences, workflows, and knowledge-backed features around language models. It is for teams that want an operational application surface and workflow controls without implementing every orchestration component in code. Model providers are configured as part of a workspace, while individual apps can use the resulting models in their prompts and flows.

Choose Dify when non-code workflow composition, app publishing, and workspace management matter more than owning every runtime primitive. It is not a replacement for a lightweight SDK when a developer only needs one server-side completion. Provider plugins and forms can vary by release, so verify the available compatible-provider option in your installed Dify environment before changing a shared workspace setting.

Use Dify's documented OpenAI-compatible model-provider path and enter GlideflowAI's /v1 URL, a private key, and an exact model ID. Validate the provider in a draft app first, then confirm the workflow uses the intended model before publishing it. Document the chosen model in the app configuration so later workflow edits do not obscure that dependency. Dify is an independent project; this is a user-managed connection, not an endorsement or partnership.

Why pair it with GlideflowAI

Dify can use a GlideflowAI provider for a draft workflow while keeping the platform's prompts, knowledge sources, and app controls in the same workspace.

The gateway catalog gives an operator a clear model ID to enter when a Dify provider form does not offer a prebuilt selection.

Setup

Use a new API key for the tool, select a model from the catalog, and begin with a small task. Do not put a key in a repository, screenshot, or shared configuration file.

1
Choose Dify's documented compatible provider path
In the installed Dify release, use its supported OpenAI-compatible model-provider mechanism. Do not inject provider values into an undocumented container or database setting.
```
Provider protocol : OpenAI Compatible
```
2
Enter gateway values and validate a draft app
Add the endpoint, key, and model in the provider fields Dify exposes, then test with a draft workflow before publishing.
```
Base URL : https://api.glideflowai.com/v1
API key  : sk-your-key
Model ID : deepseek-v4-pro
```

Before you begin: Manual check: Dify's provider plugins and model-provider UI can vary by release; use the current OpenAI-compatible provider path rather than an undocumented configuration file.

Need the endpoint basics? Read authentication, browse the model catalog, or compare pricing.

Frequently asked questions

Where should I add GlideflowAI in Dify?

Use the current Dify OpenAI-compatible model-provider mechanism, not an undocumented environment variable, database edit, or container patch.

Should I test a provider in a published app first?

No. Create or use a draft app so you can verify the model, key, and response behavior before exposing a workflow to users.

Why is there a Manual check note for Dify?

Dify provider plugins and UI can differ across releases, so this page does not promise a stable menu path that may not exist in your deployment.

Is this an official integration?

No. The connection is configured by you using a compatible API and does not imply sponsorship, endorsement, or a partnership.

Ready to connect Dify?

Create a key, use the setup above, and verify the connection on a small task before you scale it up.