Connect 21risk to Doppler

When something happens in 21risk, Notis takes the next step in Doppler. 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 Doppler

View example

Review Doppler changes during a 21risk audit

Use a 21risk audit request to collect Doppler config change history for the relevant project and environment.

View example

Keep a scheduled inventory of Doppler configs

On a schedule, list Doppler configs for selected projects and summarize the environments available for compliance tracking.

View example

Prepare a secret-name inventory for a 21risk review

Use a webhook request to list Doppler secret names for a specified config without retrieving their values.

View example

Surface recent Doppler changes for recurring review

Regularly retrieve config change history for specified Doppler configs and summarize entries that deserve compliance follow-up.

View example

Check Doppler environments for a 21risk project review

When a review request arrives, list the environments in its specified Doppler project and summarize the scope for the reviewer.

View example

Add Doppler change request status to a 21risk review

For a compliance review request, retrieve Doppler workplace change requests and summarize their current statuses for follow-up.

View example

Include Doppler integrations in a recurring control review

On a schedule, list configured Doppler integrations and summarize the inventory for a recurring 21risk control review.

View example

Find Doppler projects named in a 21risk request

Use a review request to list Doppler workspace projects and help identify the project relevant to the audit.

View example

Prepare Doppler workplace roles for access review

On a schedule, list Doppler workplace roles and summarize available roles as input to a 21risk access review.

Supported Triggers and Actions

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

21risk triggers

Doppler actions

Recurring trigger

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

TriggerScheduled

Get Authenticated User Info

Tool to retrieve information about the authenticated user or token. Use when you need to verify authentication status or get details about the current token's workplace and permissions.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Config Log

Tool to retrieve a specific config log from Doppler. Use when you need to view details about a particular configuration change or event.

ActionInstant

List Config Logs

Tool to retrieve configuration change logs for a specific config in a project. Use when you need to view the history of configuration changes, track who made changes, or identify rollback actions.

ActionInstant

Get Config

Tool to retrieve a specific Doppler config by project and config name. Use when you need to get configuration details for a specific project environment.

ActionInstant

List Doppler Configs

Tool to list configurations from a Doppler project. Use when you need to retrieve all configs or filter by environment. Supports pagination for large result sets.

ActionInstant

Create Encrypted Share Link

Tool to generate a Doppler Share link by sending an encrypted secret. Use when you need to securely share secrets with end-to-end encryption. The receive flow is end-to-end encrypted where the encrypted secret will be decrypted on the recipient's browser.

ActionInstant

Create Plain Text Share Link

Tool to generate a Doppler Share link by sending a plain text secret. Use when you need to securely share secrets with expiration controls. The secret is not stored in plain text by Doppler; the receive flow is end-to-end encrypted where the encrypted secret is decrypted in the browser.

ActionInstant

List Environments

Tool to list all environments in a Doppler project. Use when you need to retrieve the environments available in a specific 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 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.