Keep account team access aligned with the request
Turn a reviewed account access change into an update to the team’s GitHub repository permission.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add or update team repository permissions
Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.
Why this helps
Team access changes can be missed when a customer or account update is handled in Agile CRM but permissions live in GitHub.
- Update a team’s permission level for a specified organization repository.
- Keep account access changes connected to the request that initiated them.
- Receive a run report for permissions that need attention.
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 set the supplied organization team’s permission on the supplied repository to the requested level when the change is approved.
- 4Choose the notis_webhook trigger and where run reports should go.
- 5Test with one approved request for a team and repository in the same organization.
Questions about this workflow
Which permission levels can this action set?
The action supports read, write, or admin permissions for a team on a repository within an organization.
Does this work with personal repositories?
No. The listed action is for a repository within an organization, and the team must be a member of that organization.
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.