Skip to content
Notis

Connect GitHub to Borneo

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

When this happens · Trigger

Fires when a new GitHub Actions workflow artifact is created in a repository.

Do this · Action

Retrieves the status, results, and details of a scan iteration.

Examples

Ways Notis can move work from GitHub to Borneo

View example

Schedule a Borneo scan from a GitHub request

GitHub issue context starts a Borneo cloud-resource scan after the user supplies the account, scope, inspection policy, and schedule.

View example

Check a Borneo scan iteration from GitHub

Turn a GitHub issue into a focused Borneo scan-status check using a supplied scan-iteration reference.

View example

Triage Borneo inspection results from a GitHub issue

Use a GitHub issue to request filtered Borneo inspection results for a supplied scan or scope.

View example

Export Borneo scan evidence for a GitHub issue

Create a focused Borneo insight export from a GitHub request, using a supplied scan ID and explicit filters.

View example

Export Borneo sensitive leaf resources for a GitHub issue

Use a GitHub issue to export leaf-resource exposure details from Borneo, including returned info types or column details when requested.

View example

Review Borneo inventory changes for a GitHub pull request

Use a GitHub PR as change context for a Borneo top-level inventory export with violation and exception counts.

View example

Verify Borneo cloud-account context for a GitHub pull request

Attach a supplied Borneo cloud-account lookup to a GitHub PR so reviewers see the account status relevant to the change.

View example

Reconcile Borneo assets against a GitHub pull request

Use a PR as context for a filtered Borneo asset-registry check against an explicitly supplied expected asset list.

View example

Register an approved Borneo asset from a GitHub issue

Create a Borneo asset when a GitHub issue contains an explicit, authorized creation request and all required asset details.

Supported Triggers and Actions

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

GitHub triggers

Borneo actions

Recurring trigger

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

TriggerScheduled

Access scan iteration by id

Retrieves the status, results, and details of a scan iteration.

ActionInstant

Webhook trigger

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

TriggerInstant

Add discovered recipients

Adds previously discovered recipients to the confirmed recipient list.

ActionInstant

New Workflow Artifact Created

Fires when a new GitHub Actions workflow artifact is created in a repository.

TriggerPolling

Archive discovered recipient

Archives a discovered recipient and their information.

ActionInstant

Branch Changed

Fires when a branch’s commits or protection status or settings change.

TriggerPolling

Delete data breach by id

Irreversibly deletes a data breach evaluation record.

ActionInstant

New Branch Created

Fires when a new branch is created in a GitHub repository.

TriggerPolling

Create and schedule cloud resource scan

Creates and schedules a scan of cloud resources.

ActionInstant

Check Run Status / Conclusion Changed

Fires when a GitHub check run’s status or conclusion changes.

TriggerPolling

Create dashboard user

Creates a dashboard user account with assigned access.

ActionInstant

Check Suite Status / Conclusion Changed

Fires when a GitHub check suite changes status or conclusion for a reference.

TriggerPolling

Create department with translations

Creates a department with translated information.

ActionInstant

New Code Scanning Alert Created

Fires when a new code scanning alert is created in a repository.

TriggerPolling

Create domain with polling frequency

Creates a domain with an automatic polling frequency.

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 schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ 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

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13
Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit
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.

Notis

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.

  • Full run history with inputs, outputs and traces
  • Replay any run with edited inputs
  • Approval inbox, confirm via chat in one tap
  • Audit logs for compliance teams

Automations

Inbox

All12Manager5Telegram1Messages0WhatsApp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything in the box.

Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.

AI in the middle

Every step can include an LLM call: summarise, classify, extract, rewrite.

Full observability

Every run, every step, every input, all replay-able from Mission Control.

Human in the loop

Pause for approval. Notis pings you in chat with one-tap approve.

Self-healing

When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.

Related pairs

More ways to connect GitHub and Borneo

Connect any two apps with Notis in the middle.

GitHub and Borneo, or any other combination from 1,500+ 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 Borneo.