Connector

Post Open Exchange Rates reports to Microsoft Teams

Open Exchange Rates by currency and date, once a week. Open Exchange Rates goes into your data warehouse first, is linked there by SQL keys, and only then reaches Microsoft Teams. Colleagues read the answer in Teams, not an export of the source.

Open Exchange R…ConnectedHistorical excha…
Data MartPublishedone definition
Microsoft TeamsDateBaseCurre…Daily 09:00
Refreshed on a schedule. No exports, no copy-paste.

Get started free

Hand this to your AI

Revenue posted to Microsoft Teams mixes currencies, so regions can't be compared until someone converts it by hand.

Paste this into your AI assistant. It joins Open Exchange Rates to orders or invoices by date and currency in your data warehouse and posts revenue in one currency to the Microsoft Teams channel once a week.

The prompt

post weekly revenue by region converted to our base currency at Open Exchange Rates daily rates to our Microsoft Teams channel, with the rates used next to it

Endpoints

Open Exchange Rates Endpoints

Documentation

1 Open Exchange Rates endpoints you can import. Each lands in its own table in your data warehouse.

S00 · Why

Why Open Exchange Rates does not post straight to Microsoft Teams

Open Exchange Rates gives a rate for each currency and date, and a message posted from it lists rates. The sums your finance team needs come from joining those rates to orders and invoices, which neither the source nor the channel does. A Teams channel is read by people outside the team that built the report, so every number needs to explain itself. The join belongs in a data warehouse first.

  • Open Exchange Rates lists rates by currency, not converted revenue
  • A Teams channel reaches colleagues who never saw the source, so definitions must travel with the figures
  • The data analyst links the sources by SQL keys and controls what the message says
Open Exchange…Rates by currency
Microsoft Tea…
No link to revenue
Data warehouseJoined by id
OrdersOrder totals
InvoicesBilling, currency

S01 · Step 1

Step 1: Load Open Exchange Rates into your data warehouse first

Create a Data Mart with Open Exchange Rates as the data source and choose where the data lands. It works with any popular data warehouse.

  • One endpoint, Historical exchange rates data, with four fields: date, base, currency and rate
  • Authorize with your Open Exchange Rates App ID
  • Open the Open Exchange Rates connector for your data warehouse below
Open Exchan…Data Mart
Your data warehouseGoogle BigQueryAWS AthenaSnowflakeAWS RedshiftDatabricks
open_exchange_rates.historical

S03 · Step 3

Step 3: Post Open Exchange Rates reports to a Teams channel

Create a Microsoft Teams destination in OWOX with the email address of the channel, taken from the channel menu in Teams, then add a report to the published Data Mart. Write the message in Markdown and check it in Preview.

  • Every Teams channel can receive email, and OWOX sends the report to that address
  • Type / to place the Historical exchange rates data table: date, currency, rate, base and the number of rows you pick
  • Create & Run posts the first report straight away
Microsoft TeamsWeeklyOpen Exchange Rates digestdatecurrencyratebase

S04 · Step 4

Step 4: Put a short analysis under the Open Exchange Rates table in Teams

Add two or three lines beneath the table in the same message. Pick a send condition on the report, and open the Triggers tab to set the day and time of the run.

  • The lines rest on currency and rate from the table above them
  • Figures come from a fresh run of the Data Mart before each message
  • Send always, only when empty or only when not empty: chosen per report
Microsoft TeamsOpen Exchange Rates digestdatecurrencyratebaseAnalysisCompare rate for each currency with the week beforeA change in base changes every figure, so check it firstRates by date show which day a move began

S05 · Step 5

Step 5: Reuse Open Exchange Rates inside OWOX MCP

The same Data Mart works in OWOX MCP, your AI assistant for data. Request any report, chat with your data, then get it in Google Sheets or Excel in one click.

  • Ask in plain words; the answer comes from your data warehouse
  • Define the numbers once and every report reads them
OWOX MCPShow settled_revenue by currency and monthsettled_revenue
Google SheetsOpen
ExcelOpen

Recent updates

Why OWOX

Why OWOX for Open Exchange Rates in Microsoft Teams

Hand-built flows that read Open Exchange Rates and post to Teams carry the source's numbers only. OWOX posts the answers your data warehouse calculated, to the channel of your choice.

  • Settled revenue, explained. Teams shows the rates behind a converted revenue figure, so nobody asks which rate was used.
  • You own the data. Open Exchange Rates lands in your own data warehouse, in tables you control, before anything reaches Teams.
  • Nothing to build in Teams. The channel email address is all it needs: no custom connector, no flow to maintain on the Microsoft side.
  • A message with a condition. Each report has its own send condition, so a Teams channel hears only when there is something to say.
  • Maintained for you. When the source changes, the connector is updated; your Teams channel keeps getting the report.

Book a callGet started free

Trust

The Data Partner You Can Trust

users

175K Source: Internal OWOX data as of 2026-11-11

Executives and data analysts across 20+ industries

G2 rating

4.9★2

“A trusted data analytics partner” — verified review

npm installs

171K3

In Open Source We Trust

Customers