Add CMS Tag Context to New Issue Comments
Keep the CMS tag vocabulary close when a new comment clarifies a tagging problem.
Trigger
New GitHub Issue Comment
Triggers when a new comment is added to a specific GitHub issue. Only genuinely new comments are emitted; edits to existing comments do not produce duplicate events. The payload includes the comment ID, text body, author details, timestamps, and direct links to the comment on GitHub.
Action
Get Tags
Tool to get all tags. use when you need to list every tag in a given locale.
Why this helps
A useful issue comment can get lost in the thread while someone separately searches for the CMS tag vocabulary.
- Retrieve tag reference data during comment triage.
- Help maintainers interpret tagging and discovery reports.
- Keep investigation context close to the issue conversation.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Agility CMS once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language from any channel.
- 3In one instruction, ask Notis to retrieve tags when a new comment concerns content tagging or discovery.
- 4Pick the New GitHub Issue Comment trigger for GitHub.
- 5Choose a report channel, then test with one real issue comment.
Questions about this workflow
Can it identify tag changes from a comment?
It retrieves the current tag list for the requested locale. It does not provide a tag history or a change baseline.
Can it add or remove tags?
No. Get Tags is a read action and does not modify CMS data.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Agility cms. A trigger fires from one place; an action lands in another.
GitHub 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 Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
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.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Content Models
Tool to retrieve content models and page modules. use when you need schema definitions to dynamically build content structures.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Get Logs
Tool to retrieve sync items (logs) from agility cms. use after initial full sync to fetch updates.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Get Page
Tool to retrieve details of a page, including metadata, content zones, and components. use after you know the page id to fetch.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
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.
GitHub 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.