Track GitHub deployment time in Harvest
Make release-day work visible without pausing to open a timesheet.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
Create Time Entry
Tool to create a new time entry. use when logging hours for a project by specifying start/end times or duration.
Why this helps
Deployment support is fragmented across small tasks and easily undercounted.
- Capture operational effort promptly
- Improve project profitability signals
Setup
Build it in a few focused steps.
- 1Connect GitHub and Harvest to Notis once.
- 2Start a new automation from Automations in the portal.
- 3Describe that deployment status activity should create a Harvest support-time entry.
- 4Select the deployment status trigger and a reporting channel.
- 5Test against one real deployment.
Questions about this workflow
Can this run for a particular environment?
Describe the environment outcome in the prompt and select the GitHub trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Harvest. A trigger fires from one place; an action lands in another.
GitHub triggers
Harvest 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.
Create Client
Tool to create a new client. use after gathering client details to register a new client in harvest.
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.
Create Client Contact
Tool to create a new client contact. use when you need to add a contact under an existing client. call after you've retrieved or confirmed the client 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.
Create Estimate
Tool to create a new estimate. use after gathering client and line item details.
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.
Create Estimate Item Category
Tool to create a new estimate item category in harvest. use after deciding to categorize line items within an estimate.
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.
Create Estimate Message
Tool to create a new message for an estimate. use when you have an estimate id and want to send a message or run an event (send, accept, decline, re-open) on the estimate.
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 Expense
Tool to create a new expense entry. use when recording costs against projects. ensure either units or total cost is provided.
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.
Create Invoice
Tool to create a new invoice. use when you have gathered all invoice details and need to bill a client in harvest.
Commit Event
Triggered when a new commit is pushed to a repository.
Create Invoice Item Category
Tool to create a new invoice item category. use after you have decided on the category name to register it in harvest.
Connect any two apps with Notis in the middle.
Not just GitHub and Harvest. 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 Harvest.