Find Crowdin reports while preparing a localization retrospective
As the retrospective takes shape in Notion, quickly surface which Crowdin reports are available for review.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
List Reports
Tool to list reports for a given crowdin project. use after confirming project id to retrieve available reports. supports pagination via limit and offset.
Why this helps
Preparing a retrospective becomes harder when nobody knows which localization reports are available.
- Make retrospective preparation more focused.
- Reduce time spent hunting for available evidence.
- Connect project review notes with Crowdin reporting options.
Setup
Build it in a few focused steps.
- 1Connect Notion and Crowdin once in the portal.
- 2Create an automation or ask Notis to list available Crowdin reports when a localization retrospective page is updated.
- 3Describe how to identify the project and where to report the available reports in one plain-language instruction.
- 4Select the Notion Page Content Updated trigger for the retrospective page and choose a reporting channel.
- 5Test with one real retrospective update and check the reported Crowdin reports.
Questions about this workflow
Does this generate a report?
No. It lists reports available for the project.
Can the automation summarize a report too?
Describe the desired next step in the prompt and ensure the necessary report data is available.
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.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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'.
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.
Create Crowdin Project
Tool to create a new project in crowdin. use before uploading source files to initialize translation workflows.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Add Webhook
Tool to create a new webhook in a crowdin project. use after confirming the project id and desired event triggers.
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.
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.
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.
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.
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.
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.
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.