Review customer repository access on a schedule
Create a regular checkpoint for customer repository access and route results to a report channel.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if a user is a repository collaborator
Checks if a user is a collaborator on a specified github repository, returning a 204 status if they are, or a 404 status if they are not or if the repository/user does not exist.
Why this helps
Customer access checks can fall behind when nobody has a clear recurring reminder to review account and repository details.
- Create a recurring checkpoint for account access review.
- Check collaborator status for available user and repository details.
- Collect results in the chosen run report destination.
Setup
Build it in a few focused steps.
- 1Connect Agile CRM and GitHub once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language.
- 3In one instruction, ask Notis to review the available customer GitHub user and repository details and check collaborator status for each.
- 4Choose the notis_cron trigger and where run reports should go.
- 5Test with one real customer account and verify the available account details are sufficient.
Questions about this workflow
What if an account has no GitHub username or repository?
Notis needs those details to check collaborator status. Supply missing values in the account data or treat that account as needing follow-up.
Does this change GitHub access?
No. This workflow checks whether the user is already a collaborator and reports the result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agile CRM to GitHub. A trigger fires from one place; an action lands in another.
Agile CRM 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.
Agile CRM 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.