CHATBOTS

Weekly Orphaned-Service Owner Digest to Teams

Every Monday, scans the service catalog for services with no listed owner or stale ownership.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires Monday morning
  • ActionQuery catalog for missing or stale ownershipPostgreSQLPostgres
  • LogicFilter out fully-owned, recently-reviewed services
  • ActionFetch latest committer per orphaned repoGitHubGitHub
  • OutputPost the ownership-gap digest to TeamsMicrosoft Teams

What it does

On a weekly schedule, this workflow audits your Postgres service catalog for ownership gaps: services with a null owner, an owner who has left, or a 'last reviewed' date older than your threshold. For each gap it checks GitHub for the most recent committer as a suggested owner, then posts a single digest to a Teams channel.

When to use it

Run it when service ownership data drifts and incidents keep landing on the wrong team. The weekly nudge keeps the catalog honest without anyone manually auditing it.

How it works

  1. 1A weekly schedule trigger fires Monday morning.
  2. 2The Postgres step queries the catalog for services with missing or stale ownership.
  3. 3A filter drops services that are fully owned and recently reviewed.
  4. 4For each remaining service, GitHub returns the latest committer as a candidate owner.
  5. 5The results are assembled into a ranked digest table.
  6. 6The digest posts to the platform-team Teams channel, tagging the suggested owner for each gap.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect GitHubRepos, issues, pull requests, actions.
  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.