Keep customers informed after every deployment
Ship the code, then let Notis help you close the communication loop.
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
Authenticate Firm
Tool to validate the api key and retrieve firm details. use when confirming credentials before making other mailsoftly api calls.
Why this helps
After a deployment, customer updates are easy to postpone while attention moves to the next task.
- Reduces post-release follow-up
- Creates a repeatable customer communication habit
- Keeps technical and customer work connected
Setup
Build it in a few focused steps.
- 1Connect GitHub and Mailsoftly to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in plain language to authenticate Mailsoftly and prepare a customer update from each new GitHub deployment status.
- 3Pick the GitHub New Deployment Status Created trigger and choose a channel for run reports.
- 4Test it with one real deployment status and review the generated communication.
Questions about this workflow
Can I limit this to production deployments?
Yes. State the production-only rule in the plain-language automation instruction and let Notis apply it when interpreting the GitHub event.
What does the Mailsoftly action do?
It authenticates the Mailsoftly firm so the workflow can validate the connection before proceeding with the requested communication workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Mailsoftly. A trigger fires from one place; an action lands in another.
GitHub triggers
Mailsoftly 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.
Authenticate Firm
Tool to validate the api key and retrieve firm details. use when confirming credentials before making other mailsoftly api calls.
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.
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 Mailsoftly. 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 Mailsoftly.