Give canceled appointment follow-up a clear owner
Make sure a canceled meeting with tracked follow-up work has someone responsible for the next step.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
When a customer cancels, related follow-up can remain unowned while everyone assumes someone else will handle it.
- Assign ownership when a cancellation needs attention.
- Keep follow-up attached to its existing GitHub issue.
- Avoid guessing when the issue or owner is unclear.
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 handle cancellation requests only when they specify a matching existing GitHub issue and authorized assignee, then assign that user to the issue.
- 4Choose the notis_webhook trigger and select where run reports go.
- 5Test with one real cancellation handoff and verify the issue assignment.
Questions about this workflow
Does every cancellation need an issue assignment?
No. Specify which cancellations need follow-up and include the relevant issue and owner in the request.
What happens if the issue or assignee cannot be identified?
The automation prompt should direct Notis to leave the issue unchanged and report the missing information.
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.