Link GitHub repositories to organization secrets from email
Keep deployment approvals from turning into another task to chase.
Trigger
New Email Received
Trigger for new emails in an AgentMail inbox
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 repository is ready for automation, but its approved secret access is not completed.
- Moves approved automation forward
- Reduces configuration handoffs
Setup
Build it in a few focused steps.
- 1Connect Agent Mail and GitHub to Notis once.
- 2Create a new portal automation.
- 3Write an instruction to link the approved repository to the named organization secret when the authorization email arrives.
- 4Choose New Email Received, pick a private report channel, and test with a selected-access secret.
Questions about this workflow
Why use this instead of broad secret visibility?
It supports granting access to a specific approved repository while keeping the secret scoped.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agent mail to GitHub. A trigger fires from one place; an action lands in another.
Agent mail 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.
New Email Received
Trigger for new emails in an AgentMail inbox
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.
Agent mail 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.