Give background removal work a named owner
Put a responsible person on background removal work while the request is fresh.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
A clear image request can still stall if nobody is assigned to carry it forward.
- Makes issue ownership explicit at intake
- Cuts down on manual follow-up after requests arrive
- Supports adding or removing assignees as needed
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 relevant background removal issue and assign the specified GitHub user or owner defined by your rule.
- 4Choose a webhook trigger and choose where run reports should go.
- 5Test with one real request and confirm the correct issue has the intended assignee.
Questions about this workflow
Can I change the assignee later?
The GitHub action can add or remove assignees. Describe the desired result in the instruction.
What if GitHub ignores the assignment?
The action may silently ignore changes if the authenticated user lacks push access to the repository.
Does the issue need to be identifiable?
Yes. This action operates on a GitHub issue, so supply enough context for Notis to identify the relevant issue.
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.