Connect GitHub to Gorgias

When something happens in GitHub, Notis takes the next step in Gorgias. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from GitHub to Gorgias

View example

Turn GitHub security alerts into Gorgias tickets

Create a focused Gorgias ticket whenever GitHub detects a new code scanning alert, so security work is captured immediately without interrupting your current task.

View example

Route GitHub secret alerts into Gorgias

Create an urgent Gorgias ticket when GitHub detects a secret scanning alert, helping you respond before a leaked credential becomes a larger incident.

View example

Keep Gorgias current on deployment failures

Update a Gorgias ticket when a GitHub deployment status reports failure or error, giving your team one place to track customer-impacting release issues.

View example

Tag Gorgias tickets after failed GitHub runs

Add a clear tag to a Gorgias ticket when a GitHub Actions workflow run fails, making release-related support work easier to spot and prioritize.

View example

Create a support ticket for important pull requests

Create a Gorgias ticket when a new GitHub pull request matches your chosen workflow, so customer-facing changes get a clear communication and readiness follow-up.

View example

Reflect pull request review feedback in Gorgias

Update the related Gorgias ticket when a GitHub pull request review is submitted, keeping approval and requested-change signals visible to customer operations.

View example

Create Gorgias tickets from new GitHub issues

Create a Gorgias ticket for a new GitHub issue, giving customer-impacting bugs and requests a visible follow-up path without copying details by hand.

View example

Update Gorgias when a GitHub issue gets a comment

Update a related Gorgias ticket when a new GitHub issue comment arrives, so new technical context reaches the person handling customer follow-up.

View example

Sync important GitHub issue changes to Gorgias

Update a Gorgias ticket when a tracked GitHub issue property changes, helping customer-facing work stay aligned with status, ownership, labels, or milestone changes.

Supported Triggers and Actions

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

GitHub triggers

Gorgias actions

New Workflow Artifact Created

Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.

TriggerPolling

Add Ticket Tags

Adds tags to a ticket in gorgias.

ActionInstant

Branch Changed

Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.

TriggerPolling

Create Account Setting

Creates a new account setting in gorgias.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

Create Customer

Creates a new customer in gorgias.

ActionInstant

Check Run Status / Conclusion Changed

Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.

TriggerPolling

Create Team

Creates a new team in gorgias.

ActionInstant

Check Suite Status / Conclusion Changed

Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.

TriggerPolling

Create Ticket

Creates a new ticket in gorgias.

ActionInstant

New Code Scanning Alert Created

Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.

TriggerPolling

Delete Customer

Deletes a specific customer from gorgias.

ActionInstant

New Repository Collaborator Added

Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.

TriggerPolling

Delete Customer Field Value

Deletes a specific field value for a customer in gorgias.

ActionInstant

Commit Event

Triggered when a new commit is pushed to a repository.

TriggerInstant

Delete Customers

Deletes multiple customers from gorgias.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.