Create a readable record of deployment status changes
Capture each new deployment status in a consistent document that is easy to revisit.
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
Convert HTML to PDF
Tool to convert HTML to a PDF document. Use when you need to generate a PDF from raw HTML. Returns raw PDF bytes suitable for download or storage.
Why this helps
Deployment transitions can disappear into a stream of operational updates, making it harder to reconstruct what happened.
- Keep a readable record for each new deployment status.
- Include the status transition and deployment context available in the event.
- Make it easier to review deployment history outside the GitHub page.
Setup
Build it in a few focused steps.
- 1Connect GitHub and CustomJS once in the Notis portal.
- 2Create an automation in Automations, then give it a name and prompt.
- 3Tell Notis to format a new deployment status and its available deployment context as HTML and convert it to PDF.
- 4Pick the new deployment status created trigger for the deployment you want to monitor, then choose where run reports go.
- 5Test with one real deployment status and review the PDF.
Questions about this workflow
Does this monitor all deployments?
The listed trigger is for a specific deployment. Select the deployment you want the automation to monitor.
Can it include the full deployment timeline?
The trigger fires for each newly created status. It does not promise a complete historical timeline, so provide historical context if you need it included.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Customjs. A trigger fires from one place; an action lands in another.
GitHub triggers
Customjs actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Authenticate CustomJS API Key
Tool to authenticate a CustomJS API key. Use when verifying a user's API key before making further requests.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Convert HTML to PDF
Tool to convert HTML to a PDF document. Use when you need to generate a PDF from raw HTML. Returns raw PDF bytes suitable for download or storage.
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.
Convert HTML to PNG
Tool to convert HTML string to PNG image. Use when you need a PNG from HTML after preparing your markup.
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.
Capture webpage screenshot
Tool to capture a screenshot of a webpage. Use when you need a visual snapshot of a URL.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Merge multiple PDFs into one
Tool to merge multiple PDF files into a single PDF. Use when you have multiple PDF URLs and want one combined PDF.
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.
Run Puppeteer Script
Tool to run a Puppeteer script and capture a screenshot. Use when automating headless browser tasks and needing a PNG output. Use after confirming the script logic.
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 Customjs, 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 Customjs.