Bring client context into new issues
New issues are easier to triage when client ownership is clear. Retrieve the client list alongside each issue and include useful matching context in the report.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
Action
Get Clients
Tool to retrieve all clients. use when you need to list all clients on the account.
Why this helps
Issue triage can stall when the client behind a request is not obvious.
- Bring client context into the issue triage report.
- Reduce time spent switching between repositories and client records.
- Highlight missing client references for follow-up.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Bidsketch once in the Notis portal.
- 2Create an automation and ask Notis to retrieve clients and identify any clear match for each new issue.
- 3Pick the New Issue Created trigger for the relevant repository.
- 4Choose where run reports should go, then test with one real issue.
Questions about this workflow
Will this assign or label the issue?
No. The selected action retrieves clients. The workflow can report matching context, but it does not change the GitHub issue.
What if there is no clear client match?
Ask Notis to say that no match is evident and identify what reference is missing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Bidsketch. A trigger fires from one place; an action lands in another.
GitHub triggers
Bidsketch actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Client
Tool to create a client. use when adding a new client record to bidsketch.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Client
Tool to delete a client and all their proposals. use when you want to permanently remove a client and its associated proposals from your account.
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 Fee
Tool to delete a fee. use when a saved fee is no longer needed. use after confirming this fee isn't referenced in any live proposals.
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 Proposal
Tool to delete a proposal and all its content. use after confirming the proposal id to prevent accidental deletions.
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 Proposal Fee
Tool to delete a proposal fee. use when you need to remove an existing fee before finalizing or sending a proposal.
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.
Delete Proposal Section
Tool to delete a proposal section. use when you need to remove a section from a proposal after verifying its id.
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 Section
Tool to delete a section. use when you need to permanently remove a saved section after confirming its id.
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 Webhook
Tool to delete a webhook. use after obtaining the webhook id to remove it.
Connect any two apps with Notis in the middle.
GitHub and Bidsketch, 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 Bidsketch.