Skip to content
Notis

Bring the latest risk result into an order review

When your team updates an order review record, ask Notis to fetch the corresponding FraudLabs Pro result for the next decision.

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

Get FraudLabs Pro Order Result

Tool to retrieve the fraud analysis result of a previously screened order. Use after initial screening when you need to check an order's risk.

Why this helps

A reviewer can lose time reopening another tool to find the analysis tied to an order they are already handling.

  • Puts a result lookup at the point where review work changes.
  • Helps reviewers resume without searching for a previously screened order.
  • Reduces context switching during order triage.

Setup

Build it in a few focused steps.

  • 1Connect Notion and FraudLabs Pro to Notis once in the portal.
  • 2Create an automation in the portal or ask Notis to retrieve the FraudLabs Pro result when an order review record changes.
  • 3Write one plain-language instruction explaining which updated order records warrant a result lookup.
  • 4Choose the Notion Page Properties Updated trigger for the order database and choose a reporting channel.
  • 5Test with a real order that has already been screened and confirm the returned result is useful.

Questions about this workflow

Does this screen the order again?

No. It retrieves the result for a previously screened order.

What should be present in Notion?

A recognizable reference to the order that was previously screened, so Notis can request its result.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion triggers

Fraudlabs pro actions

Recurring trigger

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

TriggerScheduled

Create FraudLabs Pro Account

Tool to create a new user account under a reseller. Use after gathering personal and company details.

ActionInstant

Webhook trigger

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

TriggerInstant

FLP Feedback Order

Tool to submit feedback on a screened order. Use after determining whether a flagged order was approved or rejected to improve future fraud detection.

ActionInstant

All Page Events

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

TriggerPolling

FraudLabs Pro Screen Order

Tool to screen orders for fraud. Use when you need to assess transaction risk before fulfillment.

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

Get FraudLabs Pro Order Result

Tool to retrieve the fraud analysis result of a previously screened order. Use after initial screening when you need to check an order's risk.

ActionInstant

New Comment

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

TriggerPolling

Get SMS Verification Result

Tool to retrieve SMS verification result. Use after sending an OTP via SMS to confirm validity.

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

Send SMS OTP Verification

Tool to send SMS OTP for phone verification. Use when you need to deliver a one-time password via SMS before verifying user identity.

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

Subscribe Reseller Plan

Tool to subscribe a reseller account to a specific plan. Use after obtaining a reseller API key and selecting a plan. Example: Subscribe user "john_doe" to the MICRO plan.

ActionInstant

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

Test Order Status Changed Webhook Delivery

Tool to send a test webhook payload to the provided callback URL for FraudLabs Pro order status change notifications. This helps validate your endpoint behavior. Important: FraudLabs Pro webhook registration must be configured manually via dashboard.

ActionInstant

Connect any two apps with Notis in the middle.

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