CHATBOTS

Weekly Benefits Policy Change Digest to Teams

On a schedule, scans the HR Confluence space for recently updated benefits pages, summarizes what changed, and posts a plain-English digest to a Teams channel.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionFetch recently updated HR Confluence pagesConfluenceConfluence
  • LogicFilter to substantive changes only
  • ActionSummarize each change in plain English via OpenAIOpenAI
  • OutputPost the change digest to the Teams channelMicrosoft Teams

What it does

Keeps employees current by detecting which benefits and HR policy pages in Confluence changed during the week and posting a digestible summary to Teams. Instead of silent edits, staff get a clear "here's what's new" note with links.

When to use it

When open enrollment, plan changes, or policy revisions happen often and people miss them. Run it weekly so the whole company sees material changes without anyone manually writing an announcement.

How it works

  1. 1A weekly schedule fires the workflow.
  2. 2The flow queries the HR Confluence space for pages updated since the last run.
  3. 3It filters out trivial edits (typos, formatting) and keeps substantive changes.
  4. 4For each meaningful change, OpenAI writes a one-line plain-English summary of what was added or revised.
  5. 5The summaries are compiled into a single formatted digest with page links.
  6. 6The digest is posted to the designated Teams channel for the whole team to see.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ConfluenceSpaces, pages, blueprints.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  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.