Keep color correction requests easy to find
Route color correction requests into a labeled GitHub issue that stands out from other image work.
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
Color correction requests can blend into broader image tasks, making the specific change harder to track.
- Highlights color correction work in the issue backlog
- Uses the request context to choose relevant labels
- Helps separate a specific enhancement need from general image tasks
Setup
Build it in a few focused steps.
- 1Connect Claid AI and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to find the GitHub issue for each color correction request and add concise labels that make the requested change clear.
- 4Choose a webhook trigger and choose where run reports should go.
- 5Test with one real color correction request and confirm its issue is labeled appropriately.
Questions about this workflow
Will labels be created if they do not exist?
Yes. The GitHub action adds labels to an issue and creates labels that do not already exist.
Can this handle general image requests too?
Describe the specific color correction request and the labeling outcome in the instruction. A separate automation can address materially different request types.
Does the workflow require a field mapping?
No. Describe the desired result in plain language.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Claid ai to GitHub. A trigger fires from one place; an action lands in another.
Claid 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.
Claid 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.