Connect GitHub to DeployHQ
When something happens in GitHub, Notis takes the next step in DeployHQ. 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 DeployHQ
Turn new PR commits into a deployment overview
When a pull request receives new commits, generate a concise DeployHQ overview of what changed so you can decide whether it is ready to ship.
Abort a deployment after a failed workflow run
When a GitHub Actions workflow run fails, stop the related DeployHQ deployment before it continues consuming time or exposing an incomplete release.
Review DeployHQ history after a GitHub deployment status
When GitHub records a new deployment status, retrieve the relevant DeployHQ deployment history so the latest release state is easy to understand.
Summarize release impact after a PR review
When a pull request review is submitted, generate a DeployHQ overview of the revision range to make approval and release impact easier to assess.
Check the DeployHQ revision for every new pull request
When a pull request is opened, retrieve the latest repository revision from DeployHQ to confirm the deployment connection is pointed at the expected codebase.
Attach deployment history to every workflow run
When a GitHub Actions workflow run is created, retrieve recent DeployHQ deployments for the related project so the run starts with release context.
Fetch commit details when a workflow finishes
When a GitHub workflow run changes conclusion, retrieve detailed DeployHQ repository commit information for the revision involved.
Add a deployment exclusion for a code scanning alert
When a new code scanning alert is created, add a carefully defined DeployHQ excluded-file rule when the alert identifies a generated or non-deployable path.
Exclude exposed secret paths from deployment
When GitHub detects a new secret scanning alert, add a DeployHQ exclusion for the affected path when appropriate and report the action immediately.
Supported Triggers and Actions
Notis builds workflows that link GitHub to DeployHQ. A trigger fires from one place; an action lands in another.
GitHub triggers
DeployHQ 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.
Delete Command
Tool to delete a command from a specified project. Use when you need to remove an SSH command from a project's configuration.
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.
Delete Project
Tool to delete a project from DeployHQ. Use when you need to permanently remove a project by its permalink or identifier.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Build Cache File
Tool to delete an existing build cache file from a project. Use when you need to remove a cached build artifact from the project's build cache storage.
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.
Delete Excluded File Rule
Tool to delete an existing excluded file rule from a project. Use when you need to remove an excluded file pattern from deployment configuration.
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.
Delete Server Group
Tool to delete a server group from a project using the DeployHQ API. Use when you need to remove a server group from deployment configuration.
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.
Delete Template
Tool to delete a template by its unique permalink. Use when you need to permanently remove a template from DeployHQ.
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.
Get Projects
Tool to retrieve all projects from DeployHQ account. Use when you need to list all available projects and their configurations.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Project
Tool to view an existing project in DeployHQ. Use when you need to retrieve details about a specific project by its permalink or identifier.
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 trough 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 DeployHQ
Connect any two apps with Notis in the middle.
Not just GitHub and DeployHQ. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business DeployHQ.