Resolve each new venue planning page
Let a venue subpage carry its own map-ready location, so planning can stay in one place.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
Forward Geocoding
Tool to perform forward geocoding lookup by address or place name. Use when you need to convert a query string into geographic coordinates and structured address information.
Why this helps
Venue details spread across subpages make it harder to remember which locations still need a lookup.
- Resolve venue addresses as research is added.
- Keep planning context organized under its parent page.
- Make location details easier to reuse.
Setup
Build it in a few focused steps.
- 1Connect Notion and Geokeo to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3In a single plain-language instruction, ask Notis to send each new venue subpage's address to Geokeo and return the location result.
- 4Select Notion Page Added to Page for the planning parent page and choose where run reports should go.
- 5Test by adding a venue subpage with a real address.
Questions about this workflow
Does this follow subpages anywhere in the workspace?
The Page Added to Page trigger is scoped to a specified parent page and its immediate child pages.
What if a page has several venue addresses?
The instruction can ask Notis to resolve each clearly labeled address found on the new page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Geokeo. A trigger fires from one place; an action lands in another.
Notion triggers
Geokeo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Forward Geocoding
Tool to perform forward geocoding lookup by address or place name. Use when you need to convert a query string into geographic coordinates and structured address information.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Reverse Geocoding Lookup
Tool to perform reverse geocoding. Use when you have latitude and longitude and need an address.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Geokeo, 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 Geokeo.