Look up rental orders when project issues close
Close the loop between a finished task and the equipment it was tracking.
Trigger
Issue State / Properties Changed
Triggers when a specific GitHub issue changes any of its tracked properties. Monitored properties: state (open/closed), state_reason, title, body, assignees, labels, milestone, lock status, active_lock_reason, comment count, and closed_at timestamp. When a change is detected, the payload includes the full current issue details, the list of changed field names, and their previous values.
Action
Get Order
Tool to retrieve a specific order by id. use when you need complete details of a known order, including optional relationships like customer or coupon. call after confirming the order id.
Why this helps
Completed project work can leave a related rental order lingering unseen.
- Supports a clean project closeout
- Makes known orders easy to revisit
Setup
Build it in a few focused steps.
- 1Connect GitHub and Booqable to Notis once.
- 2Create an instruction to retrieve the related known order when a tracked issue closes.
- 3Choose Issue State / Properties Changed and a reporting channel.
- 4Close one test issue that references an order.
Questions about this workflow
How does Notis know the order?
Include the existing order reference convention in your plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Booqable. A trigger fires from one place; an action lands in another.
GitHub triggers
Booqable actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Customer
Tool to create a new customer. use when onboarding a new client and you have verified their details. example: create 'jane doe' with email jane@doe.com.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Order
Tool to create a new order. use after collecting valid customer id and timing details. example: create an order for customer '297f2584-...' starting at '2018-01-01t09:00:00z'.
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.
Create Product Group
Tool to create a new product group in booqable. use when you have defined the group's name and pricing details and want to organize items under a shared group.
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.
Delete Customer
Tool to delete (archive) a customer by id. use after confirming the customer should be hidden from searches.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Order
Tool to delete (archive) an order by id. use when you need to hide completed or canceled orders from active listings.
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.
Delete Product Group
Tool to delete a product group by id. use when you need to permanently remove a product group from your catalog after confirming its identifier.
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 Customer
Tool to fetch a specific customer by id. use after obtaining a customer identifier to retrieve full customer details.
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 Customers
Tool to retrieve a list of customers. use when you need to paginate through customers.
Connect any two apps with Notis in the middle.
GitHub and Booqable, 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 Booqable.