Language Support Documentation Tracker
Language support changes happen constantly, but documentation gets out of sync. This automation looks up language codes every time you update language support on an issue--keeping your language documentation current and your team aligned.
Trigger
Public Team Issue Properties Updated
Fires when properties on a *public-team* Linear issue change (status, assignee, priority, labels, etc.). For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_PROPERTIES_UPDATED`.
Action
Google Languages
Tool to retrieve google-supported languages. use when you need a list of language codes for localization.
Why this helps
Language support documentation falls out of sync, causing confusion about what's actually supported
- Language documentation automatically updates when status changes
- Team always knows current language support for each feature
- Historical record of language support changes
- Support team has accurate information for customer questions
Setup
Build it in a few focused steps.
- 1Connect Linear and Autom in Notis
- 2Ask Notis: 'When an issue property for language support is updated, look up and record the supported language codes'
- 3Use 'Public Team Issue Properties Updated' as your trigger
- 4Choose your notification channel
- 5Test by updating a language support property and verify language codes are recorded
Questions about this workflow
Does this track language additions and removals?
Yes. Notis records every language change, creating an audit trail of your language support history.
Can I see when a language was added or dropped?
Yes. Each update is timestamped with the exact languages added, removed, or changed.
How do I use this for feature flagging?
Share the language documentation with your feature flag system to enable/disable languages per feature.
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.