Turn Calendarhero meeting outcomes into GitHub labels
Finish a meeting with a clearer GitHub queue, without manually sorting every decision afterward.
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
Meeting decisions disappear into notes, leaving founders to reconstruct priorities later.
- Makes meeting priorities visible in GitHub
- Reduces post-meeting sorting
- Creates a shared language for follow-up
- Helps prevent decisions from being forgotten
Setup
Build it in a few focused steps.
- 1Connect Calendarhero and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it in plain language.
- 3Use this instruction: When a Calendarhero meeting summary arrives, identify the related GitHub issue and add labels for its outcome, priority, and next step.
- 4Choose an incoming webhook trigger and a channel for run reports, then test with one real meeting summary.
Questions about this workflow
What does the webhook contain?
Your connected Calendarhero workflow or backend sends the meeting context and summary to Notis.
Can Notis choose labels from the discussion?
Yes. The plain-language instruction tells Notis to interpret the summary and apply useful GitHub labels.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Calendarhero to GitHub. A trigger fires from one place; an action lands in another.
Calendarhero triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Calendarhero and GitHub. Any 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.