Keep content work moving with scheduled CMS context
Give open content-related issues the context they need for the next decision, without another manual status chase.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Create an issue comment
Adds a comment to an existing issue.
Why this helps
Open issues stall when the latest content context stays in the CMS and nobody remembers to bring it back to the discussion.
- Bring relevant CMS context into an existing issue discussion.
- Reduce manual follow-up on open content work.
- Use a recurring check-in instead of relying on memory.
Setup
Build it in a few focused steps.
- 1Connect Agility CMS and Bitbucket once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for content issue follow-up.
- 3In one instruction, ask Notis to identify the open Bitbucket issues to follow up on and comment with relevant Agility CMS context available to it.
- 4Choose a recurring schedule, set the report channel, and confirm the schedule and timezone.
- 5Test with one real issue and relevant CMS context.
Questions about this workflow
Can the workflow find every stale issue automatically?
Only if the selected Bitbucket action context provides enough issue information to identify them. Specify any additional selection criteria or baseline in the prompt.
What if Notis cannot access the latest CMS context?
The workflow can only use returned data. Supply the relevant context in the request or prompt when it is not available to Notis.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agility cms to Bitbucket. A trigger fires from one place; an action lands in another.
Agility cms triggers
Bitbucket actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a branch
Creates a branch in a repository.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Approve Pull Request
Approves a pull request as the authenticated user.
Create an issue
Creates an issue in a repository.
Browse repository path
Retrieves a file or browses directory contents at a repository revision.
Create an issue comment
Adds a comment to an existing issue.
Create a pull request
Creates a pull request in a repository.
Create repository
Creates a Git repository in a workspace.
Create snippet comment
Posts a comment or threaded reply on a snippet.
Connect any two apps with Notis in the middle.
Agility cms and Bitbucket, 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 Bitbucket.