Turn CAPTCHA job failures into action
A failed job with a clear cause deserves an immediate next step, not another investigation loop.
Trigger
Workflow Job State Changed
Triggers when the status, conclusion, timestamps, runner assignment, or step details of a specific GitHub Actions workflow job change between polls. The payload includes the full current job state, a list of which fields changed, and the previous status/conclusion values for easy comparison.
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
Founders lose time reopening logs to determine whether a failure needs hands-on attention.
- Makes failure handling predictable
- Reduces log-checking
- Preserves focus for higher-value decisions
Setup
Build it in a few focused steps.
- 1Connect GitHub and Twocaptcha to Notis once.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Describe the outcome: when a monitored job fails due to a CAPTCHA, create a Twocaptcha task from the challenge details.
- 4Choose the job-state trigger, select the run-report channel, and test one representative failure.
Questions about this workflow
Can this target one job?
Yes. Configure the GitHub trigger for the specific workflow job you want Notis to monitor.
What happens after the task is created?
Twocaptcha receives a new solving task, and Notis reports the automation run in your chosen channel.
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
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.
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.
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.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Twocaptcha. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Twocaptcha.