Connect 21risk to Dotsimple

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

View example

Check Social Accounts for a Compliance Issue

When a 21risk issue is sent to a Notis webhook, list connected Dotsimple accounts so you can see which channels may need review.

View example

Review Social Metrics Alongside Compliance Tasks

On a recurring schedule, list Dotsimple account reports to give your compliance review a view of available social metrics.

View example

Find Posts to Review After a Compliance Flag

Start from a webhook carrying a compliance concern and list Dotsimple posts for a human to identify relevant content.

View example

Prepare a Scheduled Content Review

On a recurring schedule, list Dotsimple posts and include the inventory in a review report for your compliance routine.

View example

Check Available Tags for a Compliance Review

When a webhook starts a review, list Dotsimple tags so the team can see existing labels before organizing content.

View example

Review Content Tags on a Schedule

List Dotsimple tags on a recurring schedule and surface the inventory for a person to review for duplicates or outdated labels.

View example

Gather Media Files for a Compliance Check

Start from a webhook with a compliance concern and list Dotsimple media files to help reviewers locate relevant assets.

View example

Keep a Current View of the Media Library

On a recurring schedule, list Dotsimple media files for a human check of the assets available to support compliant publishing.

View example

Inspect a Media File Referenced in a Compliance Request

Send a compliance request with a Dotsimple media file ID to the webhook and retrieve that file's metadata for review.

Supported Triggers and Actions

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

21risk triggers

Dotsimple actions

Recurring trigger

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

TriggerScheduled

Create Tag

Tool to create a new tag in dotsimple. use when you need to categorize content with custom tags. example: create a tag named "news" with color "#38bdf8".

ActionInstant

Webhook trigger

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

TriggerInstant

Delete Media Files

Tool to delete multiple media files in the workspace. use after confirming unwanted files. call this when you have a list of media ids to remove. returns success status.

ActionInstant

Delete Tag

Tool to delete a tag by its uuid. use when you need to remove a specific tag; ensure the uuid is correct before invoking.

ActionInstant

Get Media File

Tool to retrieve details of a specific media file. use when you have the mediafileid and need its metadata.

ActionInstant

Get Tag by UUID

Tool to retrieve details for a specific tag by uuid. use when you need full tag information after obtaining its identifier.

ActionInstant

List Accounts

Tool to list all connected social media accounts in the workspace. use when you need to retrieve available accounts before posting or scheduling content.

ActionInstant

List Autoresponders

Tool to list all autoresponders. use when you need to browse through your autoresponder setup.

ActionInstant

List Media Files

Tool to list all media files with optional pagination. use when you need to retrieve or browse uploaded media files page by page.

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.