Keep deployment status updates in a PDF record
Give deployment progress and outcomes a clear record that can be shared with the people who need it.
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 PDF Asynchronously
Tool to queue asynchronous PDF generation via webhook. Use when you need to generate a PDF in the background and receive the result via a webhook.
Why this helps
Deployment state changes can be scattered across tools, creating extra work when someone asks what happened.
- Create a document for each new deployment status.
- Make deployment transitions easier to share and review.
- Reduce manual status recaps.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Craftmypdf once in Notis.
- 2Create an automation in Notis and give it a name.
- 3Tell Notis to create a PDF record for each new status on the monitored deployment using your chosen template and available status details.
- 4Choose the new deployment status trigger and where run reports should go.
- 5Test with one real deployment status and check the generated PDF.
Questions about this workflow
Which status changes can be represented?
Deployment statuses can include pending, in progress, success, failure, error, inactive, and queued.
Does this monitor every deployment?
The event is for a specific deployment. Select the deployment you want to monitor when setting up the trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Craftmypdf. A trigger fires from one place; an action lands in another.
GitHub triggers
Craftmypdf actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Editor Session
Tool to create an embeddable editor session URL for a template. Use when you need to embed the PDF editor for a specific template.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create PDF Asynchronously
Tool to queue asynchronous PDF generation via webhook. Use when you need to generate a PDF in the background and receive the result via a webhook.
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.
List PDF Templates
Tool to retrieve a paginated list of PDF templates. Use when you need to browse available templates before generating a PDF.
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 Craftmypdf, 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 Craftmypdf.