Make issue approval the handoff to Planyo
Once the agreed approval event appears on the issue, Notis creates the reservation from its complete scheduling context.
Trigger
New Issue Event
Triggers when a new issue event occurs in a GitHub repository. Covers all issue timeline events such as issues being closed, reopened, assigned, unassigned, labeled, unlabeled, milestoned, demilestoned, renamed, locked, or unlocked. Events can optionally be filtered by type. The payload includes the event type, timestamp, the actor who triggered the event, the affected issue details, and any associated commit references.
Action
Add Reservation
Tool to create a new reservation. Use after gathering resource, timing, and customer details.
Why this helps
An issue can be operationally approved but still wait hours or days for someone to translate that approval into a booking.
- Make the approval signal actionable
- Shorten the path to confirmation
- Avoid relying on someone remembering the handoff
Setup
Build it in a few focused steps.
- 1Connect GitHub and Planyo Online Booking in Notis.
- 2Ask Notis to create an automation named Approved issue booking handoff.
- 3Say: "When the configured approval event occurs on a booking issue with complete resource, time, and customer details, add the reservation in Planyo and report its confirmation."
- 4Choose New Issue Event with the approval event you use, select a reporting channel, and test on one real issue.
Questions about this workflow
Which issue event should I use?
Choose the existing timeline event that reliably means approved in your process, such as a particular label or milestone event.
Can it avoid duplicate bookings?
Include a stable issue reference in the instruction and tell Notis to report rather than recreate an already confirmed request.
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.