Translation Scope Calculator
Translation projects get budgeted wrong because scope isn't clear upfront. This automation looks up all language codes the moment you create an internationalization project--giving your team and vendors exact scope for accurate timelines and quotes.
Trigger
Project Created
Fires when a new Linear project is created. Covers projects in both public and private teams — polls with the connected user's token, so visibility matches what the connected user can see in Linear.
Action
Google Languages
Tool to retrieve google-supported languages. use when you need a list of language codes for localization.
Why this helps
Translation budgets blow up because language scope was vague at project start
- Language scope automatically defined when projects are created
- Vendors get clear scope for accurate quotes
- Budget planning based on actual language count
- Fewer scope-change requests and budget overruns
Setup
Build it in a few focused steps.
- 1Connect Linear and Autom to Notis
- 2Ask Notis: 'When an internationalization or i18n project is created, look up the language codes we need to support'
- 3Use 'Project Created' as your trigger
- 4Choose where language scope data is shared
- 5Test by creating an i18n project and verify language list appears
Questions about this workflow
How do I estimate translation cost from this?
Give your vendor the language list. Most charge per-language, so multiply languages by their per-language rate.
Can I update language scope mid-project?
Yes. Ask Notis to recalculate scope anytime and it will show cost impact of adding languages.
Does this account for different content types?
Notis focuses on language codes. You'll add estimates for how much content in each language separately.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Autom. A trigger fires from one place; an action lands in another.
Linear triggers
Autom actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Google Countries
Tool to list google-supported countries. use when you need to filter or suggest countries based on a search string.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Google Images
Tool to fetch images from google search results. use when you need urls, titles, domains, and metadata for images matching a query.
Comment Received Trigger
Triggered when a comment is received.
Google Languages
Tool to retrieve google-supported languages. use when you need a list of language codes for localization.
Issue Created Trigger
Triggered when a new issue is created.
Google Locations
Tool to retrieve google-supported locations. use when searching for locations by name. returns locations ordered by reach (most populous first).
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Autom, 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 Autom.