Give follow-up work a clear owner
A scheduled review can connect a client follow-up that needs action to the GitHub owner responsible for its delivery issue.
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 dates can pass without a clear owner for the engineering work connected to the proposal.
- Make follow-up work visible to a named owner.
- Connect a client due date with its delivery issue.
- Reduce the mental load of remembering who needs to act.
Setup
Build it in a few focused steps.
- 1Connect Better Proposals and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for proposal follow-up ownership.
- 3Tell Notis in one instruction to review proposals due for follow-up and assign the linked GitHub issue to the supplied owner when the follow-up needs engineering action.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real due proposal that includes a linked issue and owner username.
Questions about this workflow
Will every proposal follow-up create an issue assignment?
Your instruction can limit assignment to follow-ups that need engineering action. The issue and username must be supplied or otherwise known.
What if the assignee cannot be assigned?
GitHub can silently ignore assignment changes when the authenticated user lacks push access to the repository.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Better proposals to GitHub. A trigger fires from one place; an action lands in another.
Better proposals 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.
Better proposals 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.