Route Authyo OTP failures into GitHub issues
Send a failure report to Notis and keep authentication problems visible in the repository where your team works.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
OTP failures can be easy to miss when reports arrive outside the engineering issue queue.
- Capture each reported OTP problem in a shared engineering queue.
- Summarize the supplied report so the team has context to investigate.
- Reduce manual copying between authentication operations and GitHub.
Setup
Build it in a few focused steps.
- 1Connect Authyo and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, then give it a name and prompt.
- 3Tell Notis to create a GitHub issue summarizing the Authyo OTP failure details in each incoming report.
- 4Choose the notis_webhook trigger and select where run reports should go.
- 5Test with one real OTP failure report sent to the webhook.
Questions about this workflow
Does Authyo send this workflow a trigger automatically?
No. Authyo has no trigger events in this package. A Notis webhook starts the automation when it receives an HTTP request.
What information should the request include?
Include the OTP failure details your team needs to investigate, such as the affected flow and any available error message. Notis cannot infer information absent from the request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Authyo to GitHub. A trigger fires from one place; an action lands in another.
Authyo triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Authyo and GitHub, 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 GitHub.