Make New Release Tags Business-Aware
A version tag can tell you what shipped, but Fireberry can show who is waiting for it.
Trigger
New Repository Tag Created
Triggers when a new tag is created in a GitHub repository. Monitors the repository's tags and fires an event for each newly created tag. The payload includes the tag name, the commit SHA and URL it points to, and archive download URLs.
Action
Fireberry: Query Records
Tool to query records with filtering, sorting, and pagination. use when you need to retrieve specific fireberry records by module.
Why this helps
Tagging a release is simple; remembering every customer, deal, and promise connected to that version is not.
- Finds related Fireberry records for a newly tagged version.
- Makes launch follow-up more deliberate.
- Keeps version context accessible without manual CRM searching.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Fireberry to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to query Fireberry whenever a new repository tag is created.
- 3Use a plain-language instruction to search by tag, commit, release, customer promise, or launch context.
- 4Select the new repository tag trigger, choose the run-report channel, and test with one real tag.
Questions about this workflow
Can this monitor only version tags?
Yes. Configure the GitHub trigger for the repository and tag pattern you use for releases.
Will it create a Fireberry record?
No. It queries existing records and reports the relevant context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Fireberry. A trigger fires from one place; an action lands in another.
GitHub triggers
Fireberry actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a new Fireberry record
Tool to create a new record in a specified fireberry table. use when you have the table name and record data ready for insertion.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Picklist Values
Tool to retrieve all possible picklist (dropdown) values for a specific field. use when you need to load all available options for a picklist field in a record type.
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.
Fireberry: Query Records
Tool to query records with filtering, sorting, and pagination. use when you need to retrieve specific fireberry records by module.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Fireberry, 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 Fireberry.