Keep your docs true
When a doc changes, find everything that now contradicts it and route the fixes.
A single source of truth stops being one the moment somebody edits it. Change the trial length on the pricing page and the sales deck, two help articles and the onboarding email are now wrong. This workflow reacts to the edit itself: it finds everything that now disagrees and routes each fix to its owner.
What does this workflow do?
When a watched document changes in Notion, Google Docs, or Confluence, the workflow extracts the facts that moved: numbers, names, dates, terms, promises, as old-to-new pairs. Then it sweeps everything it can see for the old fact, the new fact, and the near misses: passages that paraphrase the old truth without stating it ("a two-week trial" when the number moved to 30 days).
Each contradiction goes to the document's likely owner as a one-line question with the proposed fix. With their reply, the agent applies the edit. It also chases second-order breaks: places where the change's implications, not its words, create contradiction, like the "day 15 upgrade email" that just became mid-trial instead of end-of-trial.
How does it work?
- An edit triggers the sweep. A watched page changes, and the workflow reads what moved. A scheduled full sweep catches drift between edits.
- The agent extracts the facts that changed. Old to new pairs: prices, durations, names, policies, promises.
- It sweeps for contradictions. Direct statements of the old fact, paraphrases, and second-order implications, across Notion, Google Docs, Google Drive and Confluence, with permissions respected throughout.
- It routes each fix to its owner. A one-line question with the proposed edit: "Pricing page now says 30-day trial. The sales deck says 14. Update the deck to match?" A reply applies the fix.
- It reports the sweep. What was fixed, what's pending an owner's answer, and which documents were checked and found clean, so silence is distinguishable from unswept.
What makes this different from version control for docs?
Version history tells you what changed inside one document. This workflow tells you what that change broke everywhere else. It's Agentwork's contradiction detection running as a reflex instead of an audit: the same capability that flags conflicting answers when your team asks questions, pointed at the moment drift actually begins. Notion and Confluence both keep page history and backlinks; neither reads the sales deck against the pricing page and asks the owner which is true.
The maintained result is what everything else runs on. Every other workflow in the library answers from this knowledge base, so keeping it true is the compounding investment.
Works with
Notion, Google Docs, Google Drive, Confluence, Slack. Triggered by edits to watched documents, plus a scheduled full sweep.
Frequently asked questions
Which documents should I watch?
The load-bearing ones: pricing, policies, positioning, onboarding, security pages. Anything whose facts appear in other documents. You can add or remove watched documents anytime.
Does it edit documents on its own?
No. Each proposed fix goes to the document's owner, and the agent applies the edit when they reply. Nothing changes without a person agreeing.
What are second-order breaks?
Contradictions created by a change's implications rather than its words. If trials go from 14 to 30 days, a "day 15 upgrade email" isn't wrong on its face, but its logic broke. The workflow flags these separately because they're the ones humans miss.
What if the owner says the old document is the correct one?
Then the fix flows the other way: the newly edited page gets flagged back to its editor. Newer is a hypothesis, not a verdict, and the owner settles it.
How does it know who owns a document?
From ownership you've configured, or inferred from who edits and answers questions about it, labeled as a guess until confirmed. Corrections are remembered.