Dify
for LuumenAI

Inspect Dify workflow runs, then trigger the published workflow on approval

Connect a published Dify Workflow app and Luumen can read its configuration, list recent runs, and pull the inputs, outputs, and error detail for any single run. When you need the workflow to actually execute, Luumen previews the inputs it would send and asks before running it. Authentication is by API key.

Book a DemoDownload Luumen

The Dify toolbox

4 tools: 3 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet Workflow App ConfigurationReturn the connected Workflow app's identity, declared input form and upload limits, tool icons, and hosted-site settings.
  • ReadGet Workflow RunReturn one workflow run's status, inputs, arbitrary outputs, error, and execution metrics by run ID.
  • ReadList Workflow RunsReturn one page of run summaries for the connected Workflow app, with filters and a continuation cursor for older or additional runs.
  • WriteRun WorkflowRun the connected app's latest published workflow in blocking mode and return its app-defined outputs. Approval by default

One prompt, start to finish

What a governed Dify run looks like inside Luumen.

Questions

How does LuumenAI connect to Dify?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Dify on its own?

Read actions answer immediately. Anything that writes — run workflow — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Dify — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task statusAffindaRead parsed documents, collections, and annotations — change them with approvalAgent MailGive the agent its own mailbox for reading threads and sending updatesAI/ML APIInspect assistants, threads, and runs — and change them as approved steps

Put Dify to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.

Book a DemoDownload Luumen