OpenStreetMap Trigger
AI-generatedSummary
Polls OpenStreetMap for notes or changesets on the configured schedule, then emits newly seen records as n8n items. Choose an area-based event and provide a bounding box, or choose changesets by user and provide that user’s OSM display name.
Inputs
- Poll Times — Schedule for polling; defaults to every minute. Supports standard intervals, an Every X minutes or hours interval, and a custom cron expression.
- Event — Select new notes in an area, updated notes in an area, new changesets by user, or new changesets in an area. Defaults to new notes in an area.
- Polling Interval Minutes — Declared polling interval in minutes, default 15 and minimum 5. The poll implementation does not read this parameter; scheduling is configured with Poll Times.
- Bounding Box — For area events, set left, bottom, right, and top coordinates in longitude/latitude order. The box must have valid WGS84 coordinates, left < right, bottom < top, and an area no greater than 0.25 square degrees.
- OSM User Display Name — Required for the new changesets by user event; the value is sent as the OpenStreetMap display_name query parameter.
Output shape
A list of n8n items, one per newly detected note or changeset, each containing the returned record in its json field; no items are emitted when there are no fresh records.
Requests OpenStreetMap’s production API. The trigger stores its last run time and up to 500 recently seen IDs in node workflow static data, filtering out previously seen records and records whose update or creation timestamp is not later than the last run.