Give approved project work the Codespaces access it needs
When a trusted approval signal arrives, Notis can grant the approved repository access to its existing Codespaces secret.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add a selected repository to a user secret
Grants a specified repository access to an authenticated user's existing codespaces secret, enabling codespaces created for that repository to use the secret.
Why this helps
A paid project can lose momentum when a developer still cannot start the cloud workspace they need.
- Removes an early developer blocker
- Keeps secret access linked to an explicit approval
Setup
Build it in a few focused steps.
- 1Connect YNAB and GitHub to Notis once.
- 2Create a new automation with an incoming webhook trigger.
- 3Describe the approval signal, repository, and existing Codespaces secret access to grant.
- 4Choose a channel for run reports.
- 5Test with a low-risk approved repository.
Questions about this workflow
Does this create a new secret?
No. It grants a repository access to an existing authenticated user's Codespaces secret.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ynab to GitHub. A trigger fires from one place; an action lands in another.
Ynab triggers
GitHub actions
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 Ynab 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.