Assess booking closures with every severe code scanning alert
Notis pairs the alert with the affected resource's existing blackout schedule and reports whether a maintenance window is already protected.
Trigger
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.
Action
Get Resource Blackouts
Tool to fetch blackout periods for a resource. Use when determining unavailable timeslots before booking.
Why this helps
A security alert demands attention, but the operator must separately investigate whether the affected bookable resource has a safe closure window.
- Bring schedule context into incident triage
- Avoid overlapping an emergency closure with existing plans
- Reduce high-pressure tab switching
Setup
Build it in a few focused steps.
- 1Connect GitHub and Planyo Online Booking in Notis.
- 2Create an automation named Security alert resource blackouts.
- 3Enter: "For each new high-severity code scanning alert affecting the booking service, retrieve Planyo blackouts for the relevant resource and report the nearest protected maintenance windows."
- 4Select New Code Scanning Alert Created, choose an incident reporting channel, and test with a safe alert example.
Questions about this workflow
Will a security alert automatically close bookings?
No. This workflow retrieves blackout periods to inform the incident decision; it does not create closures.
Can I restrict it by severity?
Yes. Use the GitHub trigger's severity filter or state the severity threshold in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Planyo Online Booking. A trigger fires from one place; an action lands in another.
GitHub triggers
Planyo Online Booking actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Reservation
Tool to create a new reservation. Use after gathering resource, timing, and customer details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add User
Tool to add a new user in Planyo. Use when you need to create a user account after gathering user details.
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 Add-on List
Tool to retrieve a list of add-ons. Use when you need to inspect or manage add-ons for a specific resource or across the entire site after setting up credentials.
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 Coupon List
Tool to retrieve a list of coupons. Use when you need to fetch all coupons for a specific resource or the entire site (if no resource_id provided).
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 Resource Availability
Tool to check resource availability within a specified date/time range. Use when validating if a resource can be reserved before creating a reservation.
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 Resource Blackouts
Tool to fetch blackout periods for a resource. Use when determining unavailable timeslots before booking.
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 Resource Reviews
Tool to fetch reviews and ratings for a specific resource. Use when you have a resource_id and need to display customer feedback.
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.
Connect any two apps with Notis in the middle.
GitHub and Planyo Online Booking, 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 Planyo Online Booking.