Connect GitHub to Docmosis
When something happens in GitHub, Notis takes the next step in Docmosis. 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 Docmosis
Inspect Docmosis structure after a code scanning alert
When GitHub finds a new code scanning alert, inspect the relevant Docmosis template structure so the remediation brief can be prepared without hunting through template fields.
Check Docmosis readiness when a secret is exposed
When GitHub detects a secret scanning alert, verify that Docmosis is ready for the incident documentation workflow before the response begins.
Check the document template when a pull request opens
When a new GitHub pull request is created, inspect the Docmosis release or change-record template so the author can follow the right documentation path immediately.
Generate sample Docmosis data for a new issue
When a GitHub issue is added, generate sample data for the relevant Docmosis template so a repeatable issue brief can be prepared quickly.
Check template health after a failed check
When a GitHub check run fails, retrieve metadata for the relevant Docmosis template so document errors are not left hidden during technical triage.
Review Docmosis capacity after deployment status changes
When a GitHub deployment status is created, retrieve the Docmosis environment summary so founders can confirm plan and quota context around a release.
Review available templates when a release changes
When a GitHub release changes, list available Docmosis templates so release documentation does not depend on memory or scattered links.
Inspect release-template structure when a version tag is created
When GitHub creates a new repository tag, inspect the release-document template structure so versioned documentation starts with a known format.
Check documentation structure after a pull request review
When a pull request review is submitted, inspect the chosen Docmosis change-log template so review feedback and documentation expectations stay connected.
Supported Triggers and Actions
Notis builds workflows that link GitHub to Docmosis. A trigger fires from one place; an action lands in another.
GitHub triggers
Docmosis 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.
Docmosis: Delete Image(s)
Tool to delete one or more stored images. Use when you need to remove images; ensure imageName(s) are valid before use.
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.
Docmosis: Delete Template(s)
Tool to delete one or more templates from the environment. Use when you need to remove templates; multiple templates can be deleted in a single request.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Docmosis Environment Ready
Tool to verify environment readiness. Use when ensuring the environment is active and within quota before rendering documents.
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.
Docmosis Environment Summary
Tool to retrieve environment summary. Use when you need status, plan, and quota details of your Docmosis environment after authentication.
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.
Docmosis: Get API Key
Tool to extract the Docmosis API access key from connection metadata. Use before other Docmosis API calls to retrieve the Bearer token from the Authorization header.
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 Batch Upload Status
Tool to check the status of a template batch upload job. Use when monitoring batch upload progress or checking if a batch upload has completed.
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.
Download Docmosis Images
Tool to download one or more images. Use when you need to retrieve stored image files by name. If multiple names provided, images are returned in a zip archive.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Docmosis Render Queue
Tool to get current render queue status and utilization. Use when monitoring queue capacity before scheduling rendering tasks.
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 Docmosis
Connect any two apps with Notis in the middle.
Not just GitHub and Docmosis. 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 Docmosis.