Keep appointment no-shows visible for follow-up
Make a recorded no-show visible on its existing GitHub issue so the next step does not depend on memory.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Missed appointments can go unnoticed in the place where your team tracks customer follow-up.
- Bring recorded no-shows into existing issue triage.
- Use a consistent label for follow-up review.
- Avoid repeatedly checking appointment records by hand.
Setup
Build it in a few focused steps.
- 1Connect Appointo and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis to review Appointo for recorded no-shows, match only the GitHub issues identified by the information you provide, and add the agreed follow-up label.
- 4Choose the notis_cron trigger and select where run reports go.
- 5Test with one real recorded no-show and verify the matching issue and label.
Questions about this workflow
Can it determine a no-show if Appointo does not record that status?
No. The appointment data must include a no-show status or another explicit indicator for Notis to evaluate.
Will it make a new issue for a no-show?
No. This workflow labels an existing issue. Provide a reliable issue reference or matching rule.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Appointo to GitHub. A trigger fires from one place; an action lands in another.
Appointo triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Appointo and GitHub, 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 GitHub.