Bring Faceup context into an existing review process
Let a review process you already use request a focused statistics snapshot at the moment it is needed.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
FaceUp GraphQL Statistics Query
Tool to execute a graphql query to retrieve faceup statistics. use when you need to fetch or filter metrics (e.g., by date range or school ids).
Why this helps
A separate reporting lookup can break the flow of an established review process and leave the reviewer waiting for context.
- Request a statistics summary when an existing process reaches a review point.
- Avoid adding another manual lookup to the reviewer's checklist.
- Keep run reporting in the channel the team already uses.
Setup
Build it in a few focused steps.
- 1Connect Notion and Faceup to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to check Faceup statistics when the review process sends a webhook.
- 3Describe the review context and the reporting measures to retrieve and summarize.
- 4Choose an incoming webhook trigger and a channel for run reports.
- 5Test by sending one real webhook from the authorized process.
Questions about this workflow
Does a webhook need a particular payload?
Use the payload your process already sends and describe how Notis should interpret its context in the prompt.
Can this update an external review system?
The available Faceup action retrieves statistics; the automation reports the summary through its selected Notis channel.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Faceup. A trigger fires from one place; an action lands in another.
Notion triggers
Faceup actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
FaceUp GraphQL Statistics Query
Tool to execute a graphql query to retrieve faceup statistics. use when you need to fetch or filter metrics (e.g., by date range or school ids).
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 Faceup, 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 Faceup.