Follow up on locations discussed on a page
Keep one important planning page focused: when a new comment arrives there, let Mapbox help resolve the location being discussed.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Forward Geocoding
Tool to convert free-form or structured address into geographic coordinates and place features. use when you need forward geocoding from text or address components.
Why this helps
Location suggestions spread across a page discussion can take extra effort to find and verify later.
- Focus location checks on one chosen page.
- Make address follow-up easier to notice.
- Avoid a separate map search for every new suggestion.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mapbox to Notis once; enable the Notion Read comments capability.
- 2Create an automation in the portal or ask Notis to look up locations mentioned in comments on your chosen page.
- 3Select New Comment for that page, choose a channel for run reports, and test with one actual comment containing a location.
Questions about this workflow
How is this different from Comment Created?
New Comment is designed for comments on a specified Notion block or page.
Does the workflow create a route?
No. It uses Mapbox Forward Geocoding to resolve a location mentioned in the discussion.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mapbox. A trigger fires from one place; an action lands in another.
Notion triggers
Mapbox actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Batch Geocoding
Tool to perform batch forward or reverse geocoding for multiple locations. use when you need consistent geocoding of up to 50 queries in one call.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Forward Geocoding
Tool to convert free-form or structured address into geographic coordinates and place features. use when you need forward geocoding from text or address components.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Permanent Forward Geocoding
Tool to perform permanent forward geocoding. use when you need enterprise-grade permanent geocoding after confirming account privileges.
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.
Permanent Reverse Geocoding
Tool to perform permanent reverse geocoding. use after obtaining coordinates to get cacheable place data. example: lon=-73.989, lat=40.733
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Reverse Geocoding
Tool to reverse geocode coordinates into place names. use after obtaining coordinates.
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.
Get Access Token
Tool to extract and validate mapbox access token from connection metadata. use when you need a valid token for downstream actions.
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.
Request Style Embed HTML
Tool to retrieve embeddable html for a mapbox style. use when you want to embed a style in an iframe after verifying access.
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.
Retrieve Directions
Tool to retrieve directions between waypoints. use when you need navigation routes with optional turn-by-turn instructions after confirming origin and destination.
Connect any two apps with Notis in the middle.
Notion and Mapbox, 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 Mapbox.