Create Chaser invoices after successful production deployments
Capture completed billable milestones while the delivery evidence is fresh.
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 Invoice
Tool to create a new invoice record in the organization. use after ensuring the customer exists in chaser.
Why this helps
Founders often remember to ship but not to invoice the milestone they just delivered.
- Makes delivery-to-invoice handoff automatic
- Keeps cash-flow tasks visible
Setup
Build it in a few focused steps.
- 1Connect GitHub and Chaser to Notis once.
- 2Create a new automation from the portal or ask Notis conversationally.
- 3Describe that a successful production deployment for a billable client should create its Chaser invoice.
- 4Choose New Deployment Status Created and select the channel for reports.
- 5Test with a real non-sensitive production deployment status.
Questions about this workflow
Can the prompt limit this to billable clients?
Yes. State which repositories, environments, or client conventions count as billable.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Chaser. A trigger fires from one place; an action lands in another.
GitHub triggers
Chaser 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 Invoice
Tool to create a new invoice record in the organization. use after ensuring the customer exists in chaser.
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.
Get Credit Notes
Tool to retrieve a list of credit notes. use after authenticating this detail.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Customer by ID
Tool to retrieve details for a specific customer by their external (source system) id. use after obtaining the external id when you need specific customer information.
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.
Get Customers
Tool to retrieve a list of all customers associated with the organization. use when you need to display or process complete customer contact and status information.
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.
Get Organization
Tool to retrieve information about the connected organizations. use when you need organization ids, currency, timezone, or legal details before other operations.
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 Credit Note
Tool to create a new credit note record in the organization. use after confirming invoice adjustments.
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 Customer
Tool to create a new customer record in chaser. use after obtaining basic auth credentials.
Commit Event
Triggered when a new commit is pushed to a repository.
Update Customer
Tool to update an existing customer's information using their unique externalid. use after confirming the customer's externalid. e.g., "update contactemailaddress for externalid cust abc123."
Connect any two apps with Notis in the middle.
Not just GitHub and Chaser. 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 Chaser.