Set GitHub team project permissions from a synced calendar event
As plans firm up, the teams working a project change, and their project access rarely keeps pace. When Notis syncs the full details of your planning event, it sets the team's permission on the linked GitHub project, so access reflects the plan instead of trailing behind it.
Trigger
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).
Action
Add or update team project permissions
Grants or updates a team's permissions ('read', 'write', or 'admin') for a specific project, which must exist within the specified organization and be linked to it.
Why this helps
Team access to a project drifts out of sync with planning, so people either lack the access they need or keep access they should not have.
- Team project access follows the plan as it changes.
- Uses the full synced event details, not just a bare notification.
- Keeps permissions accurate without manual audits.
Setup
Build it in a few focused steps.
- 1Connect Google Calendar and GitHub to Notis once in the portal.
- 2Tell Notis: When my planning event syncs, set the working team's permission on the linked GitHub project.
- 3Select the Google Calendar event sync trigger, which returns full event data.
- 4Choose a channel where Notis confirms the permission change.
- 5Test with a real planning event and verify the project permission.
Questions about this workflow
Why use event sync instead of the webhook trigger?
Event sync returns full event data including details and attendees, which the webhook trigger does not.
Which permissions can it set?
You choose read, write, or admin in your prompt and Notis applies it.
Does the project need to be linked to the org?
Yes. The project must exist within and be linked to the organization.
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.