Integration
Connect Mailparser to Meteorologisk Institutt
When something happens in Mailparser, your agent does the next thing in Meteorologisk Institutt. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Mailparser and Meteorologisk Institutt to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Mailparser and Meteorologisk Institutt
Triggers and actions 2 triggers · 6 actions
Trigger
New Email Parsed (One Request Per Email)Triggered instantly when Mailparser finishes parsing an inbound email, with all of that email's parsed data delivered in a single request. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per Email". Parsed fields bind as {{ trigger.body.* }}. Use the One Request Per Row trigger instead when you are parsing tabular data and want each row handled as its own run.
- New Email Parsed (One Request Per Row)
Triggered instantly for EACH parsed table row when Mailparser finishes parsing an inbound email — one run per row, for tabular data such as invoice line items or price lists. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per row". That row's fields bind as {{ trigger.body.* }}. Use the One Request Per Email trigger instead when you want the whole email's parsed data in a single run.
Action
Find weather alertsLook up active MetAlerts weather warnings (wind, flood, avalanche, etc.) for Norway, optionally filtered by lat/lon/county/lead time. GET https://api.met.no/weatherapi/metalerts/2.0/current.json?lat={lat}&lon={lon}. Requires a unique User-Agent header. Returns a GeoJSON FeatureCollection of active alerts.
- Get air quality forecast
Fetch a forecast of air-quality pollutant concentrations (NO2, PM10, PM2.5, O3) for a location in Norway. GET https://api.met.no/weatherapi/airqualityforecast/0.1/complete?lat={lat}&lon={lon}. Requires a unique User-Agent header.
- Get immediate forecast
Fetch a short-term (Nordic-area) precipitation nowcast updated every 5 minutes for a lat/lon coordinate. GET https://api.met.no/weatherapi/nowcast/2.0/complete?lat={lat}&lon={lon}. Requires a unique User-Agent header. Returns minute-by-minute precipitation rate timeseries.
- Get ocean forecast
Fetch a forecast of sea conditions (wave height, sea temperature, currents) for a point at sea in Northwestern Europe. GET https://api.met.no/weatherapi/oceanforecast/2.0/complete?lat={lat}&lon={lon}. Requires a unique User-Agent header.
- Get sun and moon times
Calculate sunrise/sunset/moonrise/moonset and related sun/moon events for a lat/lon/date. GET https://api.met.no/weatherapi/sunrise/3.0/sun?lat={lat}&lon={lon}&date={date}&offset={offset} (and /moon for moon events). Requires a unique User-Agent header.
- Get weather forecast
Fetch a multi-day weather forecast for a lat/lon coordinate. GET https://api.met.no/weatherapi/locationforecast/2.0/complete?lat={lat}&lon={lon}&altitude={altitude}. Requires a unique User-Agent header (vendor blocks generic clients with 403). Returns hourly/6-hourly timeseries: temperature, wind, precipitation, humidity, cloud cover, symbol_code.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.