Connect GitHub to Gitea
When something happens in GitHub, 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 GitHub to Gitea
Turn GitHub security alerts into readable Gitea briefs
When GitHub finds a new code scanning alert, have Notis render a concise Markdown brief in Gitea with the affected rule, severity, location, and recommended next step.
Create a response brief for GitHub secret alerts
When GitHub detects a secret scanning alert, have Notis render a Gitea Markdown response brief that captures the secret type, validity status, exposure signals, and immediate containment steps.
Turn failed GitHub workflow runs into debug notes
When a GitHub Actions workflow run changes to failure, have Notis render a structured markup debug note in Gitea with the run context, likely failure point, and suggested next check.
Prepare a recovery brief for failed deployments
When a GitHub deployment status becomes failure or error, have Notis render a Gitea Markdown recovery brief with environment, commit, status, and rollback questions.
Summarize pull request reviews for faster decisions
When a GitHub pull request review is submitted, have Notis render a Gitea Markdown decision summary covering the review outcome, requested changes, and remaining questions.
Convert inline review comments into action notes
When a new GitHub pull request review comment arrives, have Notis render a Gitea Markdown action note with the comment, code location, author, and suggested follow-up.
Create a handoff brief for every new pull request
When a GitHub pull request opens, have Notis render a Gitea Markdown handoff brief with intent, scope, test status, review needs, and the next decision.
Refresh review context after new pull request commits
When a new commit is added to a GitHub pull request, have Notis render a Gitea Markdown refresh note explaining what changed and what reviewers should revisit.
Turn failed check runs into triage notes
When a GitHub check run concludes with failure, have Notis render a Gitea Markdown triage note with the check name, commit, status, timing, and investigation path.
Supported Triggers and Actions
Notis builds workflows that link GitHub to Gitea. A trigger fires from one place; an action lands in another.
GitHub triggers
Gitea actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
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.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
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.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
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.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
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.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
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 trough 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 GitHub and Gitea
Connect any two apps with Notis in the middle.
Not just GitHub and Gitea. Any combination from 1,000+ 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 Gitea.