Keep deployment history understandable
When deployment details shift, Fibery preserves the current context so you can understand what changed without reconstructing it later.
Trigger
GitHub Deployment State Changed
Triggers when a specific GitHub deployment's fields change. Monitors the following aspects of a single deployment: - ``environment`` -- the target environment name - ``original_environment`` -- the original environment name before normalization - ``description`` -- the human-readable deployment description - ``task`` -- the deployment task name - ``sha`` -- the commit SHA being deployed - ``ref`` -- the branch, tag, or SHA reference being deployed - ``updated_at`` -- the last-updated timestamp - ``transient_environment`` -- whether the environment is temporary - ``production_environment`` -- whether this is a production deployment When any of these fields change, an event is emitted containing the full current deployment details and a list of which fields changed.
Action
Update Entity
Tool to update an existing Fibery entity. Uses Commands API: fibery.entity/update.
Why this helps
Deployment metadata changes can make release history confusing during incident review or planning.
- Preserve deployment context
- Improve release traceability
- Reduce reconstruction work
Setup
Build it in a few focused steps.
- 1Connect GitHub and Fibery to Notis once through the portal.
- 2Create an automation or ask Notis to update the matching Fibery release record with changed deployment fields and a concise history note.
- 3Pick the GitHub Deployment State Changed trigger and select a reporting channel.
- 4Test it by changing a deployment description or environment in a safe workflow.
Questions about this workflow
What deployment fields are tracked?
Environment, commit SHA, ref, task, description, timestamps, and environment flags are included.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Fibery. A trigger fires from one place; an action lands in another.
GitHub triggers
Fibery actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Custom App Endpoint
Tool to delete a specific custom app endpoint. Use after confirming the app and endpoint IDs to remove.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Entity
Tool to delete a specific Fibery entity by its ID. Use when you have verified the entity exists and have its GUID. Deletion is irreversible.
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 File
Tool to delete a specific file. Use when you need to remove a file from Fibery by its ID.
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.
Execute GraphQL Query
Tool to execute GraphQL queries or mutations against a Fibery space. Use when you need to fetch or modify Fibery data via the GraphQL API.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Authenticate (validate token via API call)
Tool to validate existing Fibery personal API token by performing a real API call. If the call succeeds, returns the token value extracted from the Authorization header. Use the returned token in the `Authorization: Token <value>` header for further calls.
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 App Information
Tool to retrieve application information. Use when you need the version, name, description, authentication methods, and available data sources before further operations.
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 Custom App Endpoints
Tool to list custom app endpoints. Use when you need the available custom endpoints for a given app before invoking them.
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 Custom Apps
Tool to list all custom apps in the Fibery workspace. Use when you need the identifiers of all custom apps.
Connect any two apps with Notis in the middle.
GitHub and Fibery, 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 Fibery.