Skip to content
Notis

Make ready dubbing work visible in GitHub

A dubbing job finishes. Its GitHub issue gets the label your team uses to mark audio as ready for review.

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

Finished audio can sit unnoticed while the related GitHub issue still looks unchanged.

  • Surface completed dubbing work in the issue queue
  • Reduce manual status updates after a job finishes
  • Keep the issue linked to the CAMB.AI job

Setup

Build it in a few focused steps.

  • 1Connect CAMB.AI and GitHub once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a clear name.
  • 3In one instruction, tell Notis to use the CAMB.AI job completion details to label the related GitHub issue for audio review.
  • 4Choose the notis_webhook trigger and configure CAMB.AI or your calling service to send the job details to it.
  • 5Choose a report channel, then test with one real completed dubbing job and issue.

Questions about this workflow

What starts this automation?

A notis_webhook request starts it. The request needs to include enough CAMB.AI job and GitHub issue context for Notis to identify the issue.

Does this create a new GitHub label?

The GitHub action can add labels and creates labels that do not already exist.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

CAMB.AI 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.

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