Grant GitHub secret access after Findymail partner approval
Make approved integration access a deliberate next step instead of a buried request.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add selected repository to an organization secret
Adds a repository to an organization secret's access list when the secret's visibility is 'selected'; this operation is idempotent.
Why this helps
A partner repository needs a shared secret but the request is lost among outreach threads.
- Keeps secret access approval-based
- Reduces manual admin follow-up
Setup
Build it in a few focused steps.
- 1Connect Findymail and GitHub to Notis once.
- 2Create an automation in the portal.
- 3Write one instruction to add an approved partner repository to the selected organization secret after a webhook.
- 4Select an incoming webhook and reporting channel.
- 5Test with a non-sensitive test secret.
Questions about this workflow
Can this expose the secret in Notis?
No. Describe only the approved secret and repository access outcome; keep secret values in GitHub.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Findymail to GitHub. A trigger fires from one place; an action lands in another.
Findymail 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.
Findymail 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.