Keep numeric state visible while updating plans
A planning page edit can prompt Notis to retrieve Apilio numeric variables, making a current snapshot available while the work is fresh in mind.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Get Numeric Variables
Tool to fetch all numeric variables. use after authenticating the apilio api.
Why this helps
Planning updates can require checking operational values, but an interruption between tools can make that check easy to forget.
- Bring numeric variables into a planning edit review.
- Reduce the chance of losing a follow-up after switching tools.
- Make planning sessions easier to resume.
Setup
Build it in a few focused steps.
- 1Connect Notion and Apilio to Notis once through the portal.
- 2Create an automation with a plain-language prompt to retrieve Apilio numeric variables when content changes on the selected planning page.
- 3Select Page Content Updated and scope it to the page or relevant data source.
- 4Choose a channel for run reports and test with one real planning edit.
Questions about this workflow
Does this cover page property changes?
No. Page Content Updated tracks body content edits; use Page Properties Updated for property changes.
Can it set a numeric value?
No. This action retrieves numeric variables only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Apilio. A trigger fires from one place; an action lands in another.
Notion triggers
Apilio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Boolean Variables
Tool to fetch all boolean variables. use when you need the full list of boolean variables and their current states.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Conditions
Tool to fetch all evaluatable conditions. use when you need to list available conditions.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Logicblocks
Tool to fetch all logicblocks of a user. use after authenticating with apilio api when you need to list available logicblocks.
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 Numeric Variables
Tool to fetch all numeric variables. use after authenticating the apilio api.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get String Variables
Tool to fetch all string variables. use after authenticating the apilio api.
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 Apilio, 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 Apilio.