Keep deployment updates out of your head
When a deployment changes state, the update should travel automatically. Give stakeholders a timely, readable status without composing another message.
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
Send Batch Templated Emails
Tool to send multiple templated emails in a single batch API call. Use when you need to send up to 500 templated messages at once.
Why this helps
Founders often carry deployment communication in working memory while also handling the release itself.
- Keeps stakeholders aligned automatically.
- Separates pending, successful, and failed deployments.
- Creates a consistent release communication habit.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Postmark to Notis once through the portal.
- 2Create an automation or ask Notis to email stakeholders a concise deployment status update with the environment and relevant links.
- 3Pick the deployment status created trigger, choose a run-report channel, and test with one deployment status.
Questions about this workflow
Can this focus on production only?
Yes. Include the production environment in the instruction or trigger configuration.
Will the email include a deployment link?
Notis can include useful URLs and status details from the GitHub event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Postmark. A trigger fires from one place; an action lands in another.
GitHub triggers
Postmark 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.
Archive Message Stream
Tool to archive a message stream (soft delete). Use when you need to remove a message stream that will be permanently deleted after 45 days.
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.
Check Spam Score
Tool to assess the spam score of a raw email via the SpamCheck API. Use when you have full email source and need spam scoring before sending. Returns spam score and detailed report.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Inbound Rule
Tool to create a new inbound rule trigger to block email from a specific sender or domain. Use when you need to prevent emails from specific addresses or domains from being processed.
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.
Create Message Stream
Tool to create a new message stream. Use when you need to set up separate streams for transactional or broadcast emails.
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.
Create Suppressions
Tool to add email addresses to the suppression list for a message stream. Use when you need to prevent emails from being sent to specific addresses.
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.
Create Template
Tool to create a new email template. Use when you need reusable templates before sending emails.
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.
Create Webhook
Tool to create a new webhook configuration for Postmark. Use when you need to set up a webhook to receive event notifications for email tracking (opens, clicks, bounces, deliveries, etc.).
Commit Event
Triggered when a new commit is pushed to a repository.
Delete Inbound Rule
Tool to delete a specific inbound rule trigger. Use when you need to remove an inbound rule by its ID after confirming it's no longer needed.
Connect any two apps with Notis in the middle.
Not just GitHub and Postmark. 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 Postmark.