ISO Codes
Utilities & PersonalConvert and look up standard ISO country, currency, and language codes entirely offline, with no API key or external call. Agents normalize codes between systems that each picked a different representation.
What This Integration Enables
ISO Codes converts and looks up standard country, currency and language codes inside FlowRunner. There is no API key, no account and no external call, so the reference data your billing, shipping and tax logic depends on has no vendor behind it that can be down, rate-limited or deprecated, and no credential to rotate. This is the unglamorous fix for a problem that shows up everywhere two systems meet: each one picked a different representation of the same fact, and neither will tell you it disagreed. The connector covers the 249 officially assigned ISO 3166-1 countries in alpha-2, alpha-3 and numeric form, the current ISO 4217 currency and fund codes with their numeric codes, symbols and minor-unit digits, and the 486 ISO 639-2 languages with their ISO 639-1 equivalents, with names localizable on demand. The most consequential field in the whole set is the smallest one: minor-unit digits, which is what tells you that 1000 minor units is 1000 yen and 10.00 dollars.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Making two systems agree on a country
A CRM stores countries as alpha-2, the ERP wants numeric, and the shipping platform wants alpha-3. Rather than maintaining three mapping tables that drift, an agent calls Convert Country Code once per record and gets all three forms plus the country name back in a single response, then writes each system the form it expects. Numeric codes come back zero-padded to three characters, so values such as 004 survive the round trip instead of being read as the number four. The normalised record flows into NetSuite and ShipStation with no per-system transformation code.
Turning form prose into valid codes
A supplier onboarding form lets vendors type their country and their invoicing currency freely, because forcing a picker on a supplier portal costs completions. The agent calls Find Country by Name and Find Currency by Name on the submitted text. Matching is case-insensitive and accent-insensitive, exact matches rank above prefix and substring matches, and each call returns the best match plus up to 25 ranked candidates. High-confidence exact matches are written straight to the vendor record in QuickBooks Online. Anything that resolved on a substring is queued for a human rather than accepted.
Documents in the recipient's language
A billing flow issues invoices across a dozen markets. The agent calls Get Country Name and Get Currency with an output language derived from the customer's locale, so a German customer's invoice reads Deutschland and Vereinigte Staaten rather than Germany and United States, and the currency name is localized to match. Get Language handles the locale tag itself, tolerating full tags such as pt-BR by using the base subtag and returning both ISO 639-2 forms, which differ for around twenty languages. The rendered document goes out through SendGrid.
Human-in-Loop Highlight
The gate is money, and specifically the minor-unit digit count. Get Currency returns how many decimal digits a currency has: zero for JPY, two for USD, three for BHD, four for the CLF fund code. When a batch of amounts arrives expressed in minor units from a system whose convention is not documented, applying the ISO digit count is not a formatting decision, it is a change to the amount. Ten thousand minor units of BHD is 10.000 dinars if the sender used the ISO convention and 100.00 if it used a two-digit convention, and both numbers look entirely reasonable on an invoice. So the agent does not resolve this on its own. It stops, and asks the controller through Microsoft Teams: "412 invoices in this batch are labelled BHD. ISO 4217 gives BHD three minor-unit digits. Applying that turns the largest line, 4500000, into 4,500.000 BHD. Confirm the source system's convention before I post, or route the batch back." The agent has assembled every fact needed to decide in seconds. What it will not do is pick a scaling factor for somebody else's ledger, which is the whole point of human-in-the-loop sitting inside the flow rather than after it.
Agent Capabilities
10 actionsCountries
4- Convert Country Code Converts an ISO 3166-1 country code between its alpha-2, alpha-3 and numeric forms, auto-detecting the input so US, USA and 840 are interchangeable, with or without leading zeros. Returns all three forms plus the country name in one call, so several downstream fields can be filled from a single lookup. Numeric codes are returned zero-padded to three characters.
- Get Country Name Returns the human-readable name of a country from any ISO 3166-1 code form, with an output language for localization so DE returns Germany in English and Deutschland in German. All three code forms are returned alongside the name, and unsupported output languages fall back to English.
- Find Country by Name Finds a country from free-text using case-insensitive, accent-insensitive matching against both English and the chosen output language as well as the alpha-2 and alpha-3 codes. Exact matches rank above prefix and substring matches, and the response carries the best match plus up to 25 ranked candidates so a flow can branch on confidence rather than accepting whatever came first.
- List Countries Returns all 249 officially assigned ISO 3166-1 countries and territories with their three code forms and a localized name, sorted by name. Used to populate pickers, seed reference tables or validate a batch of codes in one call. User-assigned codes such as XK and EU VAT prefixes such as EL and XI are not part of ISO 3166-1 and are not included.
Currencies
3- Get Currency Looks up an ISO 4217 currency from its alpha-3 or numeric code and returns both forms, the localized and official ISO names, the symbol and the number of minor-unit digits. The minor-unit figure is what makes money maths correct across currencies. Fund codes such as CLF and non-currency codes such as XAU are included and flagged as such.
- Find Currency by Name Finds a currency from free-text using the same ranked, accent-insensitive matching, against the localized name, the official ISO 4217 name, the alpha-3 code and the numeric code, so yen, Japanese Yen and 392 all resolve. Returns the best match plus up to 25 ranked candidates.
- List Currencies Returns the current ISO 4217 currency and fund codes with their alpha-3 and numeric codes, localized name, symbol and minor-unit digits, sorted by name. Special codes such as fund codes, precious metals, settlement units and the no-currency code XXX are included by default and can be excluded to leave only everyday spendable currencies.
Languages
3- Get Language Looks up a language from any ISO 639 code and converts between the two-letter and three-letter forms. Accepts a 639-1 code, a 639-2 bibliographic code or a 639-2 terminologic code, and tolerates full locale tags such as pt-BR by using the base subtag. Returns both three-letter forms, which differ for around twenty languages, plus the localized and official names. Languages with no two-letter code return null rather than a fabricated one.
- Find Language by Name Finds a language from free-text using ranked, accent-insensitive matching. Several ISO 639 entries carry alternate names and every alternate is searched, along with the ISO 639-1 and both ISO 639-2 codes. Returns the best match plus up to 25 ranked candidates.
- List Languages Returns the ISO 639-2 language list with each entry's two-letter code where one exists, both three-letter forms and a localized name, sorted by name. The full list holds 486 entries including collective and special codes, and can be restricted to the roughly 183 entries that also carry an ISO 639-1 code.
Frequently Asked Questions
What can FlowRunner do with ISO Codes?
FlowRunner agents can run Convert Country Code, Get Country Name, and Find Country by Name in ISO Codes, plus 7 more actions.
Does connecting ISO Codes to FlowRunner require OAuth?
No. ISO Codes needs no credentials at all, so there is no key to obtain, store, or rotate.
Can ISO Codes trigger a FlowRunner workflow automatically?
ISO Codes doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with ISO Codes
$100 in credits. No card required. Connect in minutes.