Sync Notion Team Structure to GitHub Permissions
When team roles change in Notion, GitHub permissions update in real time. Your access control stays in sync with your actual organization.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Add or update team repository permissions
Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.
Why this helps
Managing who can push to which repos gets messy fast. Role changes in Notion don't propagate to GitHub, leaving stale permissions that create security gaps or block contributors.
- Keep permissions automatically aligned with roles
- Avoid security gaps from outdated access
- Reduce manual permission audits
- Simplify team restructuring
Setup
Build it in a few focused steps.
- 1Connect Notion and GitHub to Notis.
- 2Identify your Notion team database with role or permission properties.
- 3Tell Notis: 'When a team member's role changes in Notion, update their GitHub team permissions to match.'
- 4Select your notification channel and test by updating one person's role in Notion.
Questions about this workflow
How does Notis know which GitHub team to update?
You map it once: tell Notis 'Backend team in Notion = backend-team in GitHub' and it handles the rest.
What if someone has multiple roles?
Notis can add them to multiple GitHub teams based on multiple Notion properties.
Can permissions be revoked automatically?
Yes. Tell Notis 'If role is removed, revoke GitHub access' and it stays in sync.
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.