CONTENT CREATION
Fact-check blog PRs in your content repo and comment on the diff
When a pull request adds or edits Markdown posts, an agent fact-checks the changed claims and leaves a PR comment flagging each unsourced or contradicted statement before…
How it runs
The automated pipeline, trigger to output.
- TriggerPull request opened or updated in the content repoGitHub
- ActionFetch the diff and keep changed Markdown post linesGitHub
- ActionSearch Exa for a source per extracted claimExa
- LogicSeparate sourced claims from unsourced/contradicted ones
- OutputPost a PR review comment flagging weak claimsGitHub
What it does
For teams that keep their blog or docs as Markdown in Git, this workflow brings fact-checking into code review. On every pull request that touches post files, an agent reads the added and modified lines, isolates factual claims, verifies them against the web, and posts a review comment so unsourced statements get caught before merge.
When to use it
Use it when your content lives in a GitHub repo and publishing happens on merge. It fits engineering-adjacent content teams who already review prose in PRs and want claim verification to sit alongside lint and build checks.
How it works
- 1A pull request is opened or updated in the content repository, firing the trigger.
- 2The workflow fetches the PR diff and keeps only added or changed lines in Markdown post files.
- 3The agent extracts factual claims from those lines and searches Exa for a supporting source for each.
- 4A decision step separates claims that are sourced from those that are unsourced or contradicted.
- 5The workflow posts a PR review comment listing each weak claim with suggested sources, so reviewers can request changes before merging.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ExaNeural search across the web.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
On-demand: turn a blog URL into narrated B-roll clips
Accepts a blog URL via webhook, scrapes the article, generates a B-roll clip per paragraph with Replicate and a voiceover with ElevenLabs.
Sync a Figma master frame into localized hero renders
Pulls the current master hero frame and its text layers from Figma, generates a localized image variant for each locale defined in Airtable.
Build a Dropbox B-roll library from exported blog drafts
Triggers when a new blog draft file lands in a Dropbox folder, generates a Replicate B-roll clip for each paragraph.
Generate B-roll clips when a blog post is marked Ready in Notion
Watches a Notion blog database for posts flipped to 'Ready', splits the body into paragraphs, and generates a short B-roll video clip for each paragraph with Replicate.
Weekly: clip last week's top blog paragraph and post to socials
Runs on a weekly schedule, picks the highest-traffic paragraph from the past week's posts, generates one polished B-roll clip with Replicate.
On-Demand Screenshot Freshness Report from a Slack Command
A writer requests a freshness check in Slack for a specific docs page; the workflow inspects every screenshot on that page, scores each by age and version gap.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.