Create Zylvie products after successful GitHub deployments
Package a release only after the deployment has succeeded, so your launch work follows a real milestone.
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 Product
Tool to create a new product. use when you need to add a product with detailed custom options in zylvie platform.
Why this helps
Starting product work too early can create cleanup when a deployment does not make it through.
- Uses success as a calm, trustworthy trigger
- Avoids premature launch work
Setup
Build it in a few focused steps.
- 1Connect GitHub and Zylvie to Notis once.
- 2Create an automation in the portal or request it in plain language.
- 3Describe that a successful deployment status should create the matching Zylvie product.
- 4Pick New Deployment Status Created, select a report channel, and test after a successful deployment.
Questions about this workflow
Will failed deployments create products?
Tell Notis to act only on successful statuses in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Zylvie. A trigger fires from one place; an action lands in another.
GitHub triggers
Zylvie actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Product
Tool to create a new product. use when you need to add a product with detailed custom options in zylvie platform.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Authenticating User
Tool to retrieve information about the currently authenticated user. use when you have a valid bearer token and need to fetch the authenticated user's profile.
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.
Unsubscribe Webhook
Tool to unsubscribe from a webhook by deleting the workflow object associated with the specified webhook url. use after confirming the webhook url to remove.
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 Zylvie, 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 Zylvie.