oauth-helperAutomate OAuth login flows with user confirmation via Telegram. Supports 7 providers: Google, Apple, Microsoft, GitHub, Discord, WeChat, QQ. Features: - Auto-detect available OAuth options on login pages - Ask user to choose via Telegram when multiple options exist - Confirm before authorizing - Handle account selection and consent pages automatically
Install via ClawdBot CLI:
clawdbot install helloliuyongsheng-bot/oauth-helperAutomate OAuth login with Telegram confirmation. Supports 7 major providers.
| Provider | Status | Detection Domain |
|----------|--------|------------------|
| Google | ✅ | accounts.google.com |
| Apple | ✅ | appleid.apple.com |
| Microsoft | ✅ | login.microsoftonline.com, login.live.com |
| GitHub | ✅ | github.com/login/oauth |
| Discord | ✅ | discord.com/oauth2 |
| WeChat | ✅ | open.weixin.qq.com |
| QQ | ✅ | graph.qq.com |
When user requests to login to a website:
1. Open website login page
2. Scan page for available OAuth buttons
3. Send Telegram message:
"🔐 [Site] supports these login methods:
1️⃣ Google
2️⃣ Apple
3️⃣ GitHub
Reply with number to choose"
4. Wait for user reply (60s timeout)
5. Click the selected OAuth button
6. Enter Flow BWhen on an OAuth provider's page:
1. Detect OAuth page type (by URL)
2. Extract target site info
3. Send Telegram: "🔐 [Site] requests [Provider] login. Confirm? Reply yes"
4. Wait for "yes" (60s timeout)
5. Execute provider-specific click sequence
6. Wait for redirect back to original site
7. Send: "✅ Login successful!"URL patterns:
- accounts.google.com/o/oauth2
- accounts.google.com/signin/oauth
- accounts.google.com/v3/signinURL patterns:
- appleid.apple.com/auth/authorize
- appleid.apple.com/auth/oauth2URL patterns:
- login.microsoftonline.com/common/oauth2
- login.microsoftonline.com/consumers
- login.live.com/oauth20URL patterns:
- github.com/login/oauth/authorize
- github.com/login
- github.com/sessions/two-factorURL patterns:
- discord.com/oauth2/authorize
- discord.com/login
- discord.com/api/oauth2URL patterns:
- open.weixin.qq.com/connect/qrconnect
- open.weixin.qq.com/connect/oauth2URL patterns:
- graph.qq.com/oauth2.0/authorize
- ssl.xui.ptlogin2.qq.com
- ui.ptlogin2.qq.comAccount selector: [data-identifier], .JDAKTe
Auth buttons: button:has-text("Allow"), button:has-text("Continue")Email input: input[type="email"], #account_name_text_field
Password: input[type="password"], #password_text_field
Continue: button#sign-in, button:has-text("Continue")
Trust device: button:has-text("Trust")Account selector: .table-row[data-test-id]
Email input: input[name="loginfmt"]
Password: input[name="passwd"]
Next: button#idSIButton9
Accept: button#idBtn_AcceptEmail: input#login_field
Password: input#password
Sign in: input[type="submit"]
Authorize: button[name="authorize"]
2FA: input#app_totpEmail: input[name="email"]
Password: input[name="password"]
Login: button[type="submit"]
Authorize: button:has-text("Authorize")Method: QR code scan
- Screenshot QR code to user
- Wait for mobile scan confirmation
- Detect page redirectMethod: QR code or password login
QR: Screenshot to user
Password mode:
- Switch: a:has-text("密码登录")
- Username: input#u
- Password: input#p
- Login: input#login_buttonScan login pages for these selectors:
| Provider | Selectors | Common Text |
|----------|-----------|-------------|
| Google | [data-provider="google"], .google-btn | "Continue with Google" |
| Apple | [data-provider="apple"], .apple-btn | "Sign in with Apple" |
| Microsoft | [data-provider="microsoft"] | "Sign in with Microsoft" |
| GitHub | [data-provider="github"] | "Continue with GitHub" |
| Discord | [data-provider="discord"] | "Login with Discord" |
| WeChat | .wechat-btn, img[src*="wechat"] | "WeChat Login" |
| QQ | .qq-btn, img[src*="qq"] | "QQ Login" |
Login to each provider in clawd browser:
# Google
browser action=navigate profile=clawd url=https://accounts.google.com
# Apple
browser action=navigate profile=clawd url=https://appleid.apple.com
# Microsoft
browser action=navigate profile=clawd url=https://login.live.com
# GitHub
browser action=navigate profile=clawd url=https://github.com/login
# Discord
browser action=navigate profile=clawd url=https://discord.com/login
# WeChat/QQ - Use QR scan, no pre-login neededUser: Login to Kaggle for me
Agent:
1. Navigate to kaggle.com/account/login
2. Detect Google/Facebook/Yahoo options
3. Send: "🔐 Kaggle supports:
1️⃣ Google
2️⃣ Facebook
3️⃣ Yahoo
Reply number to choose"
4. User replies: 1
5. Click Google login
6. Detect Google OAuth page
7. Send: "🔐 Kaggle requests Google login. Confirm? Reply yes"
8. User replies: yes
9. Select account, click Continue
10. Send: "✅ Logged into Kaggle!"Generated Mar 1, 2026
A social media manager needs to log into various analytics dashboards (e.g., Hootsuite, Buffer) that support OAuth logins from providers like Google or GitHub. This skill automates the login process across platforms, saving time and reducing manual errors by handling provider-specific flows and user confirmations via Telegram.
An e-commerce business uses multiple services (e.g., Shopify, Stripe) that require OAuth logins from Google or Microsoft for account linking. This skill streamlines setup by detecting available login options, confirming with users, and automating authorization, ensuring secure and efficient integration without manual intervention.
Developers frequently access coding platforms like GitHub, GitLab, or cloud services (e.g., AWS via Google login) that use OAuth. This skill assists by scanning login pages for supported providers, prompting selection via Telegram, and handling consent pages, reducing friction in daily workflows and project setups.
Students or educators log into learning management systems (e.g., Coursera, edX) that offer OAuth logins from Google or Microsoft. The skill automates the login flow by detecting options, confirming with users, and managing provider-specific steps, enabling quick access to courses and resources with minimal effort.
Businesses targeting Chinese markets use apps that require WeChat or QQ logins, which often involve QR code scans. This skill handles these providers by capturing QR codes, sending them to users via Telegram for mobile confirmation, and automating redirects, simplifying access for non-technical users.
Offer this skill as part of a monthly subscription for businesses needing automated OAuth logins across multiple platforms. Charge based on the number of providers supported or login frequency, providing ongoing updates and support for new OAuth integrations and detection patterns.
Provide a free version with basic OAuth support for limited providers (e.g., Google and GitHub) and a paid tier unlocking all 7 providers, advanced error handling, and priority Telegram response times. This attracts individual users while monetizing enterprises requiring comprehensive automation.
License this skill to digital agencies or IT service providers who integrate it into their own client offerings. Customize it with agency branding and specific provider configurations, charging a flat fee or per-client usage to streamline login processes for their customers.
💬 Integration Tip
Ensure the Clawd browser is pre-logged into supported OAuth providers and configure Telegram channels properly to avoid timeouts and errors during user confirmations.
iMessage/SMS CLI for listing chats, history, watch, and sending.
Use when you need to control Discord from Clawdbot via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, fetch permissions or member/role/channel info, or handle moderation actions in Discord DMs or channels.
Use when you need to control Slack from Clawdbot via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).
Build or update the BlueBubbles external channel plugin for Clawdbot (extension package, REST send/probe, webhook inbound).
OpenClaw skill for designing Telegram Bot API workflows and command-driven conversations using direct HTTPS requests (no SDKs).