Extract text from GitHub documents with OCR Web Service
When a GitHub workflow forwards actual image data in the supported request format, Notis can send it to OCR Web Service and return the extracted text and processing result.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
OCRWebService Recognize
Tool to call soap recognize operation. use when performing ocr on an image to retrieve text, output document, word coordinates, and errors.
Why this helps
Scanned images stored with a code project are not searchable text, and event metadata alone is not enough to OCR the file.
- Make text in supplied scanned images easier to search and review.
- Keep the file-transfer requirement explicit instead of treating a file URL or GitHub event as image data.
Setup
Build it in a few focused steps.
- 1Connect GitHub and OCR Web Service to Notis once in the portal.
- 2Create the automation in the portal or ask Notis for it in plain language.
- 3In the instruction, require actual OCR-ready image data in the inbound request and ask Notis to return extracted text and OCR errors; do not fetch links or infer missing bytes.
- 4Select the Notis incoming-webhook trigger and configure an authorized GitHub-side sender to post image data in the format accepted by the Recognize action; choose where run reports should go.
- 5Test with one non-sensitive sample image sent as actual data and confirm the OCR result.
Questions about this workflow
Can the GitHub event itself provide the document bytes?
The listed GitHub triggers do not say that they include file bytes. This workflow requires the actual image data to be sent to the Notis webhook by an authorized GitHub-side sender.
Will the workflow download a GitHub URL?
No. The listed OCR actions do not include a GitHub file-retrieval step. The instruction skips URL-only events and processes only image data included in the supported request format.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Ocr web service. A trigger fires from one place; an action lands in another.
GitHub triggers
Ocr web service actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Account Credentials
Tool to extract ocrwebservice credentials. use when credentials need to be retrieved from connection metadata before invoking service operations.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account Information
Tool to retrieve current account details such as remaining pages, subscription plan, and expiration date. use when checking account status before submitting ocr jobs.
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.
OCR Web Service Log
Tool to retrieve ocr processing logs. use after specifying date range for your account.
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.
OCRWebService Recognize
Tool to call soap recognize operation. use when performing ocr on an image to retrieve text, output document, word coordinates, and errors.
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 Ocr web service, 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 Ocr web service.