Turn Apify security findings into labeled GitHub issues
Send an Apify security-monitoring result to Notis and keep the matching GitHub issue organized with useful labels.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Security findings can land in a long issue queue without clear labels, making follow-up easy to miss.
- Make new security findings easier to scan in the issue queue.
- Apply labels that match the finding and repository context.
- Reduce manual triage after a data collection run.
Setup
Build it in a few focused steps.
- 1Connect Apify and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to review the incoming Apify finding, identify its matching GitHub issue, and add suitable labels; include repository and issue details in the request.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real Apify finding and confirm the intended issue receives the labels.
Questions about this workflow
Does Apify trigger this workflow directly?
Apify has no trigger event here. Send its result to a Notis webhook to start the workflow.
Can the workflow create labels?
The GitHub action adds labels to an issue, and its description says labels that do not already exist are created.
What does Notis need to find the issue?
Provide enough context in the incoming result, such as the repository and issue number or a reliable issue reference.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apify to GitHub. A trigger fires from one place; an action lands in another.
Apify 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.
Apify 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.