Bring current Northflank regions into capacity planning
Make location planning easier with an up-to-date region lookup when a new view is created.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
List Regions
Tool to retrieve available project regions in Northflank. Use when you need to see which geographic regions are available for deploying projects and resources.
Why this helps
Capacity planning can stall when someone needs to leave the planning page to look up supported regions.
- Bring region options into planning follow-up.
- Reduce context switching during infrastructure decisions.
- Use a current lookup rather than relying on memory.
Setup
Build it in a few focused steps.
- 1Connect Notion and Northflank to Notis once.
- 2Create an automation asking Notis to retrieve Northflank regions when the capacity planning view is created.
- 3Select View Created and describe how the relevant view should be identified.
- 4Choose a report channel and test by creating a planning view.
Questions about this workflow
Can it only respond to a particular view type?
The event includes the view type. Describe in the instruction which planning views matter.
Does this action change a project region?
No. It retrieves available regions as planning context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Northflank. A trigger fires from one place; an action lands in another.
Notion triggers
Northflank actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create or Update Project
Tool to create a new project or update an existing project in Northflank (upsert operation). Use when you need to ensure a project exists with specific configuration, regardless of whether it's already created.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create or Update Secret
Tool to create or update a secret group in a Northflank project. Use when you need to store encrypted runtime variables or build arguments that can be inherited by services and jobs.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Project
Tool to create a new project in Northflank. Use when you need to set up a new project with specific ID, name, region, and configuration.
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.
Create Secret
Tool to create a secret group in a Northflank project. Use when you need to store encrypted environment variables that can be inherited by services and jobs.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Project
Tool to permanently delete a Northflank project and all associated resources. Use when you need to remove a project including all builds, deployments, jobs, addons, secret groups, and configurations.
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.
Get DNS ID
Tool to retrieve the DNS identifier for the authenticated account. Use when you need to get the DNS ID used for generating DNS entries for services and domains.
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.
Get Project
Tool to retrieve detailed information about a specific Northflank project. Use when you need to get project configuration, region, networking settings, or metadata.
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.
Get Secret
Tool to retrieve a secret from a Northflank project including its contents. Use when you need to view the actual secret values and metadata for a specific secret.
Connect any two apps with Notis in the middle.
Notion and Northflank, 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 Northflank.