Bring recent Datascope files into GitHub release updates
When release notes or assets change, have Notis check Datascope for generated files in the relevant date range and include useful file details in its report.
Trigger
GitHub Release State Changed
Triggers when a specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/commit, and the set of attached assets. The payload includes the full current release details, a list of which fields changed, and the previous values for comparison.
Action
List Last Generated Files
Tool to retrieve all generated files (PDFs, Excel) from a specific date range. Use when you need to access recently generated files within the last 90 days. Date format is MM/DD/YYYY.
Why this helps
Release updates may need supporting operational PDFs or spreadsheets, but finding recent generated files takes a separate search.
- Surface recent Datascope generated files during a release update.
- Reduce manual searches for supporting PDFs and spreadsheets.
- Keep file references close to release details in the report.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Datascope once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3In one instruction, ask Notis to retrieve Datascope generated files for a date range relevant to the changed release and summarize matching file details.
- 4Pick the GitHub Release State Changed trigger and choose where run reports go.
- 5Test with one real release change and review the report.
Questions about this workflow
Does this generate a new Datascope file?
No. The action lists generated files for a specified date range; it does not create files.
What date range should the automation search?
The action requires a date range in MM/DD/YYYY format and supports ranges within the last 90 days. State the intended range in your instruction or provide it through the workflow context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Datascope. A trigger fires from one place; an action lands in another.
GitHub triggers
Datascope actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Location
Tool to create a new location in DataScope with geographic coordinates. Use when you need to register a physical location with name and code identifiers.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get All Answers V2
Tool to retrieve last answers from Datascope forms (limit 200 per request). Use when you need to fetch form submissions with optional filtering by form, user, date range, or location. Supports pagination via offset parameter for retrieving additional batches.
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.
Get All Answers With Metadata
Tool to retrieve all answers with metadata from the DataScope platform. Returns up to 600 form answers with form metadata, user information, timestamps, and GPS coordinates. Use when you need to fetch submission data with filtering options by form, user, date range, or location.
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.
Get all list elements
Tool to retrieve all items from a specific metadata list in Datascope. Use when you need to fetch all elements belonging to a particular list type (products, locations, customers, etc.).
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 All Locations
Tool to retrieve all locations configured in the DataScope system. Use when you need to access location data including addresses, coordinates, and company associations.
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 Last Tickets
Tool to retrieve the last 5 tickets (findings) from the DataScope system. Use when you need to view recent tickets or findings.
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 List Element
Tool to retrieve a specific element from a metadata list by type and ID. Use when you need to fetch detailed information about a specific list element such as locations, products, or other metadata objects.
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 Ticket Types
Tool to retrieve available ticket types (findings types) from the DataScope system. Use when you need to access the list of ticket type configurations.
Connect any two apps with Notis in the middle.
GitHub and Datascope, 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 Datascope.