Let updated stops flow into route planning
A changed stop in Notion can trigger a fresh vehicle routing request around the latest operational details.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
GraphHopper VRP POST
Tool to initiate VRP optimization. Use when you need to solve vehicle routing problems synchronously.
Why this helps
A changed stop can sit unnoticed in the route plan, creating a gap between the task list and the actual day.
- Respond to changes in the active stop list.
- Reduce manual route reshuffling.
- Keep planning closer to current visit requirements.
Setup
Build it in a few focused steps.
- 1Connect Notion and GraphHopper to Notis once in the portal.
- 2Create an automation in the portal or tell Notis to reconsider vehicle routes when a stop record changes.
- 3Describe the stop set and the constraints to use in one plain-language instruction.
- 4Select Page Properties Updated for the relevant stop data source and pick a channel for run reports.
- 5Test by changing one stop's location or service details and review the proposed plan.
Questions about this workflow
Will every property update launch a new optimization?
The trigger can run on property updates for its chosen scope. Use it where those updates meaningfully affect routing.
Should I accept the proposed route automatically?
Review the result against your operating constraints before acting on it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Graphhopper. A trigger fires from one place; an action lands in another.
Notion triggers
Graphhopper actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Capacity Clustering
Tool to solve capacity clustering problem. Use when assigning a set of customers to clusters to minimize total distance synchronously.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
GraphHopper Geocoding
Tool to perform forward or reverse geocoding. Use when converting between textual addresses and latitude/longitude coordinates.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Isochrone
Tool to compute isochrone polygons for a given point. Use when you need to determine areas reachable within time or distance constraints.
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.
Calculate Matrix
Tool to calculate distance, time, or weight matrices via POST. Use when you have multiple origins/destinations or a symmetric point set and need a single batch request.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Custom Profiles
Tool to retrieve a list of all user-defined routing profiles. Use when you need to list custom profiles.
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.
POST Route
Tool to calculate complex routes via POST /route. Use when you need advanced route planning with custom parameters.
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.
Upload GPX File
Tool to upload a GPX file to a public file hosting endpoint. Returns a public URL which can be used where a 's3key' is required.
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.
GraphHopper VRP POST
Tool to initiate VRP optimization. Use when you need to solve vehicle routing problems synchronously.
Connect any two apps with Notis in the middle.
Notion and Graphhopper, 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 Graphhopper.