Find the right Loomio group for every new pull request
A new pull request should not create a scavenger hunt for where review belongs.
Trigger
New Pull Request Created
Triggers when a new pull request is created in GitHub, matching the optional configured filters. Emits an event for each newly created pull request. Supports filtering by repository, owner/organisation, author, assignee, label, state, base branch, head branch, and draft status.
Action
List Groups
Tool to list all groups accessible to the user. use when you need to retrieve and paginate user groups.
Why this helps
New work can sit waiting while the founder searches for the right group and context.
- Cuts the time spent deciding where a technical discussion belongs.
- Creates a consistent handoff from code activity to shared decisions.
- Keeps review conversations easier to find later.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Loomio to Notis once through the portal.
- 2Create an automation in Automations or ask Notis in plain language to check Loomio groups whenever a new GitHub pull request is created.
- 3Use the instruction: identify the most relevant accessible Loomio group for the pull request and report its details.
- 4Pick the GitHub new pull request trigger and choose a channel for run reports.
- 5Test it with one real pull request.
Questions about this workflow
Does this create a Loomio discussion automatically?
No. It retrieves accessible group details so you can choose the right place for the next decision.
Can I use it for a specific repository?
Yes. Describe the repository or pull request scope in the plain-language instruction.
When this happens · Trigger
Do this · Action
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.
List Groups
Tool to list all groups accessible to the user. use when you need to retrieve and paginate user groups.
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.
List Polls
Tool to list all polls accessible to the user. use when you need to retrieve poll ids and basic metadata.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Show Group
Tool to retrieve details of a specific group. use when you have a group id and need its full metadata.
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.
SHOW_POLL
Tool to retrieve details of a specific poll. use when you have a poll id and need its full metadata.
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.
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.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Loomio. Any combination from 1,000+ 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.