Make secret scanning alerts impossible to miss
Security alerts need a fast path from detection to coordinated follow-up.
Trigger
New Secret Scanning Alert Detected
Triggers when a new secret scanning alert is detected in a GitHub repository. Monitors open secret scanning alerts and fires an event for each newly detected alert. Supports filtering by secret type (e.g., personal access tokens, AWS keys) and by token validity status (active, inactive, unknown). The payload includes the alert number, secret type, validity status, resolution state, timestamps, URLs, and flags for push protection bypass, public exposure, and multi-repo detection.
Action
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.
Why this helps
A leaked secret can demand immediate action, but the alert may remain isolated in GitHub.
- Surfaces security-related follow-up in Intercom.
- Creates consistent categorization for urgent cases.
- Reduces the chance of missing a sensitive customer-impacting issue.
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 GitHub detects a new secret scanning alert, add the security-alert tag to the matching Intercom contact or conversation and include the alert link in a note if needed.
- 4Select the secret scanning alert trigger and choose a run-report channel.
- 5Test with one real or safely simulated alert.
Questions about this workflow
Will the secret value be exposed?
The instruction should tell Notis to include alert metadata and links, never the secret itself.
Can tags differ by alert type?
Yes. Describe the tag rules for token type, validity, or exposure status.
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
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.
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.
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.
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 Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Assign conversation
Assigns a conversation to a specific admin or team in intercom
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.
Attach a contact to a company
You can attach a company to a single contact.
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.
Close conversation
Closes a conversation in intercom, marking it as resolved
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 collection
You can create a new collection by making a post request to `https://api.intercom.io/help center/collections.`
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.
Create an article
You can create a new article by making a post request to `https://api.intercom.io/articles`.
Commit Event
Triggered when a new commit is pushed to a repository.
Create a note
You can add a note to a single contact.
Connect any two apps with Notis in the middle.
Not just GitHub and Intercom. 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 Intercom.