Automate Release Approvals from Release Notes
Release notes are finalized in Notion. Notis immediately approves the waiting GitHub workflow, and your release ships.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Approve a workflow run for a fork pull request
Approves a workflow run from a forked repository's pull request; call this when such a run requires manual approval due to workflow configuration.
Why this helps
Releases coordinate across teams: QA approves in Notion, but the GitHub release workflow waits for manual approval. That final step is easy to forget during a release push.
- Approve releases once in Notion, automation takes over
- Ship without waiting for manual GitHub approval
- Keep release process visible in planning docs
- Reduce delays on release day
Setup
Build it in a few focused steps.
- 1Connect Notion and GitHub integrations.
- 2Create a Notion database or page for release notes with an approval status property.
- 3Tell Notis: 'When release notes are marked as approved in Notion, approve the matching GitHub release workflow.'
- 4Specify which GitHub workflows to auto-approve.
- 5Test by marking release notes as approved in Notion.
Questions about this workflow
What if multiple workflows are waiting?
Tell Notis which one: 'Approve the build-and-release workflow for main branch.'
Can this still be overridden in GitHub?
Yes, this automates the approval flow you do in Notion.
What prevents accidental releases?
You control the trigger: only approve when all conditions are met in Notion.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to GitHub. A trigger fires from one place; an action lands in another.
Notion triggers
GitHub actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
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.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
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.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
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.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
New Page
Triggers when a new page is added to a Notion database.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Not just Notion and GitHub. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.