Check repository capabilities when your tracking schema evolves
A structural change in Notion can prompt a quick review of Gitea repository feature availability.
Trigger
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.
Action
Get General Repository Settings
Tool to retrieve the Gitea instance's global settings for repositories including feature flags for mirroring, HTTP Git, migrations, stars, time tracking, and LFS. Use when you need to understand which repository features are enabled or disabled at the instance level.
Why this helps
A new or renamed planning field can change the team's needs, while repository capabilities remain out of sight.
- Make repository feature availability easier to revisit.
- Connect planning structure changes to an operational check.
- Get a concise summary for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Notion and Gitea to Notis once in the portal.
- 2Create an automation in the portal or tell Notis what outcome you want in plain language.
- 3Ask Notis to look up Gitea general repository settings after a Notion data source schema update and summarize relevant enabled features.
- 4Pick the Notion Data Source Schema Updated trigger and a channel for run reports.
- 5Test with one real schema change.
Questions about this workflow
Will this enable repository features?
No. It reads the instance-level settings and reports their availability.
Why use a schema update as a cue?
A changed planning structure can signal a changed workflow need, making it a natural moment to review relevant repository capabilities.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gitea. A trigger fires from one place; an action lands in another.
Notion triggers
Gitea actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get ActivityPub Person Actor
Tool to retrieve the ActivityPub Person actor for a Gitea user. Use when you need to fetch a user's ActivityPub representation for federation purposes or to get ActivityStreams-formatted user data.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get General API Settings
Tool to retrieve the Gitea instance's global API settings including pagination limits and response size constraints. Use when you need to understand API rate limits or configuration parameters.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get General Attachment Settings
Tool to retrieve the Gitea instance's global settings for file attachments including enabled status, allowed file types, size limits, and file count limits. Use when you need to understand the attachment configuration of the instance.
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 General Repository Settings
Tool to retrieve the Gitea instance's global settings for repositories including feature flags for mirroring, HTTP Git, migrations, stars, time tracking, and LFS. Use when you need to understand which repository features are enabled or disabled at the instance level.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get General UI Settings
Tool to retrieve the Gitea instance's global settings for UI including default theme, allowed reactions, and custom emojis. Use when you need to understand the UI configuration of the instance.
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 Gitignore Template Info
Tool to retrieve information about a specific gitignore template. Use when you need the content of a gitignore template for repository creation or configuration.
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 Label Template Info
Tool to retrieve all labels from a specific label template. Use when you need to view the predefined label set for repository configuration.
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 License Template Info
Tool to retrieve information about a specific license template. Use when you need the content and details of a license template for repository creation or configuration.
Connect any two apps with Notis in the middle.
Notion and Gitea, 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 Gitea.