Skip to content
Notis

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

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

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

List Groups

Browse groups you can access.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

List Polls

Browse polls you can access.

ActionInstant

New Workflow Artifact Created

Triggers when a new workflow artifact is created in a repository.

TriggerPolling

Show Group

View details for a group.

ActionInstant

Branch Changed

Triggers when a branch receives commits or its protection settings change.

TriggerPolling

SHOW_POLL

View details for a poll.

ActionInstant

New Branch Created

Triggers when a new branch is created in a repository.

TriggerPolling

Check Run Status / Conclusion Changed

Triggers when a check run’s status or conclusion changes.

TriggerPolling

Check Suite Status / Conclusion Changed

Triggers when a check suite’s status or conclusion changes for a reference.

TriggerPolling

New Code Scanning Alert Created

Triggers when a new code scanning alert is created in a repository.

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

Notis

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 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything 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 GitHub and Loomio

Connect any two apps with Notis in the middle.

GitHub and Loomio, 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 Loomio.