Turn release preview checks into GitHub follow-up
Send the preview for a quick visual check and keep a discovered problem attached to its existing issue.
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
Preview checks often happen in one place while the GitHub issue needing attention is somewhere else.
- Start a check when a preview is ready, rather than waiting for the next scheduled run.
- Summarize visible problems for the tracking issue.
- Keep release review follow-up connected to the relevant GitHub issue.
Setup
Build it in a few focused steps.
- 1Connect Apiflash and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3In one instruction, describe the incoming preview URL, the existing GitHub issue, and the label to use if the screenshot shows a problem.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real preview URL and review the issue label result.
Questions about this workflow
What starts the check?
An HTTP request to the Notis webhook starts it. Include the preview URL and enough context to identify the existing GitHub issue in your instruction.
Does the automation publish or deploy the preview?
No. Apiflash captures or reviews the supplied page; the GitHub action adds a label to an existing issue.
What if there is no visual problem?
Tell Notis to leave the issue unchanged when the screenshot does not show a problem and report the result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apiflash to GitHub. A trigger fires from one place; an action lands in another.
Apiflash 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.
Apiflash 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.