Know the deployment status without checking everywhere
Your operational task updates as the deployment moves from pending to live.
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
Edit Task
Tool to edit an existing task. use after confirming task id and fields to update. updates only provided fields on the task.
Why this helps
Founders lose time reconciling deployment dashboards with their task list.
- Keeps operational status current
- Reduces duplicate status checks
- Makes release progress easier to scan
Setup
Build it in a few focused steps.
- 1Connect GitHub and Simla com to Notis once through the portal.
- 2Ask Notis to update the corresponding Simla com task whenever a GitHub deployment status is created.
- 3Select the deployment status trigger and choose the channel for run reports.
- 4Run one deployment through a test environment and verify the task update.
Questions about this workflow
Which deployment states can be handled?
The instruction can specify pending, in progress, success, failure, or other statuses.
Can this cover production deployments?
Yes. Configure the monitored GitHub deployment and mention the environment in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Simla com. A trigger fires from one place; an action lands in another.
GitHub triggers
Simla com 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.
Create Customer
Tool to create a new customer. use after gathering all customer information.
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.
Create Custom Field
Tool to create a custom field for a specified entity in simla. use when you need to extend orders, customers, corporate customers, or companies with custom metadata fields.
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 Order
Tool to create a new order. use when you have all order details prepared and need to register it in simla via the api.
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 Task
Tool to create a new task. use after gathering task details and assignees.
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.
Edit Customer
Tool to edit an existing customer. use when you need to update customer details by external 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.
Edit Custom Field
Tool to edit an existing custom field by entity and code. use when you need to update custom field metadata before usage.
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.
Edit Order
Tool to edit an existing order by external id. use when you need to update order details by external id.
Commit Event
Triggered when a new commit is pushed to a repository.
Edit Task
Tool to edit an existing task. use after confirming task id and fields to update. updates only provided fields on the task.
Connect any two apps with Notis in the middle.
Not just GitHub and Simla com. Any 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 Simla com.