Start new Jira projects with a CMS model inventory
A new project can begin with a quick view of the content structures already available in Agility CMS.
Trigger
New Project
Triggered when a new project is added in Jira
Action
Get Content Models
Tool to retrieve content models and page modules. use when you need schema definitions to dynamically build content structures.
Why this helps
Teams starting a project may not know which CMS models or modules already exist and could inform the work.
- Make existing content structures easier to discover.
- Give project kickoff discussions concrete CMS context.
- Avoid duplicate exploration across tools.
Setup
Build it in a few focused steps.
- 1Connect Jira and Agility CMS once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to retrieve CMS content models and page modules and summarize items that may relate to the new project.
- 4Pick the Jira New Project trigger and choose where run reports should go.
- 5Test with one real project creation and review the inventory.
Questions about this workflow
Does this workflow create CMS models?
No. The available action retrieves model and module definitions for review; it does not create or update them.
Can it know the project requirements automatically?
It can use details provided by the Jira project event. Add requirements or naming context to the instruction if the event does not provide enough detail.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Agility cms. A trigger fires from one place; an action lands in another.
Jira 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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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.
New Project
Triggered when a new project is added in Jira
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.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Get Content Models
Tool to retrieve content models and page modules. use when you need schema definitions to dynamically build content structures.
Get Logs
Tool to retrieve sync items (logs) from agility cms. use after initial full sync to fetch updates.
Get Page
Tool to retrieve details of a page, including metadata, content zones, and components. use after you know the page id to fetch.
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.
Jira 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.