Keep a record of your coding sessions
When you push commits to GitHub, Notis logs them on your calendar so you have a timestamped record of when you were coding and what you worked on.
Trigger
Commit Event
Triggered when a new commit is pushed to a repository.
Action
Quick Add Event
Parses natural language text to quickly create a basic google calendar event with its title, date, and time, suitable for simple scheduling; does not support direct attendee addition or recurring events, and `calendar id` must be valid if not 'primary'.
Why this helps
You code, commit, move on. There's no record of when you had focus or what you accomplished. When someone asks how much time you spent on a feature, you guess. You can't easily tell clients or managers what you shipped. Your productivity feels invisible.
- Build a visible record of when you're focused and coding versus in meetings or Slack
- Show your work output to stakeholders with timestamped commit logs on your calendar
- Reflect on your productivity by reviewing what you committed and when
Setup
Build it in a few focused steps.
- 1Connect GitHub and Google Calendar to Notis
- 2Ask Notis: 'When I push commits, add them to my calendar' or set it up in Automations
- 3Specify which repositories to track or track all of them
- 4Choose your notification channel (usually just for you, not your team)
- 5Push a test commit and confirm it appears as a calendar entry
Questions about this workflow
Will this create an event for every commit?
Yes, or you can filter to group commits by day or hour to avoid calendar clutter.
Can I see the commit message and changed files?
Yes. Notis includes the commit message and a link to see diffs.
Is this for personal accountability or to share with my team?
Primarily personal accountability, but you can share your calendar if you want transparency on when you're actively coding.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Google Calendar. A trigger fires from one place; an action lands in another.
GitHub triggers
Google Calendar actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Insert Calendar into List
Inserts an existing calendar into the user's calendar list.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Update Calendar List Entry
Updates an existing entry on the user\'s calendar list.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Calendar
Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Update Calendar
Updates metadata for a calendar.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Clear Calendar
Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Create Event
Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Delete event
Deletes a specified event by `event id` from a google calendar (`calendar id`); this action is idempotent and raises a 404 error if the event is not found.
Commit Event
Triggered when a new commit is pushed to a repository.
Create a calendar
Creates a new, empty google calendar with the specified title (summary).
Connect any two apps with Notis in the middle.
Not just GitHub and Google Calendar. Any combination from 985+ 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 Google Calendar.