Currency Converter
FinanceConvert money between currencies and retrieve published exchange rates, with no account or API key required. Agents normalize multi-currency amounts before they reach an accounting or reporting system.
What This Integration Enables
No account, no API key, no connection settings. Both rate sources behind this connector are keyless, so a flow that needs to normalize a multi-currency amount can be built and shipped without a procurement conversation about a data subscription. For a finance team that mostly needs published reference rates rather than a trading feed, that removes the usual reason the conversion ends up living in a spreadsheet formula instead of in the workflow.
The more important thing is what the connector refuses to hide. A converted amount is rarely just a display value. It becomes an invoice total, an expense reimbursement, a journal line, a figure in a board pack, and each of those is dated. So every result names the exact date of the rate it used, returns both the unrounded and the rounded value, and rounds to the minor unit count that the target currency actually has under ISO 4217, which is zero places for JPY and KRW, three for BHD and KWD, and four for CLF. Two sources sit behind it and each result names the one it came from: European Central Bank reference rates, fixed once per business day and the only source here with history back to 1999, and a broad-coverage source of roughly 160 currencies refreshed daily for the Gulf, African, Asian and Latin American currencies the ECB does not publish. Where a provider does not quote a base directly, the cross rate is computed and flagged rather than presented as a quote.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Supplier invoices restated at the right rate
An accounts payable agent processes invoices arriving in half a dozen currencies. For each one it reads the invoice date off the document rather than using today, calls Get Historical Rates for that date, and converts the amount into the reporting currency before creating the bill in QuickBooks Online. The rate date, the source and the unrounded value are written into the memo field alongside the posted amount. When the auditor asks next year why a particular euro invoice landed at that number, the answer is on the transaction rather than in someone's recollection of how the automation was configured.
Local pricing with the right number of decimals
A storefront quotes in a customer's local currency. An agent calls Get Supported Currencies once to load each currency's ISO 4217 minor unit count and caches it, then calls Convert Currency per quote and uses the rounded value the API returns rather than rounding itself. The result is that a Japanese price shows as whole yen and a Bahraini price shows three decimal places, without anyone maintaining a per-currency exception table in the pricing code. Both sources throttle heavy polling, so the agent caches rates for the day rather than converting on every page view.
Watching a pair and telling someone in time
A treasury flow tracks a currency pair the business is exposed to. A scheduled agent calls Get Rate Time Series across the trailing period, computes the average and the movement against a threshold the finance lead set, and posts a short summary to Slack when the pair crosses it. Weekends and TARGET holidays are simply absent from the series because no rate is fixed on those days, so the agent computes on the business days present rather than interpolating a number that was never published. The alert says what moved and by how much. The decision about whether to act on it belongs to the finance lead, and the agent does not model one.
Human-in-Loop Highlight
Get Historical Rates has a behavior that is correct and quietly dangerous in equal measure. The ECB fixes rates only on TARGET business days, so a request for a Saturday, a Sunday or a holiday resolves to the most recent preceding business day, and the only way to know it happened is to compare the date you asked for against the date that came back. Nothing errors. An invoice dated the 31st of a month that fell on a Sunday will convert at Friday's rate, and that may well be the right policy, but it has to be a policy somebody chose rather than a substitution nobody saw. The same applies when a pair is not quoted directly and the result is a computed cross rate. So the agent converts, detects the mismatch, and stops short of the ledger. It messages the controller in Slack: "Invoice INV-4471, 18,400 EUR, dated Sunday 31 May. No ECB fixing exists for that date; the nearest is Friday 29 May, which gives 20,110.72 USD. Today's rate would give 20,043.16 USD. Which rate governs this posting?" One question, one number, before an amount becomes a total that somebody else will reconcile. That is what Orchestration as a Service is for at the boundary of a finance system, and why human-in-the-loop sits in front of the post rather than in a month-end review.
Agent Capabilities
5 actionsConversion
1- Convert Currency Converts an amount from one currency to another at a published exchange rate, and rounds the result to the number of decimal places the target currency actually has under ISO 4217. Both the unrounded and the rounded value are returned, along with the exact date of the rate used, so a stale quote is never presented as current. Supply a date to convert at a past European Central Bank rate instead of the latest one.
Exchange Rates
3- Get Latest Rates Retrieves the most recently published rates for a base currency, optionally narrowed to a list of targets. ECB rates are fixed once per business day around 16:00 CET, while the broad-coverage source refreshes its roughly 160 currency table every 24 hours. The returned date and update timestamp identify exactly which fixing the rates belong to, which is the field an agent should log rather than the rate alone.
- Get Historical Rates Retrieves the European Central Bank reference rates published on a specific date, for invoice restatement, accounting revaluation or auditing a past transaction. The ECB fixes rates only on business days, so a weekend or holiday request resolves to the most recent preceding business day. Compare the returned date with the requested date to detect that. Data goes back to 1999 across the currencies the ECB publishes.
- Get Rate Time Series Retrieves European Central Bank reference rates for every business day in a date range, keyed by date, for charting a pair, computing a period average or finding the best rate in a window. Weekends and TARGET holidays are absent because no rate is fixed on those days. Narrow the target currencies and the range for long periods, since a multi-year request across all currencies returns a large payload.
Reference
1- Get Supported Currencies Lists the currencies available for conversion, each with its ISO 4217 minor unit count so downstream steps know how many decimal places the money should carry. It also indicates which of the two rate sources quotes each currency: the ECB set is small, authoritative and the only one supporting historical lookups, while the broad set adds the Gulf, African, Asian and Latin American currencies the ECB does not publish.
Frequently Asked Questions
What can FlowRunner do with Currency Converter?
FlowRunner agents can run Convert Currency, Get Latest Rates, and Get Historical Rates in Currency Converter, plus 2 more actions.
Does connecting Currency Converter to FlowRunner require OAuth?
No. Currency Converter needs no credentials at all, so there is no key to obtain, store, or rotate.
Can Currency Converter trigger a FlowRunner workflow automatically?
Currency Converter doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Currency Converter
$100 in credits. No card required. Connect in minutes.