Keep Apaleo unit groups aligned with reviewed code
A submitted review can be the signal that your inventory change is ready.
Trigger
Pull Request Review Submitted
Triggers when a new review is submitted for a GitHub pull request. Emits an event for each newly submitted review on the monitored pull request, covering all review types: APPROVED, CHANGES_REQUESTED, COMMENTED, and DISMISSED.
Action
Replace a unit group
Use this call to modify a unit group.<br>you must have at least one of these scopes: 'unitgroups.manage, setup.manage'.
Why this helps
Founders lose time checking whether reviewed inventory changes were actually applied in the PMS.
- Close the loop after technical review
- Reduce duplicate configuration work
- Make inventory changes easier to trust
Setup
Build it in a few focused steps.
- 1Connect GitHub and Apaleo to Notis once through the portal.
- 2Create the automation in the portal or ask Notis for it conversationally.
- 3Use this instruction: When a GitHub review approves an inventory configuration change, update the matching Apaleo unit group and report the result.
- 4Select the review-submitted trigger, choose the run-report channel, and test with one approved review.
Questions about this workflow
What if the review requests changes instead?
Tell Notis to act only on approved reviews, so requested changes do not update Apaleo.
Can this handle a renamed unit group?
Yes, if the pull request or repository context clearly identifies the intended Apaleo unit group.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Apaleo. A trigger fires from one place; an action lands in another.
GitHub triggers
Apaleo actions
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.
Archive a property
Use this endpoint to archive an existing live property this operation set the isarchived flag to true<br>you must have at least one of these scopes: 'properties.manage, setup.manage'.
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.
Check if a property exists
Check if a property exists by id.<br>you need to be authorized (no particular scope required)
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Check if a unit attribute exists
Check if a unit attribute exists<br>you must have at least one of these scopes: 'unitattributes.read, setup.read, setup.manage'.
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.
Check if a unit exists
Check if a unit exists by id.<br>you must have at least one of these scopes: 'units.read, setup.read, setup.manage'.
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.
Check if a unit group exists
Check if a unit group exists by id.<br>you must have at least one of these scopes: 'unitgroups.read, setup.read, setup.manage'.
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.
Clones a property
Use this call to clone a specific property. this operation creates a new property with inventory and rate plans from the specified property.<br>you must have at least one of these scopes: 'properties.create, setup.manage'.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Create a unit
Use this call to create a new unit.<br>you must have at least one of these scopes: 'units.create, setup.manage'.
Commit Event
Triggered when a new commit is pushed to a repository.
Create a unit attribute
Use this call to create a new unit attribute.<br>you must have at least one of these scopes: 'unitattributes.create, setup.manage'.
Connect any two apps with Notis in the middle.
Not just GitHub and Apaleo. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Apaleo.