Notice supporter response to shipped work
A successful launch is a useful checkpoint for understanding whether supporter energy moved too.
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
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 ship, switch tasks, and forget to check whether supporters responded.
- Creates a natural review moment
- Reduces manual dashboard checking
- Helps connect delivery to fundraising signals
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 and summarize Givebutter transactions after a successful GitHub deployment status is created.
- 4Pick the deployment status trigger, choose a reporting channel, and test with one successful deployment.
Questions about this workflow
Does the workflow alter supporter records?
No. It retrieves Givebutter transaction information for a focused review.
Can the report mention the deployed environment?
Yes. Ask Notis to include the deployment environment and project context in the report.
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
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.
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".
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 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 Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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 Campaign
Tool to delete a campaign by its id. use after confirming the campaign has no funds raised. example: "delete campaign 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 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".
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 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".
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.
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".
Commit Event
Triggered when a new commit is pushed to a repository.
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.
Not just GitHub and Givebutter. 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 Givebutter.