Keep available Kaleido regions close to deployment planning
Edit your deployment plan in Notion and have Notis retrieve Kaleido's regions and endpoints, giving you current reference details as you work through the plan.
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 Regions
Tool to retrieve the list of deployment zones and endpoints. Use after authenticating to list available regions.
Why this helps
Deployment notes can leave you searching separately for the regions and endpoints needed to evaluate the next step.
- Bring region and endpoint reference data into the planning flow.
- Reduce tab switching during deployment preparation.
- Keep the lookup connected to the evolving plan.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kaleido to Notis once through the portal.
- 2Create an automation with a plain-language instruction to retrieve Kaleido regions and endpoints when deployment-plan content changes.
- 3Select the Notion Page Content Updated trigger, scoped to the relevant page if useful.
- 4Choose a channel for run reports and test with one real plan edit.
Questions about this workflow
Does this select a region or deploy anything?
No. The action retrieves the available regions and endpoints for reference.
Can the trigger focus on one plan?
Yes. The Page Content Updated trigger can be scoped to a specific page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Kaleido. A trigger fires from one place; an action lands in another.
Notion triggers
Kaleido actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Organization Identity Proof
Tool to add an identity proof to an organization. Use when registering an x.509 certificate chain for an org immediately after creation.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create API Key
Tool to create a new API key for an organization. Use after confirming the org_id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete API Key
Tool to delete a specific API key. Use when you need to remove an API key by its identifier after confirming it's no longer in use.
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 API Keys
Tool to retrieve all API keys associated with the organization. Use when you need an overview of existing API keys after authenticating.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get App2App Runtimes
Tool to retrieve App2App runtimes by listing all services and filtering where service == 'app2app'. Use after authenticating to enumerate App2App service instances.
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 Application Credentials
Tool to retrieve application credentials for a specific environment. Use when you need to list DApp credentials after environment setup.
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 Consortia
Tool to retrieve all consortia associated with the organization. Use after authenticating to view existing consortia.
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 Event Streams
Tool to list all event streams configured in the environment. Use when you need to retrieve current event stream setups.
Connect any two apps with Notis in the middle.
Notion and Kaleido, 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 Kaleido.