Connect Agility cms to Crowdin

When something happens in Agility cms, 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 Agility cms to Crowdin

View example

Prepare Published Agility Content for Crowdin

When a publish request reaches Notis, retrieve the specified Agility CMS content and upload its source file to Crowdin storage for localization.

View example

Add an Agility Source File to Crowdin

On a Notis webhook request, retrieve the specified Agility CMS source file and add it to the selected Crowdin project, branch, or directory.

View example

Create a Crowdin Branch for an Agility Release

When a release request arrives by webhook, use its supplied release context to create a Crowdin branch that isolates translation work.

View example

Refresh Crowdin Source Files on a Schedule

On a recurring schedule, check for Agility CMS content that meets your instruction and add the resulting source files to a Crowdin project.

View example

Start a Crowdin Project from a Localization Request

Use a Notis webhook request to create a Crowdin project when a new Agility CMS initiative needs its own localization project.

View example

Build Crowdin Translations for Agility Content

On a recurring schedule, review the Agility CMS localization work described in your instruction and start a Crowdin project translation build.

View example

Machine Translate Agility Content in Crowdin

When a translation request reaches Notis, use Crowdin machine translation for the specified strings and languages.

View example

Add Agility Terminology to Crowdin Glossary

Turn a terminology request tied to Agility CMS content into a Crowdin glossary term for consistent localization.

View example

Organize Localization Files in Crowdin Directories

On a recurring schedule, review the Agility CMS content organization you specify and create the needed Crowdin directories for localization files.

Supported Triggers and Actions

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

Agility cms triggers

Crowdin actions

Recurring trigger

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

TriggerScheduled

Add Branch

Creates a project branch to separate translations.

ActionInstant

Webhook trigger

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

TriggerInstant

Add File

Adds an uploaded file to a project.

ActionInstant

Add Directory

Create a directory in a project.

ActionInstant

Add Label

Creates a project label.

ActionInstant

Create Crowdin Project

Creates a project to start a translation workflow.

ActionInstant

Add Glossary Term

Add a term to a glossary for consistent translations.

ActionInstant

Add Webhook

Creates a project webhook to send event notifications.

ActionInstant

Assign Label to Strings

Assigns a label to source strings in a project.

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.