Start a new safety data source with a shared baseline
When your team creates a new place to organize safety work, pair it with a quick view of the reporting activity it will help review.
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
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 new tracking structure can collect information before anyone establishes how it relates to the wider reporting picture.
- Prompt a baseline check when a new source of safety work is created.
- Help owners connect new tracking structures with current measures.
- Keep setup from becoming a series of disconnected tasks.
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 query Faceup statistics when a safety data source is created.
- 3Describe the safety context and measures the team should review as a baseline.
- 4Select the Notion Data Source Created trigger and choose a channel for run reports.
- 5Test by creating one relevant data source or validate the trigger with a real event.
Questions about this workflow
Can a template create multiple trigger events?
Yes. A template-based database creation can produce one data source event per data source it creates.
Does this trigger when a whole database is created?
No. It fires when a data source is created; the separate Database Created event represents the container.
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.