Check screenshot details when a review arrives
Have Notis look up the metadata for the screenshot tied to a reviewed change and surface its dimensions and file size in the run report.
Trigger
Pull Request Review Submitted
Triggers when a new review is submitted for a GitHub pull request. Emits an event for each newly submitted review on the monitored pull request, covering all review types: APPROVED, CHANGES_REQUESTED, COMMENTED, and DISMISSED.
Action
Get Screenshot Metadata
Tool to retrieve metadata for a previously captured screenshot. use when you need details like file size and dimensions after capture.
Why this helps
A reviewer may need to verify which screenshot was shared and whether its dimensions or file size fit the review context.
- Bring screenshot dimensions and file size into the review follow-up.
- Reduce manual lookups for visual artifacts.
- Create a clear run report for teams reviewing UI changes.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Apiflash once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to retrieve metadata for the Apiflash screenshot associated with the reviewed pull request and include the result in the run report.
- 4Pick the GitHub Pull Request Review Submitted trigger and choose where run reports go.
- 5Test with one real review that references a previously captured screenshot.
Questions about this workflow
Does this create a screenshot?
No. It retrieves metadata for a previously captured screenshot. Use a separate capture workflow when a new image is needed.
What does the metadata lookup need?
It needs a reference to the screenshot that Apiflash can use to identify the captured image. If that reference is not available in the review context, include how Notis should obtain it.
What details can the workflow report?
The action returns screenshot metadata such as file size and dimensions, which Notis can include in its run report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Apiflash. A trigger fires from one place; an action lands in another.
GitHub triggers
Apiflash actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Batch Capture Screenshots
Tool to capture screenshots for multiple urls in a single request. use when you have a list of pages to snapshot in batch.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Capture Website Screenshot (POST)
Tool to capture a screenshot of a website via http post. use when you need to post form data parameters.
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 Quota Information
Tool to retrieve current api quota usage and limits. use after authentication to monitor usage and reset times.
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 Screenshot Metadata
Tool to retrieve metadata for a previously captured screenshot. use when you need details like file size and dimensions after capture.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Apiflash, 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 Apiflash.