Connect 21risk to DeployHQ

When something happens in 21risk, 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

Build an automation Browse examples

Examples

Ways Notis can move work from 21risk to DeployHQ

View example

Collect deployment evidence for a 21risk audit

When an audit evidence request arrives, fetch the DeployHQ deployment history for the named project so you can review recent releases alongside the audit.

View example

Review upcoming deployments for compliance readiness

On a recurring schedule, retrieve upcoming DeployHQ deployments so you can review their timing and server details as part of compliance planning.

View example

Roll out approved compliance configuration changes

When an approved configuration-only rollout is requested, deploy the project's config files to the specified server or server group without deploying code changes.

View example

Refresh your deployment target inventory

On a recurring schedule, retrieve the server groups configured for a DeployHQ project to support a current view of deployment targets during compliance reviews.

View example

Summarize repository changes for a compliance review

When a review request names a project and revision range, generate an AI deployment overview of the commits between those references for the compliance reviewer.

Supported Triggers and Actions

Notis builds workflows that link 21risk to DeployHQ. A trigger fires from one place; an action lands in another.

21risk triggers

DeployHQ actions

Recurring trigger

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

TriggerScheduled

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.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete Project

Tool to delete a project from DeployHQ. Use when you need to permanently remove a project by its permalink or identifier.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Delete Template

Tool to delete a template by its unique permalink. Use when you need to permanently remove a template from DeployHQ.

ActionInstant

Get Projects

Tool to retrieve all projects from DeployHQ account. Use when you need to list all available projects and their configurations.

ActionInstant

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.

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 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.

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

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

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.