Skip to content
Notis

Carry handoff details into GitHub ownership

Send handoff context to Notis and explain how it should translate into GitHub assignee changes.

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 handoff can happen in one place while the issue owner stays unchanged in GitHub, leaving the next person unsure who is responsible.

  • Start the handoff workflow from an HTTP request.
  • Keep issue ownership in step with the handoff context.
  • Make responsibility changes visible in GitHub.

Setup

Build it in a few focused steps.

  • 1Connect Celigo and GitHub once in the Notis portal.
  • 2Create an automation in Automations, then New Automation, and give it a name.
  • 3Describe how the handoff should add or remove issue assignees in one instruction.
  • 4Choose a webhook trigger and where run reports should go.
  • 5Test with one real example and confirm the report.

Questions about this workflow

What if the handoff request does not identify the issue?

Include enough issue context in the request or your instruction for Notis to identify the intended issue.

Can a handoff remove the previous owner?

Yes. The action supports adding or removing assignees. Explain who to remove and who to add in the handoff rule.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Celigo to GitHub. A trigger fires from one place; an action lands in another.

Celigo triggers

GitHub actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Connect any two apps with Notis in the middle.

Celigo 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.