Give every Manus engineering task a GitHub owner
A clear owner means one less decision sitting in your head.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Important engineering work arrives without a named person and disappears into the backlog.
- Prevents unowned work from stalling
- Creates accountability at intake
- Reduces daily follow-up messages
Setup
Build it in a few focused steps.
- 1Connect Manus and GitHub to Notis once through the portal.
- 2Create an automation in Automations -> New Automation, or ask Notis in plain language.
- 3Tell Notis: Assign each incoming Manus engineering task to the appropriate GitHub issue owner using the task context.
- 4Choose an incoming webhook trigger, select a channel for run reports, and test with one real task.
Questions about this workflow
Does Manus need a native Notis trigger?
No. Notis receives the Manus event through an incoming webhook.
Can Notis choose the assignee?
Yes. The plain-language instruction tells Notis how to interpret the Manus task context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Manus to GitHub. A trigger fires from one place; an action lands in another.
Manus triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Not just Manus and GitHub. 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 GitHub.