Connect 21risk to Crowdin

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

View example

Start a Crowdin project for a new compliance audit

Turn a new 21risk audit request into a ready Crowdin project for translating compliance materials.

View example

Create a Crowdin branch for an audit release

Open a separate Crowdin branch when a 21risk compliance release needs its own translation track.

View example

Create a Crowdin label for compliance content

Create a reusable label in Crowdin when a 21risk request identifies a compliance content category.

View example

Upload a compliance source file to Crowdin storage

Send a compliance source file from a webhook request to Crowdin storage so it can be used in a later file-add step.

View example

Add an approved compliance file to Crowdin

Place an already uploaded compliance file into the specified Crowdin project when a 21risk request marks it ready.

View example

Review Crowdin projects for compliance localization

Run a scheduled Crowdin project inventory to keep the list of compliance localization projects current.

View example

Review compliance localization files on a schedule

Retrieve Crowdin project files on a schedule to make compliance source file reviews easier to keep up with.

View example

Check Crowdin reports for compliance projects

Retrieve available Crowdin reports on a recurring schedule to support regular review of compliance localization activity.

Supported Triggers and Actions

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

21risk triggers

Crowdin actions

Recurring trigger

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

TriggerScheduled

Add Branch

Tool to create a new branch in a crowdin project. use when you need to isolate translations for a new feature or release.

ActionInstant

Webhook trigger

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

TriggerInstant

Add File

Tool to add a new file to a crowdin project. use after uploading the file to storage to place it under the specified project, branch, or directory.

ActionInstant

Add Label

Tool to create a new label in a crowdin project. use when you need to tag resources with a custom identifier, such as 'sprint-5'.

ActionInstant

Create Crowdin Project

Tool to create a new project in crowdin. use before uploading source files to initialize translation workflows.

ActionInstant

Add Webhook

Tool to create a new webhook in a crowdin project. use after confirming the project id and desired event triggers.

ActionInstant

Assign Label to Strings

Tool to assign the specified label to provided string ids in a project. use after creating the label or verifying string ids to categorize content.

ActionInstant

Delete Branch

Tool to delete a specific branch from a crowdin project. use when you need to remove an obsolete branch after it's fully merged.

ActionInstant

Delete Label

Tool to delete the label identified by the specified label id in a project. use when you need to remove outdated or incorrect labels. ensure no resources reference the label before deletion.

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.