Keep account follow-up issues moving
Ask Notis to review the Bigpicture research you provide and assign linked GitHub issues only when an eligible owner is clearly identified.
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
Follow-up can stall when research is complete but nobody is clearly accountable for the next GitHub task.
- Surface follow-up ownership in GitHub
- Avoid guessing an assignee when research is incomplete
- Get a report when an issue cannot be assigned
Setup
Build it in a few focused steps.
- 1Connect Bigpicture io and GitHub once in Notis.
- 2Create an automation in Notis from any channel or in Automations, New Automation.
- 3In one instruction, ask Notis to review the supplied Bigpicture research and assign a linked issue only when the repository, issue number, and GitHub username are present and the owner is explicitly identified.
- 4Choose a recurring schedule trigger and select where run reports should go.
- 5Test with one real research record that includes a valid linked issue and assignable username.
Questions about this workflow
Can Notis infer who should own the follow-up?
It should assign only when the research or instructions clearly identify an owner and provide that person's GitHub username. Otherwise it should report the missing information.
Does this create a follow-up issue?
No. The available GitHub action assigns users to an existing issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bigpicture io to GitHub. A trigger fires from one place; an action lands in another.
Bigpicture io 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.
Bigpicture io 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.