Show and tell: an HTTP Request node that checks a workflow's draft before anyone sends it

[Fikpeze123]

Hi everyone — I'm Frank, founder of Pactlyst.ai (built with AI help, openly). Sharing a workflow pattern we use, in case it helps other Dify builders.

One of my test workflows drafts supplier renewal letters: a chatflow reads the old agreement, an LLM node writes the renewal draft, and then — in most setups I've seen — the draft just goes out, or sits in a chat window for a human to skim. Skimming isn't checking. So the node before "send" is an HTTP Request node pointed at Pactlyst Work Check:

POST https://api.pactlyst.ai/functions/v1/work-check
Authorization: Bearer $PACTLYST_KEY

{
  "work_text": "<the LLM node's draft letter>",
  "work_type": "document",
  "ask": "Draft a renewal letter on the same price and term as the current agreement.",
  "requesting_agent": "dify-renewal-workflow"
}

Two things come back that a skim doesn't give you. First, a verdict with findings: the work is read against document playbooks (the same door checks code and software work too) and scored — Low risk, Needs review, or High risk. Second, a gate your workflow can branch on: Low risk continues the flow; Needs review holds until a named human acknowledges the actual findings; High risk holds for a named approver who isn't the requester. Every check ends in a signed PactCheck Receipt™ with a public link — months later, "who reviewed this letter before it went to the supplier?" has an answer with a name on it. One more detail I care about: the ask travels with the work, and the result grades the draft against it — a letter that quietly changed the price comes back flagged as doing the opposite of what was asked. Your draft text itself is never stored; the receipt keeps the hash and counts.

Honest framing: this is not an official Dify plugin and there's no partnership here — it's Dify's own HTTP node plus a free API key, a few minutes to wire.

We're taking a few design partners whose workflows draft things that leave the building — three months of Pro free. Docs: pactlyst.ai/docs. And if you place review steps in your workflows differently, I'd genuinely like to hear how.

— Frank