Automate Security on Departures with Notion-Based Offboarding
A team member is offboarded in Notion. Notis immediately blocks them from your GitHub organization, ensuring no lingering access.
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
Block a user from an organization
Blocks an existing github user from an existing organization, preventing their contributions, collaboration, and forking of the organization's repositories.
Why this helps
Offboarding is chaotic. Access gets revoked in some systems but forgotten in others. GitHub org access lingers after someone leaves, creating security risks that neurodivergent founders easily miss under other stressors.
- Automate security revocation on departure
- Eliminate forgotten access revocation
- Keep your GitHub org secure
- Reduce manual offboarding steps
Setup
Build it in a few focused steps.
- 1Connect Notion and GitHub integrations.
- 2Create or identify an offboarding database in Notion (or mark departures in a team roster).
- 3Tell Notis: 'When someone's offboarded in Notion, block them from my GitHub organization.'
- 4Verify which organization to target.
- 5Test by marking one person as offboarded in Notion.
Questions about this workflow
Does this affect repositories they contributed to?
Blocking from the org prevents future access. Use this for trusted orgs; for public access, set repos to private separately.
Can I reverse this if someone returns?
Yes, just unblock them in GitHub or tell Notis to remove the block when their status changes in Notion.
Does this delete their fork or contributions?
No, it just removes their access to your org. Their contributions remain.
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.