Keep policy renewal follow-ups assigned
Let a scheduled review surface renewal work and put issue ownership back in view, so fewer important dates slip by.
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
Renewal follow-ups can sit unowned when policy status and team task tracking live in different places.
- Review policy follow-up information on a predictable schedule.
- Add or remove GitHub issue assignees as the owner needs change.
- Keep renewal work connected to an accountable person.
Setup
Build it in a few focused steps.
- 1Connect AgencyZoom and GitHub once in the Notis portal.
- 2Create an automation from Automations, New Automation, and name it for renewal follow-up.
- 3In one instruction, tell Notis which AgencyZoom policy context to review and how to assign relevant GitHub issues.
- 4Choose a recurring schedule, select where run reports should go, and test with one real example.
Questions about this workflow
Can the workflow discover upcoming renewals from an AgencyZoom event?
No AgencyZoom trigger events are listed. This workflow runs on a schedule, and Notis can use AgencyZoom information available through the connected app or context you supply.
Does the action create issues?
No. The selected GitHub action updates assignees on an existing issue. Your instruction should identify the relevant issue and intended owner using information available to Notis.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agencyzoom to GitHub. A trigger fires from one place; an action lands in another.
Agencyzoom 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.
Agencyzoom 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.