Reflect GitHub issue changes in Dynamics cases
Keep a linked case current as an issue’s status, title, labels, or other tracked details change.
Trigger
Issue State / Properties Changed
Triggers when a specific GitHub issue changes any of its tracked properties. Monitored properties: state (open/closed), state_reason, title, body, assignees, labels, milestone, lock status, active_lock_reason, comment count, and closed_at timestamp. When a change is detected, the payload includes the full current issue details, the list of changed field names, and their previous values.
Action
Update Case
Updates an existing case (incident) entity record in dynamics crm using the web api.
Why this helps
When an issue changes after a case is opened, people may have to check GitHub and Dynamics separately to see the current state.
- Reduce repeat checking across GitHub and Dynamics 365.
- Carry issue updates into an existing case when the correct case is identified.
- Keep investigation records closer to the current repository state.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Dynamics 365 once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis what you want from any channel.
- 3Ask Notis to update the Dynamics 365 case associated with the changed issue, and provide a reliable way to identify that case if the event does not include one.
- 4Pick GitHub’s Issue State / Properties Changed trigger and choose where run reports should go.
- 5Test with one real issue and an identifiable related case, then check the case update.
Questions about this workflow
How does the workflow know which case to update?
The GitHub event describes issue changes but does not guarantee a Dynamics case ID. Provide a reliable association in your instruction or another available context.
Which issue changes can start this workflow?
The event monitors tracked properties such as state, title, body, assignees, labels, milestone, and lock status.
Can it create a case if none exists?
This workflow uses the Update Case action. It requires an existing case that Notis can identify.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Dynamics365. A trigger fires from one place; an action lands in another.
GitHub triggers
Dynamics365 actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get all invoices action
Get all invoices action
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Account
Creates a new account entity record in dynamics crm using the web api.
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 Case
Creates a new case (incident) entity record in dynamics crm using the web api.
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 Contact
Creates a new contact entity record in dynamics crm using the web api.
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 Invoice
Creates a new invoice entity record in dynamics crm using the web 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 Lead
Creates a new lead entity record in dynamics crm using the web api.
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 Opportunity
Creates a new opportunity entity record in dynamics crm using the web api.
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 Sales Order
Creates a new sales order entity record in dynamics crm using the web api.
Connect any two apps with Notis in the middle.
GitHub and Dynamics365, 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 Dynamics365.