Prepare validation when a pull request opens
Give every challenge-dependent pull request a clear testing path from the start.
Trigger
New Pull Request Created
Triggers when a new pull request is created in GitHub, matching the optional configured filters. Emits an event for each newly created pull request. Supports filtering by repository, owner/organisation, author, assignee, label, state, base branch, head branch, and draft status.
Action
Create CAPTCHA Task
Tool to create a new captcha-solving task. use when you need to initiate solving of any supported captcha type. call after assembling captcha parameters.
Why this helps
New PRs can wait in review because protected validation was never prepared alongside the code.
- Reduces waiting at review time
- Makes PR setup repeatable
- Lowers the need for manual reminders
Setup
Build it in a few focused steps.
- 1Connect GitHub and Twocaptcha to Notis once.
- 2Create the automation in the portal or ask Notis to create it.
- 3Describe: when a new pull request targets the protected validation path, create a Twocaptcha task from the available challenge details.
- 4Select the new-PR trigger, choose a reporting channel, and test with one real pull request.
Questions about this workflow
Can this target only certain pull requests?
Configure the GitHub trigger for the relevant repository, branch, author, label, or draft state.
When is this most useful?
It works best when CAPTCHA-protected validation is a predictable part of the pull request process.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Twocaptcha. A trigger fires from one place; an action lands in another.
GitHub triggers
Twocaptcha actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create CAPTCHA Task
Tool to create a new captcha-solving task. use when you need to initiate solving of any supported captcha type. call after assembling captcha parameters.
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 Twocaptcha, 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 Twocaptcha.