Prepare Actions secret access for a project launch
Bring one project launch access task into the request flow so the repository is ready for its workflow.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add repo to org secret with selected access
Adds a repository to an existing organization-level github actions secret that is configured for 'selected' repository access.
Why this helps
A launch can be blocked when a new repository has not yet been added to the organization secret's selected access list.
- Starts from an HTTP request to Notis
- Checks the project context before changing secret access
- Reports whether repository access was granted
Setup
Build it in a few focused steps.
- 1Connect BambooHR and GitHub once in the Notis portal.
- 2Create an automation from Automations, New Automation, and enter its prompt.
- 3Describe how to validate the project in BambooHR, identify its repository, and name the existing selected-access Actions secret.
- 4Pick the webhook trigger, choose where run reports go, and save the automation.
- 5Test with one real project launch request and confirm the repository access.
Questions about this workflow
Does this create a new Actions secret?
No. The action adds a repository to an existing organization-level Actions secret configured for selected repository access.
Does BambooHR provide GitHub repository names?
The source description does not guarantee that. Supply a repository lookup rule or include the repository in the request context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bamboohr to GitHub. A trigger fires from one place; an action lands in another.
Bamboohr 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.
Bamboohr 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.