Make failed GitHub checks visible in Clientary
When a check fails, give the investigation a clear home in the client project.
Trigger
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.
Action
Create Task
Tool to create a new task in Clientary. Use when you need to create a task with a title, optionally associating it with a project and assignee.
Why this helps
A failed check can block delivery, but the issue may be overlooked when project follow-up happens outside GitHub.
- Bring code delivery blockers into project tracking
- Create a clear investigation step
- Reduce the chance of a failed check being overlooked
Setup
Build it in a few focused steps.
- 1Connect GitHub and Clientary once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3In one instruction, describe which failed check conclusions should create an investigation task and what details it should include.
- 4Pick GitHub's Check Run Status / Conclusion Changed trigger and choose where run reports should go.
- 5Test with one real failed check and confirm the task gives enough context to investigate.
Questions about this workflow
Will a task be created when a check starts running?
The event includes status and conclusion changes. Tell Notis to create a task only when the check reaches a failure conclusion.
Can it assign the task to a developer?
Ask for an assignee only when the GitHub event or available context identifies a matching Clientary staff member. Provide a reliable identity match if needed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Clientary. A trigger fires from one place; an action lands in another.
GitHub triggers
Clientary actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Client
Tool to create a new client record in Clientary. Use when you need to add a new client to the system with company details and contact information.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Contact
Tool to create a new contact within a specified client. Use when you need to add a contact to a client account with name and email as required fields.
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 Expense
Tool to create a new expense record in Clientary to track expenditures within your account. Use when you need to record expenses, optionally assigning them to specific clients or projects. Requires an amount field.
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 Lead
Tool to create a new lead record in Clientary. Use when you need to add a new lead to the system with company details and contact information.
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 Project
Tool to create a new project in Clientary with name and rate. Use when you need to set up a new project for tracking time, expenses, or managing client work.
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 Task
Tool to create a new task in Clientary. Use when you need to create a task with a title, optionally associating it with a project and assignee.
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.
Delete Client
Tool to remove a client and all associated projects, invoices, estimates, and contacts. Use when you need to permanently delete a client from Clientary. WARNING: Deletions are permanent and not reversible.
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.
Delete Lead
Tool to permanently delete a lead and all associated Estimates and Contacts. Use when you need to remove a lead that is no longer needed. Warning: This action is irreversible.
Connect any two apps with Notis in the middle.
GitHub and Clientary, 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 Clientary.