Keep CMS page changes visible with scheduled reviews
Bring page sync results into a concise review so important updates are easier to spot.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Sync Pages
Tool to retrieve all page items in paged format with sync tokens. use when synchronizing local page data after receiving cms change notifications.
Why this helps
Page changes can go unnoticed when checking the sitemap and CMS manually is another task to remember.
- Make page sync activity easier to scan.
- Support a consistent review of paged updates.
- Help teams identify changes that need human follow-up.
Setup
Build it in a few focused steps.
- 1Connect Agility CMS in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to retrieve synced pages and summarize returned changes, noting when prior sync state is needed.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real sync run and check that the report reflects the pages returned.
Questions about this workflow
Does this workflow change or publish pages?
No. The listed Sync Pages action retrieves page items and sync data; it does not edit or publish pages.
Can it compare pages with a previous run?
A comparison requires prior sync state or a saved baseline. If that state is not available to the automation, provide it or treat the report as a summary of the current returned data.
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.