Connect Notion to Gitea
When something happens in Notion, Notis takes the next step in Gitea. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Gitea
Recommend a matching Gitea gitignore
When a new Notion project page appears, find suitable Gitea gitignore templates and send a short recommendation with their contents for a quick repository setup.
Review Gitea license options for a project
When a project page is created in Notion, retrieve Gitea license template information and share a brief review checklist to help founders make an informed licensing decision.
Keep a Gitea version note with workspace updates
When a Notion page changes, check the Gitea instance version and include it in a concise run note, making it easier to keep operational context current.
Surface Gitea API limits after a Notion property change
After Notion page properties change, retrieve Gitea's general API settings and summarize relevant pagination and response-size constraints for the run report.
Review Gitea repository capabilities after schema changes
When a Notion data source schema changes, retrieve Gitea's general repository settings and report relevant feature availability for the team to consider.
Check Gitea attachment settings for a new database
When a Notion database is created, retrieve Gitea's attachment rules and provide a brief note for teams planning to keep project artifacts in issues or discussions.
Add Gitea UI context to a new data source
When a Notion data source is created, retrieve Gitea's general UI settings and report the instance theme and available reactions as useful interface context.
Find Gitea label templates when a team creates a view
When a new Notion view is created, retrieve Gitea label templates and share a concise reference for teams organizing work across a new planning view.
Bring license template details into a project subpage
When a project subpage is added in Notion, retrieve Gitea license template information and send a concise reference for the related project discussion.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and Gitea
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.