Docs › Dify and Flowise with RunVouch

Dify and Flowise with RunVouch

Both tools expose a workflow or chatflow over HTTP; the schedule lives outside them, in cron, n8n or a cloud scheduler. That outside caller is the thing that stops quietly.

How it runs on Dify and Flowise

Wrap the caller script with rv run; the script calls the Dify (/v1/workflows/run) or Flowise (/api/v1/prediction/{id}) endpoint and writes the answer to a file that serves as evidence.

Store the key

An environment variable in the caller's environment; the Dify or Flowise API key stays where it is.

Wrap the job

# crontab
0 7 * * * rv run daily-brief --evidence-file /out/brief.json -- python call_dify.py

# call_dify.py
import json, os, requests
r = requests.post("https://api.dify.ai/v1/workflows/run", timeout=600,
    headers={"Authorization": f"Bearer {os.environ['DIFY_KEY']}"},
    json={"inputs": {"topic": "overnight"}, "response_mode": "blocking", "user": "cron"})
r.raise_for_status()
json.dump(r.json(), open("/out/brief.json", "w"))

rv fails open: if RunVouch is unreachable the job still runs and you get one warning line.

Register the cadence and caps

rv agent nightly-report --cadence 24h --grace 30m --max-runtime 1h --evidence --cap-run-cost 2

Register the agent once, from anywhere with the key. Cadence is what turns a schedule that stopped into an alert; --evidence makes a run without evidence a failure; the caps pause the agent when it overspends.

What goes silent on Dify and Flowise

• A workflow that returns 200 with an empty outputs is a success to the caller; the evidence file being empty is not.
• Token usage is in the Dify response (metadata.usage); pass it as cost with rv end for the daily cap.

What RunVouch detects

Need a key? Get a free key · Stuck? contact