Label GitHub issues from screenshots with Astica AI
Send a screenshot and issue details to Notis. Astica AI extracts the important context, and GitHub gets the labels that help your team triage it.
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
Useful bug evidence arrives as screenshots, leaving someone to interpret it and update the issue by hand.
- Extract visible error text and context from screenshots.
- Suggest labels based on the evidence and issue details.
- Reduce manual triage and context switching.
Setup
Build it in a few focused steps.
- 1Connect Astica AI and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, ask Notis to analyze the submitted screenshot and add appropriate existing or relevant labels to the specified GitHub issue.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real screenshot and issue number.
Questions about this workflow
What should the webhook request include?
Include the screenshot or an accessible image reference, plus the repository and issue number so Notis can identify where the labels belong.
Will it create labels that do not exist?
GitHub's add-label action can create labels that are missing. Ask Notis to prefer your team's existing label conventions when analyzing the screenshot.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Astica ai to GitHub. A trigger fires from one place; an action lands in another.
Astica ai 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.
Astica ai 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.