CHATBOTS

Microsoft Teams Metric-Definition Bot

Answers Microsoft Teams questions about how a business metric is calculated by pulling its canonical SQL definition and source columns from the warehouse and dictionary.

CategoryChatbots
Enginepaperclip
Difficultyintermediate
Triggerchat
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerTeams message naming a metricMicrosoft Teams
  • ActionFetch canonical definition + SQL from CodaCodaCoda
  • ActionVerify source columns in Snowflake schemaSnowflakeSnowflake
  • LogicAdd deprecation/contested warnings
  • OutputReply in Teams with definition, sources, caveatsMicrosoft Teams

What it does

Resolves the endless "how is revenue actually calculated?" debate. In Microsoft Teams, anyone can ask about a metric and get its canonical definition, the exact source columns and filters behind it, and any known caveats.

When to use it

When finance, sales, and product each compute the same metric differently and you need one authoritative answer surfaced where people already chat.

How it works

  1. 1A message in Microsoft Teams names a metric (for example "net revenue retention").
  2. 2The flow fetches the metric's canonical definition and SQL snippet from the Coda metrics catalog.
  3. 3It resolves the underlying source columns against the live Snowflake schema to confirm the inputs still exist and are typed as documented.
  4. 4A logic step checks whether the metric is marked deprecated or contested and adds the appropriate warning.
  5. 5The bot replies in Teams with the plain-English definition, the source columns, the calculation logic, and any caveats.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Microsoft TeamsChannels, chats, files.
  2. 2
    Connect CodaDocs, packs, automations.
  3. 3
    Connect SnowflakeWarehouses, queries, shares.
  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.