Add holiday context to README change follow-up
When project instructions change, downstream work may need planning. Notis can retrieve Clockify holidays for your specified period and report them with the README change.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
Get Holidays In Period
Tool to retrieve holidays in a specific period. use when you need holidays assigned to a user between two dates after confirming the workspace id.
Why this helps
Small documentation changes can create follow-up work, and availability checks add another step before planning it.
- Include holiday context in documentation change follow-up.
- Plan related work with fewer separate lookups.
- Keep the date range explicit in your instruction.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Clockify once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis which date period and Clockify workspace to check for holidays when the README changes.
- 4Pick the GitHub Repository README Changed trigger and choose a report channel.
- 5Test with one real README change and review the run report.
Questions about this workflow
Does the action determine holidays automatically for any dates?
It retrieves holidays in a specific period. Include the date range and workspace context in your instruction.
Does it know whether a README change affects the schedule?
No. Notis can summarize the README change, but whether it changes a plan depends on context you provide.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Clockify. A trigger fires from one place; an action lands in another.
GitHub triggers
Clockify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Client
Tool to add a new client to a workspace. use when you need to create a client in a specific workspace.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Webhook
Tool to create a new webhook in a workspace. use when you want to subscribe to workspace events by registering a callback url.
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.
Delete Client
Tool to delete a client from a workspace. use after archiving the client and confirming no associated data exists.
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.
Delete Webhook
Tool to delete a webhook from a workspace. use when you need to remove an existing webhook by its id.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Filter Workspace Users
Tool to filter users in a workspace by advanced criteria. use when you need a paginated, sortable list of workspace users matching multiple filters.
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.
Find All Users On Workspace
Tool to list all users in a workspace. use when you need to retrieve workspace members after confirming the workspace id. example: "find all users on workspace 64a687e29ae1f428e7ebe303."
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.
Find User's Team Managers
Tool to get managers of a user in a workspace. use after confirming workspace and user ids are correct.
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.
Generate New Webhook Token
Tool to generate a new webhook token. use after confirming workspace and webhook ids.
Connect any two apps with Notis in the middle.
GitHub and Clockify, 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 Clockify.