Keep deployment follow-up in the right Respond.io conversation
When a monitored GitHub deployment succeeds, Notis can add an internal note to the existing Respond.io conversation you have explicitly associated with that repository. The update stays inside your team and is not sent to the customer.
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
Add internal comment to conversation
Tool to add a comment (internal note) to a contact's conversation. use after verifying the contact identifier.
Why this helps
A deployment can complete while its customer support context remains stale, leaving the team to look across tools before answering a follow-up.
- Record a successful deployment status and environment in the mapped support conversation.
- Keep the update internal so it can inform a later human response without sending a customer message.
- Avoid guessing which Respond.io contact belongs to a GitHub repository by requiring an explicit mapping.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Respond.io to Notis once, and establish an explicit mapping from the monitored repository to an existing Respond.io contact conversation.
- 2Create an automation in the portal or ask Notis conversationally; instruct it to add a concise internal note only for successful statuses and only when that exact mapping exists.
- 3Select the new deployment status trigger for the intended deployment, choose a channel for run reports, and create the automation.
- 4Test with one successful status and verify the internal note appears on the mapped conversation; leave failures and unmatched repositories untouched.
Questions about this workflow
Will this send a message to the customer?
No. The action adds an internal comment to a Respond.io conversation. It does not send a customer-facing reply.
How does it find the right conversation?
Use an explicit repository-to-contact conversation mapping in the instruction or available context. Do not infer the Respond.io contact from a GitHub username or repository name, and skip the note if the mapping is missing.
Which deployment information can the note include?
The trigger reports the deployment status, creator, environment, description, timestamps, and relevant URLs. Keep the note to those available details and the configured repository context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Respond io. A trigger fires from one place; an action lands in another.
GitHub triggers
Respond io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add internal comment to conversation
Tool to add a comment (internal note) to a contact's conversation. use after verifying the contact identifier.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Contact
Tool to create a new contact in the workspace. use when you need to add a contact by specifying an identifier; delay subsequent actions due to processing.
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 channels
Tool to retrieve a list of channels connected to the workspace. use when you need to enumerate all messaging channels with pagination support.
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.
List users
Tool to retrieve a list of users in the workspace. use when you need to fetch all workspace users for auditing or assignment.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Add internal comment to conversation
Tool to add a comment (internal note) to a contact's conversation. use after verifying the contact identifier.
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 Space Tag
Tool to create a new tag in the workspace. use when you need to label or categorize contacts or conversations after workspace setup.
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.
Get Message
Tool to retrieve a specific message. use when you need the details of a message sent to or received from a contact.
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.
Update Space Tag
Tool to update an existing tag in the workspace. use when you need to modify a tag's name, description, color, or emoji after confirming it exists.
Connect any two apps with Notis in the middle.
GitHub and Respond io, 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 Respond io.