Connect Box to Crowdin

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

View example

Stage new Box files for Crowdin localization

When a source file lands in a Box folder, send it to Crowdin storage so it is ready to add to a localization project.

View example

Stage updated Box source versions

When a Box file gets a new version, stage the updated source in Crowdin storage for localization review.

View example

Create a Crowdin branch for a Box release drop

When a new item appears in a Box release folder, create a Crowdin branch to isolate localization work for that release.

View example

Create a Crowdin label from Box review comments

When a new comment is added to a monitored Box file, create a Crowdin label for the review topic so it can be organized in the project.

View example

Keep Crowdin file details aligned with Box changes

When a monitored Box file's properties change, update the corresponding Crowdin file details with the relevant new information.

View example

Create a Crowdin label when Box folder collaboration starts

When a new collaborator is added to a Box folder, create a Crowdin label to mark localization work that needs partner review.

View example

Register a Crowdin webhook from a localization handoff request

When a localization handoff request reaches a Notis webhook, create the requested webhook in the specified Crowdin project.

View example

Get a scheduled Crowdin localization report check

On a schedule, list available reports for a Crowdin project so localization status checks do not depend on remembering to look.

Supported Triggers and Actions

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

Box 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

Collaboration Details Changed

Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.

TriggerPolling

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

Comment Changed

Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.

TriggerPolling

Create Crowdin Project

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

ActionInstant

New File Comment Added

Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.

TriggerPolling

Add Webhook

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

ActionInstant

File Metadata Changed

Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.

TriggerPolling

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

File Shared Link Changed

Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.

TriggerPolling

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

New File Version Uploaded

Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.

TriggerPolling

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.