Connect Mailparser to Nominatim

Both apps 5Mailparser 2Nominatim 3

• 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.

• Trigger
  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 address by OSM ID

  Look up address details for one or more OSM objects by their OSM type+ID. Endpoint: GET /lookup (https://nominatim.org/release-docs/latest/api/Lookup/).

• Action
  Geocode address

  Search OSM objects by free-text address or place query and return matching locations with coordinates. Endpoint: GET /search (https://nominatim.org/release-docs/latest/api/Search/).

• Action
  Reverse geocode

  Look up the address/place at a given latitude/longitude coordinate. Endpoint: GET /reverse (https://nominatim.org/release-docs/latest/api/Reverse/).

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.