CHATBOTS

Teams Owner Bot with Confluence Runbook Context

An agent-driven Teams bot that answers ownership and 'how do I reach the owner' questions by combining the Postgres catalog, recent commits, and the service's Confluence runbook…

CategoryChatbots
Enginepaperclip
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerTeams mention with a free-form ownership questionMicrosoft Teams
  • ActionQuery Postgres catalog for owner and teamPostgreSQLPostgres
  • ActionPull recent commits to confirm active maintainersGitHubGitHub
  • ActionSearch Confluence for the service runbookConfluenceConfluence
  • LogicAgent reasons over sources to compose the answer
  • OutputReply in Teams with owner, escalation, and runbook linkMicrosoft Teams

What it does

This is a smarter ownership assistant. When someone asks about a service in Teams, an agent gathers three sources: the owner record from the Postgres catalog, the recent commit history from GitHub, and the service's runbook page from Confluence. It then composes a natural-language answer covering who owns it, how to escalate, and where the docs live.

When to use it

Use it when 'who owns this' questions usually become follow-ups like 'what's their escalation path' or 'where's the runbook'. The agent answers the whole chain in one pass instead of three separate lookups.

How it works

  1. 1A Teams mention triggers the agent with the user's free-form question.
  2. 2The agent resolves the service name and queries the Postgres catalog for the owner and team.
  3. 3It pulls recent GitHub commits to confirm active maintainers.
  4. 4It searches Confluence for the service's runbook and escalation section.
  5. 5The agent reasons over all three sources, deciding what the user actually needs.
  6. 6It replies in the Teams thread with the owner, escalation path, and a runbook link.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Microsoft TeamsChannels, chats, files.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect GitHubRepos, issues, pull requests, actions.
  4. 4
    Connect ConfluenceSpaces, pages, blueprints.
  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.