Organize customer questions during security incidents
A security incident needs a clear customer listening channel, not another loose thread.
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
Create Survey
Tool to create a new survey. use when you have a survey title and need an id for follow-up operations. example: "create a survey titled 'customer satisfaction'"
Why this helps
During a secret exposure response, founders must coordinate technical remediation and customer reassurance at the same time.
- Creates a dedicated listening channel quickly
- Captures recurring customer concerns
- Supports clearer incident communication planning
Setup
Build it in a few focused steps.
- 1Connect GitHub and SurveyMonkey to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create an incident feedback survey after a new secret scanning alert.
- 3Select the New Secret Scanning Alert Detected trigger and choose the channel for run reports.
- 4Test it with one real alert and review the generated survey.
Questions about this workflow
Does this send an incident notice automatically?
No. It creates a survey. You can use the resulting questions and responses to inform your communication plan.
Can the survey include the detected secret type?
Yes. Ask Notis to use relevant non-sensitive alert context while excluding secrets or credentials.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Survey monkey. A trigger fires from one place; an action lands in another.
GitHub triggers
Survey monkey 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 Survey
Tool to create a new survey. use when you have a survey title and need an id for follow-up operations. example: "create a survey titled 'customer satisfaction'"
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.
Delete Survey
Tool to delete a specific survey. use when the survey id is confirmed correct. deletion is irreversible. example prompt: "delete survey '123456789'."
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Survey Collectors
Tool to retrieve a list of collectors for a specific survey. use when you need collector urls, counts, and statuses.
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.
Get Contacts
Tool to retrieve a list of contacts. use after authenticating with surveymonkey. call this to fetch all contacts associated with your account.
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 Groups
Tool to retrieve a list of groups. use after authentication when you need to enumerate or paginate through all groups in your surveymonkey account.
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.
Get Survey Responses
Tool to retrieve a list of responses for a specific survey. use when you need to browse or filter responses after confirming the survey id.
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.
Get Survey Details
Tool to retrieve metadata and counts for a specific survey. use after confirming the survey id.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Surveys
Tool to retrieve a list of surveys. use when you need to enumerate or paginate through all surveys.
Connect any two apps with Notis in the middle.
Not just GitHub and Survey monkey. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Survey monkey.