AI & RAG

Answer citation freshness audit

Reviews recent policy-bot answers, re-checks each cited source against the live Confluence and Drive documents.

CategoryAI & RAG
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionRead recent answers + citations from SupabaseSupabaseSupabase
  • ActionRe-fetch live state of cited Confluence/Drive docsConfluenceConfluence
  • LogicFlag answers with changed or deleted sources
  • OutputMark needs-review in Supabase + Slack digestSlack

What it does

Guards against stale answers. It reads the log of answers your policy bot has given, re-fetches every cited source, and detects when the underlying document has been edited or removed since the answer went out. Affected answers are flagged for follow-up.

When to use it

Use it when policy changes frequently and you have already given automated answers that may now be wrong. It is a trust-and-safety layer for any deployed RAG Q&A system, surfacing answers that need a correction or re-send.

How it works

  1. 1A scheduled trigger starts the audit (e.g. daily).
  2. 2The workflow reads recent answers and their cited source IDs from the Supabase answer log.
  3. 3It re-fetches each citation's current state from Confluence and Drive.
  4. 4A diff check flags answers whose sources changed materially or no longer exist.
  5. 5Flagged answers are written back to Supabase as needs-review and a digest is posted to Slack for the owning team.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SupabaseTables, auth, storage, edge functions.
  2. 2
    Connect ConfluenceSpaces, pages, blueprints.
  3. 3
    Connect Google DriveDocs, sheets, slides, files.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.