Add GitHub issue assignees when a sprint planning event is created
Nothing kills momentum like unowned tickets. When a sprint planning event appears on your calendar, Notis assigns the GitHub issues in scope to the people who own them, so the team walks into planning with clear responsibility already in place.
Trigger
Event Created
Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info.
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
Issues sit unassigned until someone remembers to divvy them up, which leaves work in limbo and forces awkward mid-meeting reshuffling.
- Every issue has an owner before planning starts, so no ticket falls through.
- Removes the manual step of assigning tickets one at a time.
- The team walks in knowing exactly what is theirs.
Setup
Build it in a few focused steps.
- 1Connect Google Calendar and GitHub to Notis once in the portal.
- 2Tell Notis in plain language what you want, for example: When a sprint planning event is created, add the sprint owners as assignees on the issues in scope.
- 3Select the Google Calendar event created trigger.
- 4Choose the channel where Notis should report each run.
- 5Create a test sprint event and confirm the assignees are added.
Questions about this workflow
Does this fire on every new calendar event?
It fires on newly created events, and your plain-language prompt tells Notis which ones matter, such as sprint planning.
What if the assignee lacks access?
GitHub silently ignores assignee changes when the person does not have push access, so Notis reports the run either way.
Can I change the owners later?
Yes. Edit the automation prompt at any time to reflect new ownership.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Calendar to GitHub. A trigger fires from one place; an action lands in another.
Google Calendar triggers
GitHub actions
Attendee Response Changed
Polling trigger that fires when any attendee's RSVP changes to accepted, declined, or tentative. Returns attendee info and current status.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Event Canceled or Deleted
Triggers when a Google Calendar event is cancelled or deleted. Returns minimal data: event_id, summary (if available), and cancellation timestamp.
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.
Event Starting Soon
Triggers when a calendar event is within a configured number of minutes from starting. Returns event details, time remaining, attendees, and join links when available.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Calendar Event Changes
**SOON TO BE DEPRECATED** - Use Calendar Event Sync (polling trigger) instead. Real-time webhook trigger for calendar event changes. Returns event metadata only. For full event data, use Calendar Event Sync (polling trigger).
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Event Created
Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info.
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.
Calendar Event Sync
Polling trigger that returns full event data including details, attendees, and metadata. For real-time notifications with basic info, use Calendar Event Changes (webhook).
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.
Event Updated
Triggers when an existing Google Calendar event is modified. Returns the event ID, change type, and the specific fields that changed with their previous and new values.
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 Google Calendar and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.