Tags Stay in Sync Across Linear and Your CMS
Every time an issue updates, your content tags are fetched and aligned, so tags mean the same thing everywhere in your system.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Get Tags
Tool to get all tags. use when you need to list every tag in a given locale.
Why this helps
You tag issues in Linear but your CMS tags are different, creating confusion. You end up with duplicate tag names and can't search or filter correctly.
- One consistent tag vocabulary across Linear and CMS
- No more searching for tags by different names
- Better filtering and reporting accuracy
Setup
Build it in a few focused steps.
- 1Connect Linear and Agility CMS to Notis once in the portal.
- 2Create an automation called 'Issue Updates Sync Tags' with the instruction: 'When an issue is updated in Linear, fetch all tags from Agility CMS and align them with the issue.'
- 3Select 'Issue Updated' as your trigger and choose your notification channel.
- 4Test by updating an issue and verifying that CMS tags are fetched.
Questions about this workflow
Will this automatically apply tags to the issue?
No, it retrieves and aligns the tags so you can see which CMS tags are relevant. You control the final tagging.
What if Linear and CMS tags have overlapping names?
Notis will intelligently match and consolidate tags by meaning. You can review and refine the mapping as needed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Agility cms. A trigger fires from one place; an action lands in another.
Linear triggers
Agility cms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Authors
Tool to retrieve all authors from an agility cms instance. use when you need the full list of authors for display or processing.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Categories
Tool to get all categories. use when you need to list every category in a given locale.
Comment Received Trigger
Triggered when a comment is received.
Get Content Item
Tool to fetch details of a content item by content id. use when you need item fields and metadata from agility cms.
Issue Created Trigger
Triggered when a new issue is created.
Get Content List
Tool to retrieve a list of content items by reference name. use when you need to fetch and page through content list data with optional filtering, sorting, and link expansions.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get Content Models
Tool to retrieve content models and page modules. use when you need schema definitions to dynamically build content structures.
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).
Get Logs
Tool to retrieve sync items (logs) from agility cms. use after initial full sync to fetch updates.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Get Page
Tool to retrieve details of a page, including metadata, content zones, and components. use after you know the page id to fetch.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Get Page Modules
Tool to retrieve all page modules defined in the agility instance. use when you need only modular definitions without content models.
Connect any two apps with Notis in the middle.
Linear and Agility cms, 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 Agility cms.