Turn review findings into clear issue ownership
Move findings from a Cloudlayer document into GitHub with a clear owner on each related issue.
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
Document reviews often create follow-up work without making it obvious who owns each issue.
- Give actionable findings a visible owner
- Reduce manual follow-up after document reviews
- Use ownership guidance supplied with the webhook
Setup
Build it in a few focused steps.
- 1Connect Cloudlayer and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Tell Notis to match supplied review findings to GitHub issues and assign owners only when the request includes clear ownership guidance.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real review summary that includes issue references and ownership guidance.
Questions about this workflow
Can this infer who owns an issue?
The automation should use ownership guidance supplied in the request. The available action adds or removes issue assignees, and changes may be ignored if the authenticated user lacks push access.
What should the webhook include?
Include the document findings and any issue references or ownership rules needed to make assignments clear.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cloudlayer to GitHub. A trigger fires from one place; an action lands in another.
Cloudlayer 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.
Cloudlayer 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.