Keep task ownership aligned across Breeze and GitHub
A change of owner in Breeze can show up on the linked GitHub issue without a second round of manual updates.
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
When task ownership changes in one tool but not the other, work can sit without a clear next owner.
- Keep issue ownership current
- Make handoffs visible to code reviewers
- Spend less time checking who owns the next step
Setup
Build it in a few focused steps.
- 1Connect Breeze and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3In one instruction, tell Notis to update the linked GitHub issue assignee when the Breeze task owner changes, using the owner's GitHub username.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real Breeze task owner update and a linked GitHub issue.
Questions about this workflow
Does a Breeze username always match a GitHub username?
No. Provide the matching GitHub username in the task details or request, or include a clear identity rule in your instruction.
What if the issue cannot be assigned to that person?
GitHub may ignore assignment changes when the account lacks repository access. Check the run report and repository permissions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Breeze to GitHub. A trigger fires from one place; an action lands in another.
Breeze 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.
Breeze 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.