Prepare useful stops around upcoming visits
Once a week, gather nearby options around the client visits you have already planned in Notion.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Nearby search
Searches for places (e.g., restaurants, parks) within a specified circular area, with options to filter by place types and customize the returned fields and number of results.
Why this helps
Useful stops and practical needs are often researched only after a busy travel day has begun.
- Creates a predictable moment for trip preparation.
- Finds relevant nearby options for multiple upcoming visits.
- Reduces last-minute decisions on travel days.
Setup
Build it in a few focused steps.
- 1Connect Notion and Google Maps to Notis once in the portal.
- 2Create an automation in the portal or tell Notis to check upcoming visit pages weekly and search for useful nearby services.
- 3Pick a recurring schedule and the channel for run reports.
- 4Test with one upcoming visit page and confirm the area and place types are useful.
Questions about this workflow
How does the schedule know which visits are upcoming?
Describe the upcoming visits to review in the prompt; Notis uses the Notion context available to it.
Can the weekly scan choose different place types?
Yes. Specify relevant categories such as parking or cafes in the plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Google Maps. A trigger fires from one place; an action lands in another.
Notion triggers
Google Maps actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Distance Matrix
Calculates travel distance and time for a matrix of origins and destinations. supports different modes of transportation and options like departure/arrival times. use when needing to determine travel metrics between multiple points.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Geocoding, Reverse Geocoding, and Place ID Lookup
Deprecated: tool to convert addresses into geographic coordinates (latitude and longitude) and vice versa (reverse geocoding), or get an address for a place id. use for finding coordinates for an address, finding an address for coordinates, or looking up an address by its place id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get directions
Fetches detailed directions between an origin and a destination, supporting intermediate waypoints and various travel modes.
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.
Get Route
Calculates one or more routes between two specified locations using various travel modes and preferences; addresses must be resolvable by google maps.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Embed Google Map
Tool to generate an embeddable google map url and html iframe code. use when you need to display a map (place, view, directions, street view, search) on a webpage without javascript.
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.
Nearby search
Searches for places (e.g., restaurants, parks) within a specified circular area, with options to filter by place types and customize the returned fields and number of results.
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.
Text Search
Searches for places on google maps using a textual query (e.g., "restaurants in london", "eiffel tower").
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 Google Maps, 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 Google Maps.