CONTENT CREATION

Pre-publish webhook gate that returns pass or fail to your CMS

Your CMS calls this workflow before publishing; it fact-checks the draft's claims and returns a structured pass/fail verdict with reasons.

CategoryContent Creation
EngineSim + Paperclip
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerCMS sends a pre-publish webhook with the draftHTTP webhook
  • ActionVerify each extracted claim via PerplexityPerplexityPerplexity
  • LogicCompute pass/fail verdict from claim results
  • ActionLog run and verdict to Postgres audit tablePostgreSQLPostgres
  • OutputReturn structured pass/fail payload to the CMSHTTP webhook

What it does

This workflow is a synchronous fact-check gate any CMS or publishing tool can call over a webhook. It receives the draft, verifies the factual claims, and returns a machine-readable verdict, so your publishing system can hard-block a post that contains unsourced or contradicted claims rather than relying on a human to remember.

When to use it

Use it when you run a custom CMS, static-site pipeline, or headless publishing setup and want fact-checking enforced in code at the moment of publish. It is the right choice when a Slack nudge or calendar review is not a strong enough guarantee.

How it works

  1. 1The CMS sends a webhook containing the draft title and body at publish time.
  2. 2The agent extracts every factual claim and verifies each against the web.
  3. 3A decision step computes a verdict: pass when all claims are sourced, fail when any are unsourced or contradicted.
  4. 4The workflow logs the run and verdict to a Postgres table for an audit trail.
  5. 5It responds to the webhook with a structured payload (verdict, failing claims, suggested sources) the CMS uses to allow or block publication.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect PerplexitySearch-grounded answers with citations.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.