Turn client site updates into usable locations
Keep project location research moving as site information changes in your notes.
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
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
Client work brings fresh details at unexpected times, and address lookups can become another follow-up to remember.
- Resolve client site addresses while project details are current.
- Keep location context with its working page.
- Avoid a separate queue of manual lookup tasks.
Setup
Build it in a few focused steps.
- 1Connect Notion and Geokeo to Notis once via the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Give Notis one plain-language instruction to geocode any client site address added to the page and report the coordinates and structured result.
- 4Select Notion Page Content Updated for the site page or data source, then choose a channel for run reports.
- 5Test by adding one actual client site address to the page.
Questions about this workflow
Can this watch a single project page?
Page Content Updated can be scoped to one page or to a data source.
What if the address is already on the page?
The instruction can ask Notis to act only when the updated content includes a newly added or changed address.
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.