Keep Plate Recognizer usage visible after recognition jobs
When a GitHub Actions job submits Snapshot API recognition requests, it can help to review account usage soon after the run. Notis can retrieve Plate Recognizer's current-month call statistics and put the aggregate in a report you already review.
Trigger
GitHub Workflow Run State Changed
Triggers when a GitHub Actions workflow run's status or conclusion changes. Monitors a single workflow run and fires an event whenever it transitions between states (e.g., queued to in_progress, or in_progress to completed) or when its conclusion is set (e.g., success, failure, cancelled).
Action
Snapshot Get Statistics
Tool to retrieve usage statistics for the current month's snapshot api recognition calls. use after making snapshot api calls to monitor monthly usage.
Why this helps
Usage monitoring can get separated from the code workflow that makes recognition calls, making it harder to notice cumulative API consumption.
- Pair completion of a known recognition workflow with a current-month usage snapshot.
- Make cumulative Snapshot API call activity easier to review alongside engineering runs.
- Keep the result read-only and clearly separate account-wide statistics from per-run usage.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Plate Recognizer to Notis once in the portal.
- 2Create an automation and describe in one plain-language prompt that, when the designated GitHub Actions recognition run completes, Notis should retrieve the current-month Snapshot API usage statistics and report the aggregate.
- 3Select the GitHub workflow-run state trigger for the run you intend to monitor and choose where run reports should go.
- 4Test with one completed run that submits Snapshot API requests and confirm the report shows current-month account usage, not a per-run count.
Questions about this workflow
Does this show how many recognition calls that specific GitHub run made?
No. The Plate Recognizer action returns usage statistics for the current month's Snapshot API recognition calls. It does not attribute calls to a specific run.
Does this tell me how much quota remains or stop a run before a limit?
No. The action retrieves usage statistics only. The request does not list a quota-limit or throttling action, so the workflow does not claim remaining allowance or block requests.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Platerecognizer. A trigger fires from one place; an action lands in another.
GitHub triggers
Platerecognizer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Snapshot Get Statistics
Tool to retrieve usage statistics for the current month's snapshot api recognition calls. use after making snapshot api calls to monitor monthly usage.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
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.
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 Platerecognizer, 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 Platerecognizer.