Route briefed work to GitHub assignees
Pass a Cloudpress brief to Notis with the issue and people responsible, and add those assignees in GitHub.
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
Ownership gets lost when a work brief and its GitHub issue are maintained separately.
- Make issue ownership visible in the repository.
- Reduce follow-up to transfer assignments from a brief.
- Use the assignee names supplied with the request.
Setup
Build it in a few focused steps.
- 1Connect Cloudpress and GitHub once in the Notis portal.
- 2Create a named automation in Automations, New Automation.
- 3In one instruction, tell Notis to add the requested assignees to the GitHub issue identified in the incoming Cloudpress brief.
- 4Choose the webhook trigger and a channel for run reports.
- 5Test with one real brief containing a repository, issue number, and assignable GitHub usernames.
Questions about this workflow
What information does the webhook need?
Provide the repository owner and name, issue number, and GitHub usernames to assign.
What if a username cannot be assigned?
GitHub may ignore changes if the authenticated user lacks push access. Test with a real issue and users who can be assigned.
Can the automation remove assignees too?
The selected action supports adding or removing assignees. State clearly in the instruction which names to add or remove.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cloudpress to GitHub. A trigger fires from one place; an action lands in another.
Cloudpress triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Cloudpress and GitHub, or any other 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.