Automated Perplexity Claim Fact Checking
Whenever you hand WebRun a draft, it pulls out every factual claim, asks Perplexity about each one in its own thread, reads the answer and its citations, marks the claim supported, contradicted, or unverified with the source link beside it, posts the review to Slack, and drafts an email back to the writer.
How do I fact check the claims in a draft before it is published?
Hand WebRun a draft and it takes each factual claim in it to Perplexity, runs a sourced check, and marks the claim supported, contradicted, or unverified with the citation beside it. It posts the marked-up review to Slack and drafts an email back to the writer, so nothing unsupported reaches a customer.
- Every factual claim is marked and sourced before publication
- Contradicted claims are listed first, so the riskiest fix happens first
- The note to the writer is written and waits in Drafts
Built for writers · editors · content marketers · communications teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
perplexity.aiin a real browser with your saved login - no setup, no API keys. -
1
Perplexity - check each claim against sources
perplexity.ai
WebRun opens Perplexity to check each claim against sources. - Read the draft you handed over and list every factual claim in it
- Open Perplexity and type each claim as its own prompt, one thread per claim
- Read the answer and the citations it returns
- Mark the claim supported, contradicted, or unverified and keep the source links
Done when Every factual claim in the draft is marked and carries its source links.
-
2
Slack - post the marked-up review
slack.com
WebRun opens Slack to post the marked-up review. - Post the marked-up review to the editorial channel
- List contradicted claims first, then unverified ones, then supported
- Put the source link and the quoted claim on every line
Done when The editorial channel has the full claim review in Slack.
-
3
Gmail - draft the note back to the writer
gmail.com
WebRun opens Gmail to draft the note back to the writer. - Draft a note to the writer listing the claims that need a fix or a source
- Quote each claim and paste the citation underneath it
- Leave the email unsent in Drafts. You read it and send it
Done when A review email sits unsent in Gmail Drafts for the writer.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it upload my draft anywhere?
No. File uploads are blocked by policy. WebRun types each claim into Perplexity as a question, one claim at a time, so the full document is never posted to any site.
Will it publish or send the piece?
No. It never publishes, and the note back to the writer is left unsent in Gmail Drafts. WebRun reviews the draft. A human decides what happens to it.
What does unverified mean?
It means Perplexity returned no source that clearly supports or contradicts the claim. WebRun marks it rather than guessing, so an editor knows exactly which lines still need evidence.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.