Give carbon purchase follow-ups a clear GitHub owner
Send an order update with the related issue and owner, and Notis can assign that issue for follow-up.
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 carbon purchase may need action, but without a named owner the follow-up can stall between tools.
- Makes ownership visible on the related issue
- Cuts manual handoff after an order update
- Keeps follow-up attached to the existing work item
Setup
Build it in a few focused steps.
- 1Connect Cdr platform and GitHub once in the Notis portal.
- 2In Automations, choose New Automation and give it a name and prompt.
- 3Tell Notis to use each incoming order update to assign its related GitHub issue to the owner named in the request.
- 4Pick the webhook trigger, choose a report channel, and test with one real update, issue, and assignable GitHub username.
Questions about this workflow
What information should the webhook request include?
Include the order update, the related GitHub issue number, and the GitHub username to assign.
Will assignment always succeed?
GitHub may silently ignore assignment changes if the authenticated user lacks push access to the repository. Use a repository where that account has the required access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cdr platform to GitHub. A trigger fires from one place; an action lands in another.
Cdr platform 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.
Cdr platform 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.