otherapi_key

Dify

Run and inspect a published Dify Workflow app through its Service API, including configuration and workflow run history.

Integration

Vendor
Dify
Category
other
Auth
API_KEY
Tools
4
Composio slug
dify

Tools

  • Get Workflow App Configuration

    Return the connected Workflow app's identity, declared input form and upload limits, tool icons, and hosted-site settings. If the app is unpublished, the response identifies the unavailable parameters section while preserving the other meta

  • Get Workflow Run

    Return one workflow run's status, inputs, arbitrary outputs, error, and execution metrics by run ID.

  • List Workflow Runs

    Return one page of run summaries for the connected Workflow app, with filters and a continuation cursor for older or additional runs.

  • Run Workflow

    Run the connected app's latest published workflow in blocking mode and return its app-defined outputs. Inspect the app configuration first: the configured workflow may perform irreversible external side effects.

Setup

  1. Create or open a Switchy Project.
  2. Open Integrations and connect Dify.
  3. Authorise through api_key. Switchy stores the connection against your org.
  4. Everyone in the Project can now @-mention the Dify tools in chat.

What teammates see: by default, memories from Dify are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Projects have used this MCP together with a given model.

How Switchy teams use it

Not enough Projects yet to publish anonymised usage stats (we require ≥ 50 Projects per week).

Starter prompts

Starter prompts for this model will land here soon.

More other MCPs

See all other MCPs

Data last verified 7 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.