Check the first available IP in a new risk data source
A new data source can mark the start of a fresh risk workflow. Let Notis check an IP if one is already available to it.
Trigger
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.
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
Structural setup changes can consume attention before anyone checks the underlying risk evidence.
- Tie a new risk data source to an IP check when context allows.
- Bring a lookup into the setup process.
- Get a run report that is easy to review.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ip2proxy to Notis once.
- 2Create an automation conversationally or in the portal.
- 3Ask Notis in one instruction to check any IP available in the new risk data source context and report its classification.
- 4Select Data Source Created, choose a run-report channel, and test with a real source where an IP is accessible.
Questions about this workflow
Does a data source event mean a row was added?
No. It means a new data source was created; a row addition uses a page event instead.
What if no IP is available at creation?
Use a page or property event that occurs when the actual IP record is added.
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.