Skip to content
Notis

Connect GitHub to Async Interview

When something happens in GitHub, Notis takes the next step in Async Interview. 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

Permanently delete an interview job; this cannot be undone.

Examples

Ways Notis can move work from GitHub to Async Interview

Keep interview jobs aligned with new pull requests

When a pull request is created, update the relevant Async Interview job with the engineering work context so candidate evaluation stays connected to current product needs.

Use submitted code reviews to refresh interview jobs

When a GitHub pull request review is submitted, update the associated Async Interview job with the latest review signal for more informed technical hiring decisions.

Refresh interview role context after meaningful commits

When a commit is pushed to a repository, update the relevant Async Interview job so interview questions and expectations reflect recent engineering changes.

Turn assigned engineering issues into interview preparation

When an issue is assigned to you, update the relevant Async Interview job with the problem context that can shape practical candidate questions.

Update interview roles when new product issues appear

When a new GitHub issue is created, update the relevant Async Interview job with emerging product needs and technical context.

Keep interview jobs aware of repository traction

When a repository gains a stargazer, update the relevant Async Interview job with the traction signal for roles supporting open-source or developer-facing products.

Update interview jobs when a collaborator joins

When a new GitHub collaborator is added, update the relevant Async Interview job with team access context and any resulting onboarding or hiring implications.

Keep interview panel context current when reviewers change

When pull request reviewers change, update the relevant Async Interview job with the latest engineering ownership context for coordinated interviewing.

Refresh interview skills when issue priorities change

When a GitHub issue changes state, labels, assignee, or other properties, update the relevant Async Interview job with the revised skill or priority context.

Supported Triggers and Actions

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

GitHub triggers

Async Interview actions

Recurring trigger

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

TriggerScheduled

Delete Job

Permanently delete an interview job; this cannot be undone.

ActionInstant

Webhook trigger

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

TriggerInstant

List Jobs

Retrieve a list of interview jobs.

ActionInstant

New Workflow Artifact Created

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

TriggerPolling

List Interview Responses

Retrieves interview responses with candidate details.

ActionInstant

Branch Changed

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

TriggerPolling

Update Job

Update an existing interview job.

ActionInstant

New Branch Created

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

TriggerPolling

Check Run Status / Conclusion Changed

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

TriggerPolling

Check Suite Status / Conclusion Changed

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

TriggerPolling

New Code Scanning Alert Created

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

TriggerPolling
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,600+ 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 Async Interview

Connect any two apps with Notis in the middle.

GitHub and Async Interview, or any other combination from 1,600+ 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 Async Interview.