Follow up while a successful deployment is fresh
A successful deployment is a clean moment to reconnect with the people it helps. Notis can surface your Reply.io sequences then.
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
List Sequences
Tool to retrieve a paginated list of sequences. use when you need to browse sequences with optional filtering by name.
Why this helps
Positive shipping moments pass without customer follow-up because the founder is already moving to the next task.
- Capture the best timing for follow-up
- Reduce reliance on memory after shipping
- Make customer communication part of completion
Setup
Build it in a few focused steps.
- 1Connect GitHub and Reply.io to Notis once through the portal.
- 2Create the automation with a plain-language instruction to list Reply.io sequences after a successful GitHub deployment status.
- 3Choose the new deployment status trigger and a channel for run reports.
- 4Test with a successful staging deployment.
Questions about this workflow
Can it run only on success?
Yes. Instruct Notis to act only when the deployment status is successful.
What happens for failed deployments?
The instruction can exclude failures so the workflow stays focused.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Reply io. A trigger fires from one place; an action lands in another.
GitHub triggers
Reply io 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.
Delete Campaign
Tool to delete a campaign by id. use when you need to remove an existing campaign; use after confirming the campaign id.
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.
Delete Email Account
Tool to delete a specific email account. use when you need to remove an existing email account identified by its id.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Sequence
Tool to delete a sequence. use after confirming the sequence exists to remove it permanently.
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.
Delete User
Tool to delete a user. use after confirming the user exists to remove them permanently.
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.
Generate ULID
Tool to generate a ulid string. use when a unique identifier is required for creating tasks or other entities in reply.io.
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 Campaigns
Tool to list all campaigns (sequences). use when you need a paginated list of campaigns.
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.
Reply.io List Contacts
Tool to list all contacts. use when verifying api access and gathering contact ids for testing contact creation.
Commit Event
Triggered when a new commit is pushed to a repository.
Reply.io List Email Accounts
Tool to list all email accounts. use when you need to retrieve email accounts page by page.
Connect any two apps with Notis in the middle.
Not just GitHub and Reply io. 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 Reply io.