Turn successful deployments into Curated drafts
When something ships, give it a place in your next update.
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 Draft Issue
Tool to create a draft issue for a publication. use after confirming the publication id. applies default settings if optional fields are omitted.
Why this helps
Founders ship improvements but forget to tell customers until much later.
- Links communication to real shipping events.
- Makes customer updates easier to start.
- Keeps launch momentum from getting lost.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Curated to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to create a Curated draft issue when a GitHub deployment status succeeds.
- 3Pick the new deployment status trigger and choose a channel for run reports.
- 4Test with one successful deployment and check the generated draft.
Questions about this workflow
Will it run for failed deployments?
Instruct Notis to create the draft only when the deployment status is successful.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Curated. A trigger fires from one place; an action lands in another.
GitHub triggers
Curated 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 Draft Issue
Tool to create a draft issue for a publication. use after confirming the publication id. applies default settings if optional fields are omitted.
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 Collected Link
Tool to create a collected link for a publication. use when you want to add a new link (with url, title, etc.) to a publication's collection.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
List Email Subscribers
Tool to list all email subscribers for a publication. use after confirming the publication id.
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.
List Publications
Tool to list all publications accessible by the api key. use when you need to retrieve your publication ids for further api calls. example prompt: "list my publications".
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.
List Categories
Tool to list all categories for a publication. use after you have the publication id and need to fetch its categories.
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.
List Issues
Tool to list all issues for a publication. use after you have the publication id and need to fetch its issues (supports pagination).
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.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Curated. 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 Curated.