FlowRunner
PricingContact
Theme
Start Free

Unit Converter

Utilities & Personal

Convert values between 142 units of measure across 13 dimensions entirely offline, with no API key or external call. Agents normalize units between systems that each chose a different one.

16 actions No credentials available
Platform Documentation ↗ Capability data verified 2026-08-01
A supplier sends a shipment manifest with weights and dimensions in mixed units
Agent reads each line's value and the unit string as written
Agent confirms each unit string is unambiguous with Get Unit Info
Agent converts every line to the carrier's required units with Convert Units
Agent posts the normalised manifest with both original and converted values to the logistics channel
Where a unit string is ambiguous, the logistics lead names the exact unit before the booking is made

What This Integration Enables

Unit Converter converts values between 142 units across 13 dimensions inside FlowRunner, with no API key, no account and no external call. That means the arithmetic your shipping bookings, engineering records and lab data depend on has nothing to provision and nothing that can be unavailable at the moment a manifest needs converting. What makes it worth a page rather than a footnote is what it refuses to do. Every factor is the exact international definition, so a pound is 0.45359237 kg rather than a rounded approximation. US and imperial gallons, pints and fluid ounces are separate labelled units, because a US gallon is 3.785411784 L and an imperial gallon is 4.54609 L. Temperature is converted with proper affine scaling rather than a multiplier. Fuel economy uses the correct reciprocal relation. Conversions between different quantities, such as metres to kilograms, are rejected with a clear error rather than returning a plausible number, and genuinely ambiguous input such as gal or ton raises an ambiguity error listing the exact keys to use. This is the calculator an agent is not allowed to improvise, which matters a great deal when a language model is the thing doing the improvising.

Without FlowRunner

Units left as text Values arrive as psi, BTU, acres or ton and get copied without conversion
Conversions done by hand Someone multiplies by a factor they half remember from a search result
Ambiguity resolved by guessing A field reading ton is assumed to mean whichever ton the reader expects

With FlowRunner

Exact international definitions Every factor is the defined value, so an inch is exactly 25.4 mm
Conversion as a workflow step The maths happens in the flow, with the source value kept beside the result
Ambiguity refused, not guessed Inputs such as gal or ton raise an error naming the exact keys to use

Use Case Scenarios

A manifest the carrier will accept

A manufacturer receives supplier manifests in whatever units the supplier's own system uses, then books freight with a carrier that requires kilograms and centimetres. An agent walks the manifest, calls Convert Units on each value without needing to know in advance which dimension a line belongs to, since the dimension is detected from the units themselves, and writes both the original value and the converted value onto the booking record in ShipStation. Keeping both means a dispute six weeks later is settled by reading the record rather than by reconstructing what somebody assumed.

Sensor readings that mean the same thing

A facilities team pulls readings from equipment across several sites, some reporting pressure in psi and some in bar, some reporting temperature in Fahrenheit and some in Celsius. Before anything is charted or alerted on, the agent normalises every reading with Convert Pressure and Convert Temperature. Psi is derived from the exact pound-force definition rather than a rounded constant, and temperature is treated as an absolute reading with the correct offset applied. The normalised series lands in BigQuery and a threshold breach raises a ticket in PagerDuty against a number that means one thing across the estate.

Giving an AI agent a calculator instead of a guess

An agent extracts product specifications from supplier PDFs, which is a job language models do well, and then has to convert those specifications into the catalogue's standard units, which is a job language models do plausibly rather than correctly. The flow routes every conversion through this connector instead. List Units gives the agent the exact set of unit keys it is allowed to use, Get Unit Info confirms a candidate string before a conversion is attempted, and Convert Units performs the arithmetic. The extraction stays with the model. The maths does not.

Human-in-Loop Highlight

The gate is a converted number that becomes a declaration. Convert Units refuses ambiguous input rather than resolving it: a value labelled ton raises an ambiguity error listing the exact keys, because a short ton is 907.18474 kg, a long ton is 1016.0469 kg and a metric tonne is 1000 kg, and all three are ton in ordinary writing. On a spreadsheet that is a rounding argument. On a customs declaration or a carrier booking it is a filed figure with a signature behind it, and the correction costs a re-file rather than an edit. So when an ambiguity error is raised on a value bound for a booking or a declaration, the agent does not fall back to the most common reading. It holds the line and asks the logistics lead in Microsoft Teams: "Line 14 of manifest MFT-3391 reads 18 ton from supplier Kestrel. Short ton gives 16,329 kg, long ton gives 18,289 kg, metric tonne gives 18,000 kg. Which unit does Kestrel use? I will store the answer against the supplier so this does not come back." The human decides once and the mapping is fixed, which is the difference between an escalation and a recurring interruption. Every one of these is logged as an automation exception rather than resolved in silence.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

16 actions

Physical Dimensions

13
  • Convert Length Converts a length or distance across metric, imperial, nautical and astronomical units, from nanometres to parsecs. All factors are the exact international definitions, so an inch is exactly 25.4 mm and a mile is exactly 1.609344 km. An optional rounding step produces display-ready output.
  • Convert Mass Converts a mass or weight across metric, avoirdupois and troy units, from micrograms to long tons. The pound is the exact 0.45359237 kg definition, and short tons, long tons and metric tonnes are kept strictly separate so a shipping or invoicing weight is never silently misread.
  • Convert Temperature Converts between Celsius, Fahrenheit, Kelvin, Rankine and Réaumur, applying the correct offset as well as the scale because temperature scales are affine rather than proportional. Values are treated as absolute readings, not as differences, and the action documents that a difference of 10 degrees Celsius equals a difference of 18 degrees Fahrenheit and should not be converted here.
  • Convert Area Converts an area across metric and imperial units including hectares and acres, with exact derived factors so an acre is exactly 4046.8564224 square metres. Used for property, agriculture, construction and mapping data that arrives in mixed units.
  • Convert Volume Converts a volume or liquid capacity across metric, US customary and imperial units. US and imperial gallons, quarts, pints and fluid ounces are separate, clearly labelled units, because conflating them is a common and expensive mistake. Also covers cubic units, cooking measures and the 42 gallon oil barrel.
  • Convert Time Converts a duration between nanoseconds and years. Calendar units are approximations by necessity and are labelled with the basis used: a month is 30 days, a year is 365 days, a Julian year is 365.25 days. Exact calendar arithmetic across real months and leap years belongs in a date function instead.
  • Convert Speed Converts between metres per second, kilometres per hour, miles per hour, knots, feet per second and Mach. A knot is exactly one nautical mile per hour and a mile per hour is exactly 0.44704 metres per second. Mach is referenced to sea level standard conditions and should be treated as an approximation at altitude.
  • Convert Pressure Converts between pascals, bar, atmospheres, torr, millimetres and inches of mercury, and psi, with psi derived from the exact pound-force definition rather than a rounded constant. Used for weather data, tyre and hydraulic specifications, and industrial sensor readings.
  • Convert Energy Converts between joules, calories, watt hours, BTU, foot-pounds and electronvolts. The calorie is the thermochemical calorie of exactly 4.184 J, and the kilocalorie is the dietary Calorie seen on food labels. Used for utility billing, nutrition data, battery capacity and engineering work.
  • Convert Power Converts between watts, kilowatts, megawatts, horsepower and BTU per hour. Mechanical horsepower and metric horsepower are separate units, because vehicle specifications quoted in hp and PS are not interchangeable. Used for appliance ratings, HVAC sizing and vehicle data.
  • Convert Data Size Converts between bits, bytes and their decimal and binary multiples, with SI powers of 1000 and IEC powers of 1024 offered separately so storage marketing figures and operating system figures can be reconciled. Bit-based network units are included for bandwidth calculations.
  • Convert Angle Converts between degrees, radians, gradians, turns, arcminutes, arcseconds and milliradians, using the full double-precision value of pi. Used for geospatial coordinates, CAD data and any library that expects radians.
  • Convert Fuel Economy Converts between consumption units and efficiency units, applying the reciprocal relation rather than a scale factor, because doubling the miles per gallon halves the litres per 100 km. US and imperial gallons are separate units here too. Values must be greater than zero.

Reference and Generic Conversion

3
  • Convert Units Converts a value between any two units without the caller knowing which dimension they belong to, detecting the dimension from the units themselves. Units are accepted as keys, symbols or names. Conversions between different quantities are rejected with a clear error rather than returning a meaningless number, and ambiguous inputs raise an ambiguity error listing the exact keys to use instead.
  • List Units Returns every supported unit, optionally filtered to one dimension, with its key, display label, symbol, relation to the dimension base unit and accepted aliases. Used to build pickers, validate incoming unit strings before conversion, or show an AI agent exactly which unit keys it may use.
  • Get Unit Info Looks up a single unit and returns its dimension, canonical key, symbol, aliases and exact relation to its base unit, together with the units it can convert to. Used to confirm that an incoming string is unambiguous before a conversion runs, or to explain a conversion factor to an end user.

Frequently Asked Questions

What can FlowRunner do with Unit Converter?

FlowRunner agents can run Convert Length, Convert Mass, and Convert Temperature in Unit Converter, plus 13 more actions.

Does connecting Unit Converter to FlowRunner require OAuth?

No. Unit Converter needs no credentials at all, so there is no key to obtain, store, or rotate.

Can Unit Converter trigger a FlowRunner workflow automatically?

Unit Converter doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Unit Converter

$100 in credits. No card required. Connect in minutes.