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.
4 tools: 3 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Dify run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as run workflow. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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.
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.
Connect in minutes. Every action scoped, approved, and audited from day one.