Connect Accredible certificates to 21risk

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

View example

Check compliance after a credential milestone

Use an Accredible webhook to start a focused 21risk compliance lookup when a certificate or badge milestone is reached.

View example

Review monthly item trends alongside credential activity

Run a scheduled 21risk monthly item query to review question and site data as part of a credential program check-in.

View example

Find audit reports for a credential review

Start a 21risk audit report lookup from a credential related webhook and send the matching report list to your run channel.

View example

Keep an organization list ready for credential reviews

Schedule a 21risk organization lookup so credential program reviews start with an up to date list to inspect.

View example

Pull property insurance details for a credential review

Use a webhook to retrieve 21risk property details related to sites when a credential review needs insurance context.

View example

Refresh risk categories for credential review planning

Schedule a 21risk category lookup to give credential review planning a current reference for compliance checks.

View example

Look up risk models when a credential review starts

Start a 21risk risk model lookup from a webhook so reviewers can see available models as a credential review begins.

View example

Prepare a site directory for credential reviews

Schedule a filtered or paged 21risk site lookup to make location review easier during credential program check-ins.

Supported Triggers and Actions

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

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