Route archival follow-up to a GitHub owner
When an Archive.org review needs code or documentation follow-up, have Notis locate the existing issue you specify and assign it to its owner.
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
A review can identify needed work without making clear who should pick up the related GitHub issue.
- Give review follow-up a clear owner
- Reduce manual handoffs between research and code tracking
- Keep assignments tied to an existing GitHub issue
Setup
Build it in a few focused steps.
- 1Connect Archive.org and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for the review handoff.
- 3Write one instruction explaining what Archive.org review to assess, how to find the related existing GitHub issue, and who to assign when follow-up is warranted.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real reviewed item and a GitHub issue; confirm the proposed assignee can be assigned.
Questions about this workflow
Does the automation create a GitHub issue if none matches?
No. It assigns users to an existing issue. Include a way to identify that issue in your instruction.
What if GitHub cannot assign the selected user?
The assignment may be ignored if the user cannot be assigned or the authenticated account lacks push access. Check the run report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Archive.org to GitHub. A trigger fires from one place; an action lands in another.
Archive.org 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.
Archive.org 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.