Signed decision evidence for Dify workflows.
Record agent decisions, external actions, outcomes and human reviews in Dify. Verify your evidence trail without changing the agent runtime.
LoopGrid for Dify v0.1.0 · Tool plugin · Compatible with reachable LoopGrid deployments.
LoopGrid records and verifies evidence; it does not execute payments, refunds or other external business actions.
Install the LoopGrid tool plugin.
- Open the LoopGrid listing in Dify Marketplace ↗.
- Install the plugin into your Dify workspace.
- Open the plugin provider configuration and connect your LoopGrid deployment.
127.0.0.1 on your own computer is not reachable from Dify Cloud.One credential for the workflow.
Configure these three provider credentials:
defaultFor access to all six tools, a key with ingest, read and review scopes is sufficient. Keep the key in Dify provider credentials, not in workflow text or screenshots.
Six tools, one evidence lifecycle.
Capture the decision envelope, agent identity, context and proposed action.
Append evidence of an action performed by a separate workflow tool or service.
Attach the observed downstream result to the same decision.
Record a human approval or rejection for a reviewable decision.
Retrieve the recorded evidence and lifecycle history.
Check the captured evidence integrity through the connected LoopGrid service.
Record what was proposed and what actually happened.
Use explicit LoopGrid tool nodes in a Dify Workflow or Chatflow. Do not depend on an LLM remembering to call the evidence tool.
Dify agent / model → LoopGrid: Record Decision → Policy or approval step, when required → External action tool (for example, your refund API) → LoopGrid: Record Action → Observe authoritative downstream result → LoopGrid: Record Outcome → LoopGrid: Get Decision → LoopGrid: Verify Decision
Pass the returned decision_id through the subsequent LoopGrid nodes. Use an external reference to correlate the external action and observed outcome. Submit Review is available for decisions that require human oversight.
Integrity verification is not action execution.
Only send the evidence fields the workflow needs. Record an authoritative downstream response when claiming that an external action happened. Verification checks captured evidence integrity and provenance; it does not establish decision correctness, capture completeness or legal compliance.
Start with one consequential workflow.
Record the decision, correlate the external action and its observed outcome, then verify the captured evidence.