Get Agility CMS route context on request
Ask for a route lookup and get the relevant sitemap view without manually browsing the CMS.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Sitemap Flat
Tool to retrieve the flat sitemap as a mapping of page paths to sitemap items. use when you need page routing logic after knowing locale and channel.
Why this helps
Finding the right page path can interrupt focused work when a request needs a quick routing answer.
- Make route lookups available on demand.
- Reduce manual sitemap browsing.
- Return page path context for the requested locale and channel.
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 use the request's locale and channel to retrieve the flat sitemap and summarize the relevant paths.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real request that includes a locale and channel.
Questions about this workflow
Can the webhook look up a page by any field?
The sitemap action returns a flat mapping of page paths to sitemap items. Ask for route context based on the locale and channel supplied in the request.
Does the lookup create or change routes?
No. Get Sitemap Flat retrieves routing information for review.
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.