Keep handoff notes connected to the Apilio logicblock inventory
When a handoff page changes, Notis can retrieve Apilio logicblocks and add the current inventory to the run report for the next person or next work session.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Get Logicblocks
Tool to fetch all logicblocks of a user. use after authenticating with apilio api when you need to list available logicblocks.
Why this helps
Handoff details can be easy to lose across sessions, especially when the next step depends on knowing what automations already exist.
- Give handoff updates current automation inventory context.
- Make work easier to resume after a break or interruption.
- Reduce repeated searching during transitions.
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 logicblocks when a block changes on the handoff page.
- 3Select Page Updated and specify the handoff page.
- 4Choose a channel for run reports and test by updating one real handoff block.
Questions about this workflow
Can I watch any page?
This Page Updated trigger is for a specified page.
Will it launch an automation in Apilio?
No. It retrieves the user's logicblock list for the report.
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.