Screen orders created under your intake hub
Add an order as a subpage under the intake hub and let Notis start the corresponding fraud check.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
FraudLabs Pro Screen Order
Tool to screen orders for fraud. Use when you need to assess transaction risk before fulfillment.
Why this helps
A useful intake structure still leaves a manual gap if each new subpage needs a separate screening reminder.
- Starts a screen when an order is added to the intended intake area.
- Keeps the trigger tied to a clear Notion workflow location.
- Reduces missed checks in page-based intake.
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 screen order subpages created under your intake hub.
- 3Describe in one plain-language instruction how Notis should identify order subpages and assess them.
- 4Choose the Notion Page Added to Page trigger for the intake hub and select a run-report channel.
- 5Test by adding one real order subpage with screening details.
Questions about this workflow
Does it cover nested subpages at every depth?
The trigger is for a new subpage immediately under the specified parent page.
Can the hub contain other page types?
Yes, but the instruction should tell Notis to screen only pages that clearly contain eligible order data.
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.
Create FraudLabs Pro Account
Tool to create a new user account under a reseller. Use after gathering personal and company details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
FraudLabs Pro Screen Order
Tool to screen orders for fraud. Use when you need to assess transaction risk before fulfillment.
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.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get SMS Verification Result
Tool to retrieve SMS verification result. Use after sending an OTP via SMS to confirm validity.
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.
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.
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.
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.
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.
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.
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.