Skip to content
Notis

Turn Notion release plans into Crowdin branches

A new release plan can kick off localization in Crowdin as soon as it lands in Notion.

Trigger

New Page

Triggers when a new page is added to a Notion database.

Action

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.

Why this helps

Release localization gets delayed while someone remembers to create the matching Crowdin branch.

  • Start a localization branch as part of the release planning flow.
  • Reduce the chance that translation setup gets forgotten.
  • Keep release names recognizable across planning and localization.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Crowdin to Notis once through the portal.
  • 2Create an automation in the portal or ask Notis conversationally to create Crowdin branches for new Notion release pages.
  • 3Write one plain-language instruction describing how the release page should guide branch creation.
  • 4Select the Notion New Page trigger and choose a channel for run reports.
  • 5Test with one real release page and confirm the branch appears in Crowdin.

Questions about this workflow

Does this create a branch for every new page?

The prompt can tell Notis to act only on pages that represent releases; describe the condition in plain language.

Do I need to connect both tools again for each release?

No. Connect Notion and Crowdin once, then reuse them across automations.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Notion 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

All Page Events

Triggers when any Notion page is created or updated across the workspace.

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 Created

Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.

TriggerInstant

Create Crowdin Project

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

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Add Webhook

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

ActionInstant

Database Created

Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.

TriggerInstant

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

Data Source Created

Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.

TriggerInstant

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

Data Source Schema Updated

Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.

TriggerInstant

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

Connect any two apps with Notis in the middle.

Notion and Crowdin, 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 Crowdin.