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.
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
Fires when a new GitHub Actions workflow artifact is created in a repository.
Do this · Action
Deletes an SSH command from a project’s configuration.
Examples
Ways Notis can move work from GitHub to DeployHQ
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
TriggerScheduled
Delete Command
Deletes an SSH command from a project’s configuration.
ActionInstant
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
TriggerInstant
Delete Project
Permanently removes a project.
ActionInstant
New Workflow Artifact Created
Fires when a new GitHub Actions workflow artifact is created in a repository.
TriggerPolling
Delete Build Cache File
Deletes a build cache file from a project.
ActionInstant
Branch Changed
Fires when a branch’s commits or protection status or settings change.
TriggerPolling
Delete Excluded File Rule
Deletes an excluded file rule from a project’s deployment configuration.
ActionInstant
New Branch Created
Fires when a new branch is created in a GitHub repository.
TriggerPolling
Delete Server Group
Deletes a server group from a project’s deployment configuration.
ActionInstant
Check Run Status / Conclusion Changed
Fires when a GitHub check run’s status or conclusion changes.
TriggerPolling
Delete Template
Permanently removes a template.
ActionInstant
Check Suite Status / Conclusion Changed
Fires when a GitHub check suite changes status or conclusion for a reference.
TriggerPolling
Get Projects
Lists all projects in your account.
ActionInstant
New Code Scanning Alert Created
Fires when a new code scanning alert is created in a repository.
TriggerPolling
Get Project
Retrieves details about a project.
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.
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 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.
Related pairs
More ways to connect GitHub and DeployHQ
Connect any two apps with Notis in the middle.
GitHub and DeployHQ, 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 DeployHQ.