Connect Addresszen to 21risk

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

View example

Check compliance before confirming an address

When an address is submitted, use its site or location details to retrieve relevant 21risk compliance data and report checks that need attention.

View example

Review monthly item patterns by site

On a schedule, retrieve 21risk monthly item facts and summarize notable site and question patterns using the returned data.

View example

Add property context to an address review

When a location review starts, use supplied site details to retrieve matching 21risk property information, including available COPE details.

View example

Keep a scheduled view of audit reports

On a recurring schedule, retrieve 21risk audit reports and summarize their returned status and timing details for a quick review.

View example

Find the 21risk site for an incoming location

When a location request arrives, search the 21risk site directory using supplied details and report likely matching site records.

View example

Review the 21risk organization directory

On a schedule, retrieve organizations from 21risk and summarize the returned directory for a quick administrative review.

View example

Check risk categories for a location review

When a location review begins, retrieve relevant 21risk risk model categories and summarize the available groups for that site context.

View example

Review available 21risk risk models

On a schedule, retrieve the available 21risk risk models and summarize the models returned for planning or audit preparation.

Supported Triggers and Actions

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

Addresszen triggers

21risk actions

Recurring trigger

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

TriggerScheduled

Get Compliance

Retrieves compliance data for sites, categories, and questions.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Items (BETA)

Retrieves items for analytics and reporting.

ActionInstant

Get Items Per Month

Retrieves monthly item data by question and site.

ActionInstant

Get Organizations

Lists organizations.

ActionInstant

Get Properties

Retrieves property details related to sites, including insurance information.

ActionInstant

Get Reports

Retrieves audit reports, including draft, published, and scheduled reports.

ActionInstant

Get RiskModel Categories

Retrieves risk model categories used to group questions and compliance checks.

ActionInstant

Get Risk Models

Lists risk models used for audits and compliance.

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.