Refresh a Fly app catalog after a Notion schema change
When you adjust how infrastructure is tracked, refresh the Fly app list at the same time and review whether your catalog still covers the current apps.
Trigger
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.
Action
List Apps
Tool to list all Fly Apps in an organization. Use when you need to retrieve apps for a specific organization using its slug.
Why this helps
Changes to infrastructure tracking can leave the app catalog out of sync with what is running.
- Pair a structural tracking change with an app catalog refresh.
- Check whether the documentation still covers deployed apps.
- Keep catalog maintenance from becoming a forgotten task.
Setup
Build it in a few focused steps.
- 1Connect Notion and Fly to Notis once in the portal.
- 2Create an automation with one plain-language instruction to identify the organization covered by the changed infrastructure data source, retrieve its Fly app list, and report it for catalog review.
- 3Select the Notion Data Source Schema Updated trigger, choose a run-report channel, and test with one real schema update.
Questions about this workflow
Does this change the Notion schema or Fly apps?
No. It retrieves the Fly app list and reports it for review.
Why use a schema update as the trigger?
A change to tracking structure is a useful moment to review whether the infrastructure catalog still reflects the apps in Fly.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Fly. A trigger fires from one place; an action lands in another.
Notion triggers
Fly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add WireGuard Peer
Tool to add a WireGuard peer connection to a Fly.io organization for private network access. Use when setting up VPN access or private networking between your infrastructure and Fly.io.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check App Name Availability
Tool to validate an app name for Fly.io app creation. Use when you need to check if a proposed app name is available before attempting to create a new app. Returns availability status via GraphQL query.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Check Jobs
Execute GraphQL queries against the Fly.io checkJobs endpoint. Retrieves check jobs with their schedules, URLs, and configuration. Supports pagination via first/last/after/before parameters. Returns both data and errors for flexible error handling.
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.
Check User Only Token
Check whether the authentication token only allows user access. Returns false if the token allows organization access, true if it only allows user access.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Health Check Job
Tool to create a health check job for monitoring application endpoints in Fly.io. Use when you need to set up automated health monitoring for a URL from multiple geographic locations.
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.
Create Check Job Run
Triggers a run of an existing health check job on Fly.io. Use when you need to manually trigger a health check for monitoring or testing purposes.
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.
Create Delegated WireGuard Token
Tool to create a delegated WireGuard token for peer management in a Fly.io organization. Use when you need to generate a token for managing WireGuard peers with delegated access.
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.
Create Third-Party Configuration
Tool to create a third-party service configuration for discharging macaroon caveats. Use when you need to configure external authorization services for Fly.io token validation.
Connect any two apps with Notis in the middle.
Notion and Fly, 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 Fly.