Keep customer ownership aligned with pull request changes
When responsibility changes in GitHub, make the support owner change visible too.
Trigger
Pull Request State / Properties Changed
Triggers when a specific GitHub pull request changes any of these tracked properties: state (open/closed), title, body, draft status, lock status, merge status, assignees, labels, requested reviewers, or milestone. The payload includes the full current PR details, the list of changed field names, and their previous values.
Action
Assign conversation
Assigns a conversation to a specific admin or team in intercom
Why this helps
Reviewer, assignee, or status changes can leave customer follow-up with the wrong owner.
- Reflects meaningful ownership changes in Intercom.
- Reduces stale assignments and handoff confusion.
- Keeps customer follow-up aligned with active work.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Intercom to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it.
- 3Use this instruction: When a customer-impacting GitHub pull request changes assignees, reviewers, draft status, labels, or merge state, update the matching Intercom conversation assignment and add a concise context note.
- 4Choose the pull request state or properties changed trigger and select a report channel.
- 5Test with one real pull request change.
Questions about this workflow
Which properties should trigger reassignment?
Specify the properties that represent a meaningful ownership or workflow change for your team.
Can the workflow only update internal ownership?
Yes. Ask Notis to avoid customer-facing replies and update assignment or notes only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Intercom. A trigger fires from one place; an action lands in another.
GitHub triggers
Intercom actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add subscription to a contact
You can add a specific subscription to a contact. in intercom, we have two different subscription types based on user consent - opt-out and opt-in: 1.attaching a contact to an opt-out subscription type will opt that user out from receiving messages related to that subscription type. 2.attaching a contact to an opt-in subscription type will opt that user in to receiving messages related to that subscription type. this will return a subscription type model for the subscription type that was added to the contact.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add tag to a contact
You can tag a specific contact. this will return a tag object for the tag that was added to the contact.
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.
Assign conversation
Assigns a conversation to a specific admin or team in intercom
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.
Attach a contact to a company
You can attach a company to a single contact.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Close conversation
Closes a conversation in intercom, marking it as resolved
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 a collection
You can create a new collection by making a post request to `https://api.intercom.io/help center/collections.`
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 an article
You can create a new article by making a post request to `https://api.intercom.io/articles`.
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 a note
You can add a note to a single contact.
Connect any two apps with Notis in the middle.
GitHub and Intercom, 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 Intercom.