See how far people can travel to an event
Update an event page and have Notis request a reachable-area map around its location for practical planning.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Generate isoline (isochrone/isodistance)
Tool to generate isochrone or isodistance isolines. Use when visualizing reachable areas from a point; use `id` to poll ongoing calculations.
Why this helps
Choosing an event location without a quick sense of travel reach can make attendance harder to plan.
- Explore areas reachable from the event location.
- Support venue and attendance planning with geographic context.
- Avoid building a reachability check from scratch.
Setup
Build it in a few focused steps.
- 1Connect Notion and Geoapify to Notis once in the portal.
- 2Create an automation in plain language asking Notis to generate a Geoapify reachability area when event location content is updated.
- 3Select Page Content Updated for the event page or its data source.
- 4Choose a reporting channel and test with a real event address and travel-time goal.
Questions about this workflow
What does a reachability area show?
Geoapify can generate an isochrone or isodistance around a point, representing areas within a chosen travel time or distance.
Can this tell me attendee travel time?
It shows a reachable area from the event location, rather than calculating each attendee's individual trip.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Geoapify. A trigger fires from one place; an action lands in another.
Notion triggers
Geoapify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Address Autocomplete
Tool to fetch address suggestions based on partial input. Use when you need to get predictive suggestions from incomplete address text.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Batch Requests
Tool to create or retrieve batch jobs. Use when processing multiple API calls asynchronously in one operation.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Administrative Boundaries
Tool to retrieve administrative boundaries a location is part of. Use when you have either a place ID or coordinates and need GeoJSON boundaries. Returns a FeatureCollection.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Forward Geocoding
Tool to convert an address into geographic coordinates. Use when you need latitude and longitude from an address.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Geometry Operation
Tool to perform geometric operations on stored polygon geometries. Use when combining or intersecting multiple stored geometries.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
IP Geolocation
Tool to determine geographic location of an IP address. Use when you need to lookup location information by IP.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Generate isoline (isochrone/isodistance)
Tool to generate isochrone or isodistance isolines. Use when visualizing reachable areas from a point; use `id` to poll ongoing calculations.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Map Matching
Tool to snap GPS traces to the road network and correct inaccuracies. Use when raw GPS points need alignment to roads.
Connect any two apps with Notis in the middle.
Notion and Geoapify, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Geoapify.