Carry approved collaborator onboarding into Planyo
Notis recognizes the new collaborator signal, checks for the required onboarding context, and creates the Planyo user only when it is safe to do so.
Trigger
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.
Action
Add User
Tool to add a new user in Planyo. Use when you need to create a user account after gathering user details.
Why this helps
A collaborator gets repository access, but their booking account becomes a separate onboarding task that is easy to miss.
- Reduce split onboarding checklists
- Create accounts only with complete details
- Report a clear success or missing-information outcome
Setup
Build it in a few focused steps.
- 1Connect GitHub and Planyo Online Booking to Notis once.
- 2Create an automation named Approved collaborator booking user.
- 3Write: "When an approved collaborator is added with the required onboarding details available, add that person as a Planyo user; otherwise report what is missing."
- 4Select New Repository Collaborator Added, choose the onboarding report channel, and test with one approved test collaborator.
Questions about this workflow
Is a GitHub username enough to create a Planyo user?
Not necessarily. Tell Notis which user details must be present and to stop safely when they are missing.
Can I restrict this to certain repository roles?
Yes. Include the permitted collaborator roles in the plain-language 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.