Keep support escalations moving when an IP appears
Support conversations can surface an address that needs a closer look. Let Notis make the check and return a clear signal for triage.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Check Proxy Status of an IP
Tool to check if an IP address is a proxy. Use after obtaining an IP to detect proxy, VPN, or Tor status.
Why this helps
Escalations already demand attention, and an IP lookup can become another open loop for the person handling the case.
- Check addresses raised in a selected escalation thread.
- Keep lookup follow-up with the relevant support context.
- Reduce the need to pause triage and switch tools.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ip2proxy to Notis once and enable comment reading for Notion.
- 2Create the automation conversationally or in the portal.
- 3In a single prompt, ask Notis to check IPs in new comments on the escalation page and report proxy, VPN, or Tor status.
- 4Choose New Comment, set the escalation page, select a report channel, and test with a real comment.
Questions about this workflow
Can this be used across all support pages?
Use the workspace-capable Comment Created event with an optional page filter, or configure New Comment for a specific page.
Will Notis resolve the support case?
It reports the IP classification so the support owner can decide what to do next.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ip2proxy. A trigger fires from one place; an action lands in another.
Notion triggers
Ip2proxy actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Proxy Status of an IP
Tool to check if an IP address is a proxy. Use after obtaining an IP to detect proxy, VPN, or Tor status.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 Ip2proxy, 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 Ip2proxy.