Verify Planyo availability after every successful GitHub deployment
Let Notis confirm that the bookable window tied to a release is actually available, then report the result where you already work.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
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.
Why this helps
A deployment can look healthy while the newly promoted service, event, or consultation window is still unavailable in Planyo.
- Catch launch-day scheduling gaps early
- Replace a manual post-deploy checklist item
- Receive one focused readiness report
Setup
Build it in a few focused steps.
- 1Connect GitHub and Planyo Online Booking to Notis once.
- 2Create a new automation in the portal and name it Successful deploy booking readiness.
- 3Use the prompt: "After a successful deployment status, check availability in Planyo for the release resource and launch window, then report any gaps."
- 4Select New Deployment Status Created as the trigger, choose a reporting channel, and test with one real successful deployment.
Questions about this workflow
Can this ignore failed deployments?
Yes. State in the plain-language prompt that Notis should act only when the new deployment status is successful.
Does it create a reservation?
No. This workflow checks availability and reports the result; it does not reserve the slot.
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
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.
Add Reservation
Tool to create a new reservation. Use after gathering resource, timing, and customer details.
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.
Add User
Tool to add a new user in Planyo. Use when you need to create a user account after gathering user details.
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 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.
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 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).
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 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.
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 Resource Blackouts
Tool to fetch blackout periods for a resource. Use when determining unavailable timeslots before booking.
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.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Planyo Online Booking. 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 Planyo Online Booking.