Start a route investigation from an escalation
Log the escalation in Notion and start a Globalping traceroute for the documented endpoint, so the network follow-up does not rely on memory.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Measurement
Tool to create and trigger a network measurement. Use when you need connectivity checks from specific geographic or network locations.
Why this helps
Customer escalations can move between people and channels, making a route investigation easy to lose among status updates.
- Turns a documented route concern into an investigation signal.
- Reduces manual handoffs between customer support and network diagnosis.
- Keeps the relevant endpoint close to the escalation record.
Setup
Build it in a few focused steps.
- 1Connect Notion and Globalping to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to run a traceroute when a customer escalation page reports a route concern.
- 3Describe in one plain-language instruction how to identify the endpoint and when a traceroute is appropriate.
- 4Choose Notion New Page as the trigger for the escalation records and choose a run-report channel.
- 5Test with a safe endpoint and a real example escalation record.
Questions about this workflow
Can a traceroute explain a customer's full experience?
It shows a network path from available probes and can support investigation, but it does not represent every customer route.
Will all escalation records create a traceroute?
The automation instruction should clearly identify route concerns that warrant this action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Globalping. A trigger fires from one place; an action lands in another.
Notion triggers
Globalping actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Measurement
Tool to create and trigger a network measurement. Use when you need connectivity checks from specific geographic or network locations.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Measurement Results
Tool to get measurement results by ID. Use when you need to retrieve the status and detailed per-probe results of an existing measurement.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
GlobalPing Health Check
Tool to check API health status. Use when verifying API availability.
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.
List Probes
Tool to list all currently connected probes. Use after authenticating with the API to retrieve online probe metadata.
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 Globalping, 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 Globalping.