Skip to content
Notis

Check IP Reputation Automatically When Security Incidents Appear

Stop switching between tools to check if an IP is dangerous. The moment you create an incident page, Notis checks Abuselpdb and logs the reputation status so you have context instantly.

Trigger

Page Created

Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.

Action

Check IP Reputation

Tool to check the reputation of an ip address. use when you need to determine if an ip address has been reported for abusive activity within a specified look-back period. example: checkip(ipaddress='8.8.8.8', maxageindays=90).

Why this helps

You create a new incident in Notion but have to manually switch to Abuselpdb to check the IP reputation, breaking your investigation flow and causing delays.

  • No context switching between Notion and Abuselpdb
  • Reputation data appears in your incident record automatically
  • Investigate faster with immediate threat intelligence

Setup

Build it in a few focused steps.

  • 1Connect your Notion workspace to Notis and grant access to security incident pages.
  • 2Connect your Abuselpdb account to Notis via the portal.
  • 3Create a new automation: open Notis automation portal, click 'New Automation', name it 'Incident IP Check', and enter this prompt: 'When a new page is created in Notion, check the IP reputation in Abuselpdb and add the reputation status as a property on the page.'
  • 4Select 'Page Created' as the trigger and choose your preferred channel to receive run reports.
  • 5Test by creating a sample incident page with an IP address and confirm the reputation check runs.

Questions about this workflow

What if an incident doesn't have an IP address?

Notis will skip the check gracefully. The automation only triggers on pages with IPs.

How long does the reputation check take?

Typically under 30 seconds from page creation to result logged in your incident.

Can I use this on existing incidents?

Only new incidents going forward. For existing ones, you can run a one-time batch check via webhook.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Abuselpdb. A trigger fires from one place; an action lands in another.

Notion triggers

Abuselpdb actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Retrieve IP Blacklist

Tool to retrieve a list of the most reported ip addresses. use when building dynamic blocklists or threat intelligence feeds.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Bulk Report

Tool to submit multiple ip abuse reports in bulk. use when you need to report a large set of ips at once by uploading a csv file with required headers. csv must include columns: ip, categories, reportdate, comment.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Check Block

Tool to check the reputation of all ip addresses in a cidr range. use when you need aggregated abuse data for a network block.

ActionInstant

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.

TriggerInstant

Check IP Reputation

Tool to check the reputation of an ip address. use when you need to determine if an ip address has been reported for abusive activity within a specified look-back period. example: checkip(ipaddress='8.8.8.8', maxageindays=90).

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Clear Address Reports

Tool to remove all reports associated with a specific ip address. use when you need to purge your own abuse records after verifying control of the ip.

ActionInstant

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.

TriggerInstant

Get Abuse Reports

Tool to retrieve a list of abuse reports for a specific ip address. use when you need to fetch historic reports with optional filtering by status, date range, reporter, and pagination.

ActionInstant

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.

TriggerInstant

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.

TriggerInstant

Connect any two apps with Notis in the middle.

Notion and Abuselpdb, 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 Abuselpdb.