Send Calendly follow-ups to the right GitHub owner
Leave the call with a clear owner. When a booking names a follow-up person and issue, Notis can assign that issue in GitHub.
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
Follow-up work has no clear owner after the meeting, so it sits until someone remembers to assign it.
- Make ownership visible on the issue.
- Reduce post-meeting handoffs.
- Keep follow-up tied to the booking context.
Setup
Build it in a few focused steps.
- 1Connect Calendly and GitHub once in the Notis portal.
- 2Create an automation and provide its name, prompt, report channel, and trigger.
- 3In one instruction, tell Notis to assign the referenced issue to the follow-up owner named in the booking.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with a real booking that names an assignable GitHub user and issue.
Questions about this workflow
What information does the booking need?
It needs to identify the GitHub repository and issue, plus the GitHub username of the person to assign.
What if the user cannot be assigned?
GitHub may reject or ignore the assignment depending on repository access. Review the run report and confirm that the person can be assigned.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Calendly to GitHub. A trigger fires from one place; an action lands in another.
Calendly 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.
Calendly 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.