Connect GitHub to Appdrag
When something happens in GitHub, Notis takes the next step in Appdrag. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from GitHub to Appdrag
Send New PR Commits to Appdrag Build Intake
Post each newly pushed pull request commit to an Appdrag backend function for build tracking.
Update Appdrag Review Status After a GitHub Review
Use submitted GitHub pull request reviews to update a matching record through an Appdrag Visual SQL UPDATE function.
Look Up Appdrag Records for a New PR Commit
Use each newly added pull request commit to query Appdrag records related to the commit or its work item.
Send New GitHub Issues to Appdrag Triage
Pass newly created repository issues to an Appdrag POST function for your existing triage process.
Keep an Appdrag PR Record Current
Update an Appdrag database row when a GitHub pull request opens, closes, or is synchronized.
Send GitHub Check Suite Results to Appdrag
Forward check suite state and conclusion changes to an Appdrag function for build result handling.
Route GitHub Code Scanning Alerts to Appdrag
Send newly created code scanning alerts to an Appdrag backend function for security response intake.
Send Secret Scanning Alerts to Appdrag
Forward detected GitHub secret scanning alerts to an Appdrag function for your response workflow.
Look Up Appdrag Context When a Workflow Run Changes
Query Appdrag records when a GitHub Actions workflow run changes status or conclusion, then summarize relevant context.
Supported Triggers and Actions
Notis builds workflows that link GitHub to Appdrag. A trigger fires from one place; an action lands in another.
GitHub triggers
Appdrag actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Execute Cloud Backend function via DELETE
Tool to execute a Cloud Backend API function via DELETE on the default environment. Use when you need to call a function with DELETE parameters and optional APIKey.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute Preprod Function (DELETE)
Tool to execute the pre-production version of a Cloud Backend API function via DELETE. Use when you need to test or validate delete operations in the preprod environment before production deployment.
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.
Execute PROD API Function (GET)
Tool to execute a production Cloud Backend API function via GET. Includes robust URL handling and fallbacks to accommodate management base URLs.
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.
Execute Dev Function (PATCH)
Tool to execute the development version of a Cloud Backend API function via PATCH. Use after deploying or updating your function to the dev environment.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Execute Cloud Backend function via POST
Tool to execute a Cloud Backend API function via POST on the default environment. Use when you need to call a function with POST parameters and optional APIKey.
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.
Execute Function POST (Preprod Env)
Tool to execute a Cloud Backend API function via POST on the preprod environment. Use when you need to test a function in the preprod environment before releasing to production. Include apiKey if your function requires APIKey security.
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.
Execute Cloud Backend function via PUT (default)
Tool to execute a Cloud Backend API function via PUT on the default environment. Use when you need to call a function with PUT parameters and optional APIKey.
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.
Execute Cloud Backend function via PUT (preprod)
Tool to execute a Cloud Backend API function via PUT on the preprod environment. Use when you need to call a function with PUT parameters and optional APIKey in preprod.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything 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.
More ways to connect GitHub and Appdrag
Connect any two apps with Notis in the middle.
GitHub and Appdrag, 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 Appdrag.