Keep recurring document follow-ups owned
A scheduled review can turn document status into a clear GitHub next step.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Recurring document checks can surface work without making it clear who should act next.
- Make follow-up ownership explicit.
- Create a predictable review routine.
- Reduce unattended work surfaced by document checks.
Setup
Build it in a few focused steps.
- 1Connect Algodocs and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Write one instruction naming the Algodocs records to review and the GitHub issue and assignee for each follow-up.
- 4Pick a recurring schedule, select the report destination, and test with one real record and issue.
Questions about this workflow
Does Algodocs trigger this automation?
No. A Notis cron schedule starts it, and the instruction tells Notis which Algodocs records to review.
Where do issue and owner details come from?
Provide repository, issue number, and GitHub username in the instruction or the data available to the run.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Algodocs to GitHub. A trigger fires from one place; an action lands in another.
Algodocs 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.
Algodocs 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.