Connect 21risk to Aryn
When something happens in 21risk, Notis takes the next step in Aryn. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from 21risk to Aryn
Create an Aryn docset for every 21risk audit evidence intake
When a 21risk audit package arrives by webhook, create an Aryn docset to hold its evidence for review.
Open an Aryn DocSet for urgent compliance reviews
Create a separate Aryn DocSet when a 21risk compliance review needs focused document analysis.
Generate a monthly Aryn plan for control analysis
On a schedule, generate an Aryn query plan for reviewing recurring 21risk control evidence before execution.
Draft an Aryn query plan for a new audit gap
When a 21risk audit gap is reported, generate an Aryn plan for investigating the supporting documents.
Review weekly Aryn DocSet metadata for compliance archives
Check metadata and usage statistics for an Aryn DocSet used to store 21risk compliance archives.
Check Aryn DocSet status after a 21risk incident
Retrieve Aryn metadata for the DocSet linked to a 21risk incident so the team can confirm its current state.
Retrieve a specific control evidence document
When 21risk sends a document reference, retrieve the matching Aryn document for focused review.
Retrieve binary evidence for a 21risk incident
Fetch the binary content of an Aryn document when a 21risk incident payload identifies the file.
Review outstanding Aryn tasks before weekly compliance planning
List outstanding Aryn asynchronous tasks on a schedule and summarize what needs attention for 21risk work.
Supported Triggers and Actions
Notis builds workflows that link 21risk to Aryn. A trigger fires from one place; an action lands in another.
21risk triggers
Aryn actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create DocSet
Tool to create a new docset. use when you need to allocate a storage container before adding documents.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create DocSet
Tool to create a new docset. use when you need to allocate a storage container before adding documents.
Delete DocSet
Tool to delete a docset and all its documents. use after confirming the docset id, when you need to permanently remove a docset and its contents.
Generate plan
Tool to generate a query plan without executing it. use when you need to review the logical plan before running your query (e.g., "generate a plan for revenue breakdown by region").
Get DocSet Metadata
Tool to retrieve metadata for a specific docset. use when you have the docset id and optionally need usage statistics.
Get Document by ID
Tool to retrieve a document by id. use after both docset and document ids are available.
Get Document Binary
Tool to retrieve the binary content of a document by docset id and document id.
List Async Tasks
Tool to list all outstanding asynchronous tasks for the account. use when you need to check pending or running tasks.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect 21risk and Aryn
Connect any two apps with Notis in the middle.
21risk and Aryn, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Aryn.