Prepare new Linear issues as Gitea-ready briefs
Turn each new Linear issue into a clear Markdown brief, then render it as HTML using Gitea's comment context for a readable handoff.
Connect Linear to Gitea
When something happens in Linear, 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
Triggers when a new comment is received.
Do this · Action
Retrieve a user’s ActivityPub profile.
Examples
Ways Notis can move work from Linear to Gitea
Turn Linear comments into compact Gitea-ready summaries
When a Linear comment arrives, have Notis distill its decision or request into concise Markdown and render the raw Markdown as HTML for a quick handoff.
Format Linear issue changes as implementation notes
Summarize a changed issue's meaningful updates in Markdown, then render it with Gitea's comment context for a clear implementation note.
Prepare a project kickoff outline for repository work
Shape new Linear project context into a structured Markdown kickoff outline, then render it with Gitea markup support for a readable start.
Summarize project changes for implementation planning
When Linear project properties change, create a concise Markdown note about the planning impact and render it as HTML with Gitea's comment context.
Make Linear project updates easier to scan
Condense a posted project update into a status digest in Markdown and render it as HTML for a quick repository-side review.
Format private-team comment context for a controlled handoff
Summarize a private-team Linear comment into a minimal handoff note, then render it with Gitea's comment context for review by the connected user.
Prepare a focused brief for private-team issues
Turn each visible private-team issue into a minimal Markdown brief and render it with Gitea markup support for a controlled handoff.
Summarize private issue property changes
Describe the meaningful property changes on a private Linear issue in concise Markdown and render the note as HTML for review.
Supported Triggers and Actions
Notis builds workflows that link Linear to Gitea. A trigger fires from one place; an action lands in another.
Linear triggers
Gitea actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
TriggerScheduled
Get ActivityPub Person Actor
Retrieve a user’s ActivityPub profile.
ActionInstant
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
TriggerInstant
Get General API Settings
Retrieves global Gitea API settings, including pagination limits and response size constraints.
ActionInstant
Comment Received Trigger
Triggers when a new comment is received.
TriggerInstant
Add Issue Dependency
Make one repository issue depend on another.
ActionInstant
Issue Created Trigger
Triggers when a new issue is created.
TriggerInstant
Get General Attachment Settings
Retrieve an instance’s attachment settings.
ActionInstant
Issue Updated Trigger
Triggers when an issue is updated, such as when its labels or status change.
TriggerInstant
Cancel Workflow Run
Cancel an active Actions workflow run and return its resulting state.
ActionInstant
Private Team Comment Created
Triggers when a comment is posted on an issue in a private team.
TriggerPolling
Get General Repository Settings
Retrieve an instance’s repository settings.
ActionInstant
Private Team Issue Created
Triggers when an issue appears in a private team.
TriggerPolling
Change Repository Files
Create, update, upload, rename, or delete repository files in a single commit.
ActionInstant
Private Team Issue Properties Updated
Triggers when an issue's properties change in a private team.
TriggerPolling
Get General UI Settings
Retrieve an instance’s interface settings.
ActionInstant
Trigger Types
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 schedule (recurring or one-time), and a change in one of your Notis databases.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.
New Notion pageStripe chargeCalendar event
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.
Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used
Scheduled triggers
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Daily · 8:00Weekdays onlyOnce · Dec 13
Beta
Database triggers
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Row addedProperty editedValue > limit
Why AI automation
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.
Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use
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:
TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability
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
All12Manager5Telegram1Messages0WhatsApp2Email4Slack8
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.
Related pairs
More ways to connect Linear and Gitea
Connect any two apps with Notis in the middle.
Linear and Gitea, or any other combination from 1,500+ 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.