Convert field data requests into scan form questions
When a repository issue spells out information field teams need to collect, Notis can use it to prepare questions for your existing CodeREADr service.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
Action
Collect Data With Questions
Tool to configure data collection forms by adding custom questions. Use after creating a service to collect survey questions after each scan.
Why this helps
Requests for new scan data can sit in an issue while teams keep collecting incomplete information in the field.
- Turn written collection requirements into a question setup request.
- Keep field data changes tied to the issue that requested them.
- Reduce follow-up needed to get scan forms updated.
Setup
Build it in a few focused steps.
- 1Connect GitHub and CodeREADr once in the Notis portal.
- 2Create an automation in Automations, or tell Notis in plain language from any channel.
- 3In one instruction, ask Notis to use new issues that describe a field data requirement to prepare custom questions for the specified existing CodeREADr service.
- 4Pick the GitHub New Issue Created trigger and choose where run reports go.
- 5Test with one real issue and confirm the service context and requested questions are clear.
Questions about this workflow
Does this create a CodeREADr service too?
This workflow prepares questions for an existing service. Include the service context in your instruction.
What issues should start the workflow?
The trigger is New Issue Created. Describe in your instruction how Notis should recognize issues that contain a field data request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Codereadr. A trigger fires from one place; an action lands in another.
GitHub triggers
Codereadr actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Collect Data With Questions
Tool to configure data collection forms by adding custom questions. Use after creating a service to collect survey questions after each scan.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Configure CodeREADr Connector
Helper to guide configuring the CodeREADr Connector for Google Sheets. There is no public API to programmatically create connector configurations. This tool validates your API connectivity (optional) and returns clear steps to proceed via the Google Sheets Add-on UI: https://www.codereadr.com/knowledgebase/codereadr-connector-add-on/
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.
Configure Direct Scan URL (DSU)
Tool to configure a Direct Scan URL (DSU). Use after obtaining a valid service ID to set up scan callbacks. Use when you need to enable or update the DSU postback settings for a CodeREADr service.
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.
Configure CodeREADr Kiosk Mode
Tool to enable and configure Kiosk Mode for unattended scanning. Use when setting up a dedicated scanning kiosk after service setup.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Configure Picking, Delivery & Receiving App
Tool to configure the complete picking, delivery, and receiving workflow. Use when setting up scan workflow endpoints for an existing CodeREADr service.
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.
Configure CodeREADr Postback URL
Tool to configure a real-time postback URL for a CodeREADr service. Use when you need to set up or modify scan forwarding for an existing service.
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 CodeREADr Service
Tool to create a new workflow configuration (service) for scanning tasks. Use after obtaining a valid API key when registering a new Service.
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.
Delete CodeREADr Database
Tool to delete an existing CodeREADr database. Use when you need to remove a database by its ID after confirming you no longer need its data. Example prompt: "Delete database with ID 123e4567-e89b-12d3-a456-426614174000".
Connect any two apps with Notis in the middle.
GitHub and Codereadr, 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 Codereadr.