CHATBOTS

Handbook Sync: Re-Index the HR Bot When Notion Pages Change

Watches the HR handbook in Notion for edits and automatically refreshes the bot's knowledge index, then announces what changed so the helpdesk bot never quotes a stale policy.

CategoryChatbots
Enginesim
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHandbook page edited in NotionNotionNotion
  • ActionFetch updated page contentNotionNotion
  • ActionSummarize material changesOpenAI
  • ActionWrite updated content to bot knowledge index
  • LogicFilter out trivial edits
  • OutputPost change note to People team SlackSlack

What it does

This flow keeps the bot's answers trustworthy. Whenever a page in the HR handbook is edited in Notion, it re-indexes the changed content into the bot's knowledge base and posts a short change note to the People team, so the helpdesk bot always cites the current policy instead of an outdated one.

When to use it

Use this when your handbook changes often, open enrollment, comp-cycle, or policy updates, and you can't afford the bot answering from yesterday's version.

How it works

  1. 1A change to any handbook page in Notion fires the trigger.
  2. 2The flow fetches the updated page content and metadata.
  3. 3An LLM step summarizes what materially changed versus the prior version.
  4. 4The new content is written into the bot's knowledge index for retrieval.
  5. 5A logic step filters out trivial edits (typos, formatting) so only substantive changes are announced.
  6. 6The bot posts a concise change note to the People team Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect NotionPages, databases, comments.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.