Connect GitHub to Loomio

When something happens in GitHub, Notis takes the next step in Loomio. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from GitHub to Loomio

View example

Check Loomio groups when a pull request arrives

When a GitHub pull request is opened, retrieve the accessible Loomio groups so the founder can quickly identify the right decision space for review.

View example

Check Loomio polls after a pull request review

When a GitHub pull request review is submitted, list accessible Loomio polls so unresolved product or process decisions do not disappear inside code review.

View example

Find a Loomio group for each new GitHub issue

When a new GitHub issue is added, retrieve accessible Loomio groups to help route product, customer, or operational questions to the right conversation space.

View example

Look up Loomio polls for issues assigned to you

When GitHub assigns a new issue to you, list accessible Loomio polls to check whether the work depends on an existing team decision.

View example

Check Loomio polls after inline review comments

When a new inline GitHub review comment arrives, list relevant Loomio polls so questions raised in code review can be resolved in the right decision thread.

View example

Find the right Loomio group when PR reviewers change

When requested GitHub pull request reviewers change, retrieve accessible Loomio groups to keep review ownership and decision context aligned.

View example

Check Loomio polls when a pull request changes state

When a GitHub pull request opens, closes, or synchronizes, list accessible Loomio polls to keep implementation changes connected to active decisions.

View example

Find Loomio groups when issue details change

When tracked GitHub issue properties change, retrieve accessible Loomio groups to reassess where the updated work should be discussed.

View example

Check Loomio polls after GitHub issue labels change

When labels change on a GitHub issue, list accessible Loomio polls to surface new product, priority, or risk decisions connected to the updated classification.

Supported Triggers and Actions

Notis builds workflows that link GitHub to Loomio. A trigger fires from one place; an action lands in another.

GitHub triggers

Loomio 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.

TriggerPolling

List Groups

Tool to list all groups accessible to the user. use when you need to retrieve and paginate user groups.

ActionInstant

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.

TriggerPolling

List Polls

Tool to list all polls accessible to the user. use when you need to retrieve poll ids and basic metadata.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

Show Group

Tool to retrieve details of a specific group. use when you have a group id and need its full metadata.

ActionInstant

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.

TriggerPolling

SHOW_POLL

Tool to retrieve details of a specific poll. use when you have a poll id and need its full metadata.

ActionInstant

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

Commit Event

Triggered when a new commit is pushed to a repository.

TriggerInstant

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 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.

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

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

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.