Turn Cal booking intake into a labeled GitHub issue
Keep booking follow-up close to the work: send a Cal intake webhook to Notis and label the related GitHub issue.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Booking details can get separated from the GitHub issue that needs follow-up, leaving requests harder to spot.
- Make booking-related work easier to scan in GitHub.
- Reduce manual context switching between Cal and issue triage.
- Use labels that already exist or let GitHub create supplied labels.
Setup
Build it in a few focused steps.
- 1Connect Cal and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Describe how to review the webhook details and add appropriate labels to the related GitHub issue.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real Cal webhook and confirm the intended issue was labeled.
Questions about this workflow
Does Cal provide a trigger event for this workflow?
No. Start it with a Notis webhook, which runs when an HTTP request reaches the webhook.
Will Notis create a new GitHub issue?
No. This workflow uses the GitHub action to add labels to an issue. The prompt should identify the intended existing issue from the supplied details.
What if the required label does not exist?
The GitHub action description says labels that do not already exist are created.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cal to GitHub. A trigger fires from one place; an action lands in another.
Cal 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.
Cal 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.