Integration
Connect Mailparser to openSenseMap
When something happens in Mailparser, your agent does the next thing in openSenseMap. 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 openSenseMap 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 openSenseMap
Triggers and actions 2 triggers · 8 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 measurements by phenomenonFetch the latest measurements for all sensors measuring a given phenomenon/grouptag, as JSON or CSV. GET /statistics/idw or /boxes/data (phenomenon-scoped query)
- Find senseBoxes near location
Search senseBoxes near a given coordinate/bounding box and phenomenon. GET /boxes with near/bbox query params
- Get 10000 latest measurements for sensor
Fetch up to the 10000 latest raw measurements for one sensor, with optional from-date/to-date filters. GET /boxes/:senseBoxId/data/:sensorId
- Get database statistics
Fetch overview statistics about the openSenseMap database (box count, sensor count, measurement count). GET /stats
- Get latest measurements of senseBox
Fetch the latest measurements of all sensors for a given senseBox. GET /boxes/:senseBoxId/sensors
- Get latest measurements of sensor
Fetch the latest measurement value for one specific sensor of a senseBox. GET /boxes/:senseBoxId/sensors/:sensorId
- Get senseBox
Fetch details for one senseBox station by its ID. GET /boxes/:senseBoxId
- List senseBoxes
List all senseBox stations, optionally filtered by bounding box/phenomenon/exposure. GET /boxes
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews