Use reliable checks to pace supporter reviews
When a full validation suite finishes, it is a natural moment to look beyond the code.
Trigger
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.
Action
Get Transactions
Tool to retrieve a list of transactions associated with your account. use when you need to list all donations and payments, optionally filtered by scope.
Why this helps
Founders either check fundraising too often or forget it entirely during technical validation.
- Creates predictable review points
- Reduces unnecessary interruptions
- Connects validation progress with supporter awareness
Setup
Build it in a few focused steps.
- 1Connect GitHub and Givebutter to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in plain language.
- 3Tell Notis to retrieve Givebutter transactions when a monitored GitHub check suite reaches a meaningful conclusion and summarize the result.
- 4Select the check suite status trigger, choose a reporting channel, and test with one completed check suite.
Questions about this workflow
Can only successful suites trigger the review?
Yes. State that Notis should act only when the suite conclusion is successful.
Can the report include the branch or ref?
Yes. Ask Notis to include the monitored ref and check conclusion.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Givebutter. A trigger fires from one place; an action lands in another.
GitHub triggers
Givebutter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive Contact
Tool to archive a contact by their id. use after ensuring the contact has no associated data (e.g., no transactions or communications). example: "archive contact abc123".
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Campaign
Tool to create a new campaign. use when you have title, description, goal, and type ready, after confirming your givebutter account is authenticated.
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 Webhook
Tool to create a new webhook subscription. use when you need to receive real-time notifications programmatically after confirming your endpoint can validate givebutter's signing secret.
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 Campaign
Tool to delete a campaign by its id. use after confirming the campaign has no funds raised. example: "delete campaign abc123".
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 Contact
Tool to delete a contact by their id. use after confirming the contact has no associated data (e.g., no transactions or communications). example: "delete contact abc123".
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 Fund
Tool to delete a fund by its id. use when you need to remove a fund after confirming it exists. example: "delete fund fund abc123".
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 Webhook
Tool to delete a webhook by its id. use when you need to remove an obsolete webhook after confirming no further events are needed. example: "delete webhook abc123".
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.
Get Fund
Tool to retrieve details of a specific fund by its id. use after confirming the fund id is valid.
Connect any two apps with Notis in the middle.
GitHub and Givebutter, 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 Givebutter.