Grant GitHub Actions Secret Access When Deals Reach Milestones
When a deal progresses to a critical stage, your deployment infrastructure should automatically gain the secrets it needs. Notis grants repository access to GitHub Actions secrets on your schedule.
Trigger
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
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
You manually grant secret access when a deal closes or reaches implementation. Missing a step means deployment credentials aren't available when engineers need them.
- Repositories automatically gain credentials when deals advance
- No manual secret management tied to deal stages
- Reduces access gaps that delay deployments
- Keeps secrets granted only to repos that need them at that stage
Setup
Build it in a few focused steps.
- 1Connect Hubspot and GitHub to Notis.
- 2Ask Notis: 'When a deal reaches [stage name], grant [repository] access to the [secret name] secret.'
- 3Select Deal Stage Updated as your trigger.
- 4Choose your alert channel.
- 5Test by advancing a deal and confirming the repository gains access in GitHub Actions settings.
Questions about this workflow
Can I automate this for multiple secrets?
Yes. You can specify multiple secrets per stage, or different secrets for different deal stages.
What if a deal goes backward in stages?
By default, access is not revoked. You can tell Notis to revoke access if a deal goes back to an earlier stage, or to leave access intact.
Does this work with organization-level secrets?
Yes, fully supported. Organization secrets can be granted to selected repositories based on deal stages.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Hubspot to GitHub. A trigger fires from one place; an action lands in another.
Hubspot triggers
GitHub actions
Contact Created Trigger
Contact Created Trigger
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
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 Hubspot and GitHub. Any combination from 985+ 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.