Turn approved access tasks into GitHub team permissions
Capture the organization, team, repository, and access level in Todoist; Notis carries out the GitHub update and reports the result.
Trigger
New Task Created
Trigger when a new task is added to Todoist.
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
Approved team access changes can linger because they require a separate, easy-to-postpone GitHub admin session.
- Close approved access requests promptly
- Reduce admin context switches
- Keep a readable request trail in Todoist
Setup
Build it in a few focused steps.
- 1Connect your Todoist and GitHub accounts to Notis.
- 2Ask Notis to set GitHub team repository permissions from new Todoist access tasks that name the organization, team, repository, and level.
- 3Select the New Task Created event and your preferred reporting channel.
- 4Test with a low-risk permission request in a repository you administer.
Questions about this workflow
Which permission levels can be requested?
Use a permission supported by the repository and organization, and make sure the named team belongs to that organization.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Todoist to GitHub. A trigger fires from one place; an action lands in another.
Todoist triggers
GitHub actions
New Task Created
Trigger when a new task is added to Todoist.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Todoist and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.