Resolve address questions right from comments
When a location comes up in a page discussion, get its coordinates without starting a separate research task.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or 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
A simple address question can linger in comments because nobody has time to open another tool.
- Give address questions a useful geographic result.
- Reduce manual follow-up on location details.
- Keep the response anchored to the relevant page discussion.
Setup
Build it in a few focused steps.
- 1Connect Notion and Geokeo to Notis once in the portal, enabling Read comments for Notion.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Give Notis one plain-language instruction to find an address in new comments on the page and return Geokeo's coordinates and structured address.
- 4Select Notion New Comment for the intended page or block, then pick a channel for run reports.
- 5Test with one comment containing a real address.
Questions about this workflow
How is this different from the workspace-wide comment trigger?
New Comment is attached to a specified Notion block or page, while Comment Created can cover comments across the accessible workspace.
Will it locate the place or return coordinates?
Forward geocoding can return both coordinates and structured address details for an address or place name.
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.