Share CI variables with approved repositories
Make project setup dependable while keeping shared configuration intentional.
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 variable
Grants a repository access to an organization-level github actions variable, if that variable's visibility is set to 'selected repositories'.
Why this helps
Small teams repeatedly pause to grant repository access to common CI configuration.
- Removes repeated admin work
- Accelerates CI setup
- Preserves deliberate access boundaries
Setup
Build it in a few focused steps.
- 1Connect Docparser and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to build it conversationally.
- 3Use one instruction: when a parsed project approval names a repository, grant it access to the specified selected organization Actions variable.
- 4Choose the incoming webhook trigger, select the reporting channel, and test with one approved project request.
Questions about this workflow
Is this for secret values?
No. This workflow grants access to an organization-level Actions variable, not a secret.
Can the workflow support multiple projects?
Yes. Describe the approval and repository rules in the single automation instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Docparser to GitHub. A trigger fires from one place; an action lands in another.
Docparser 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 Docparser and GitHub. Any 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.