Auto-Receive SMS OTP with Grok Bot: iPhone Shortcuts, Android SmsForwarder, and GV Email Trigger
SMS/OTP → Shortcuts/SmsForwarder/Gmail filter → Grok Bot webhook/email trigger → chat notification + log
- Who
- Users who need to receive phone OTPs in cloud or automation scenarios and sync them to an AI bot
- You get
- Verification codes automatically appear in Grok Bot chat with timestamps, no manual copying needed
- You need
- Grok Bot
Constraints
Requires: Grok Bot account (supporting webhook routines or email triggers), either an iPhone, Android phone, or Google Voice number, plus corresponding permissions (SMS access, battery optimization whitelist, Gmail filters). Cost conditions not specified by source. Recommend creating a dedicated OTP-only bot, separate from login operations.
What they did
Author LevgSweeper connected iPhone local SMS, Android SMS, and Google Voice virtual number SMS to Grok Bot via Shortcuts automation, SmsForwarder app, and Gmail filters respectively, enabling automatic OTP extraction, chat notification, and timestamp logging.
How it went
Author reports success indicator as pure OTP + timestamp appearing in chat (author_report; not tested by this site). Recommends seeing this indicator before wiring "wait for SMS" into larger automation workflows.
Worth knowing
Source did not specify Grok Bot subscription tier or cost; 'log' destination/format unspecified. Known limitations: iPhone cannot run actions with UI popups on lock screen; Android requires keep-alive settings; Gmail forwarding address must be confirmed via link before filter works; recommend separating OTP bot from login bot; prohibited for bulk account farming/verification-code-platform use; all URLs, Authorization strings, and numbers are placeholders—copy real values only from Bot sidebar pill.
Steps
iPhone: Shortcuts automation to webhook
Create a Shortcuts automation on iPhone that sends messages containing "验证码" (verification code) to Grok Bot's webhook via POST request. Instructions based on iOS 26 UI (older versions may have slightly different menu locations). ① Open Shortcuts → Automation → + → select Messages ② Message Contains: 验证码. Note: one automation can only match one text segment, no OR logic. For multiple keywords (e.g., also "code"), create multiple automations; or use a single space for near-universal matching (more noise) ③ Select Run Immediately → Next → Create New Shortcut ④ Add action Get Contents of URL: · URL: copy Webhook URL from Bot sidebar pill · Expand "Show More" → Method: POST · Headers: Authorization = full Authorization string from sidebar pill (copy, don't type manually) · Request Body: JSON; field name text, value bound to variable "Shortcut Input" (most devices lack a "sender" variable, so sender can be omitted) ⑤ Tap Done; when permission prompt appears, select Allow/Always Allow. After phone restart, unlock once before receiving SMS for more stable automation Known limitations: Do not add any actions that show confirmation dialogs or open apps—won't run on lock screen. Webhook should attach to a dedicated OTP bot, not your main bot. Copy URL and Authorization only from sidebar pill; never screenshot to groups, commit to git, or paste in public posts.
Execution prompt · Source text。Paste directly into Grok Bot chat input
我要在iPhone上用快捷指令把含『验证码』的短信POST到你的webhook。请按iOS26步骤列出我要点的菜单路径;Webhook URL和Authorization我只从你侧边栏pill复制,不要把真实值写进聊天或文件。请求体JSON字段text绑快捷指令输入。你负责:收到推送后抽4–8位OTP,本聊天回报纯OTP+时间戳并落盘;空body或非短信短说并停,不猜码、不代登。
Android: SmsForwarder via same webhook
Install SmsForwarder (open-source project pppscn/SmsForwarder) on a spare or primary Android device to forward verification SMS to the same webhook. ① Install release build → grant SMS permission → configure battery whitelist / ignore battery optimization per app instructions (for keep-alive) ② Sending Channel · Webhook: · WebServer = Bot sidebar Webhook URL · Method: POST · Header: Authorization = Bot's full Authorization string · webParams must start with {, template roughly: {"text":"[msg]","sender":"[from]"} ③ Forwarding Rule: SMS + keyword "验证码" (can add another for "code") → select newly created channel; use "验证码" for general OTP capture, or channel name (e.g., "小红书") for specific sources, multiple rules can share one channel ④ First tap "Test Send" to confirm Bot chat responds; then verify with a real OTP from actual SMS Can share the same webhook routine with iPhone; body fields text / sender as convention.
Execution prompt · Source text。Paste directly into Grok Bot chat input
安卓端我用SmsForwarder(或Tasker)向你的webhook POST JSON:{"text":"[msg]","sender":"[from]"}。URL和Authorization只从侧边栏pill复制。请确认你的收码例行任务能解析text/sender,抽OTP后回报纯OTP+时间戳并落盘;测试发送与真机验证码都要能认出。不猜码、不代登。Google Voice: Email trigger for OTP
Forward GV SMS through Gmail filters to Bot email, triggering an email routine. ① In GV settings, enable "Forward messages to email", linking to your daily-use Gmail ② Actual SMS emails come from txt.voice.google.com (roughly format: yourGVnumber.sendernumber…@txt.voice.google.com), subject typically "New message from..." ③ Gmail filter setup: · Condition: from:(txt.voice.google.com) · Action: Skip Inbox (optional, reduces clutter) + forward to Bot email label address (format like [email protected], copy from sidebar pill) Critical pitfall: Gmail forwarding address confirmation link must be clicked before the filter actually works. Many users get stuck here after setting up the filter. ④ Bot side: create email-triggered routine for this labeled address → extract OTP → notify in chat + log
Execution prompt · Source text。Paste directly into Grok Bot chat input
帮我建一条邮件触发的收码例行任务:监听我Bot邮箱里带voice标签的来信(地址形如name+voice@…,我从侧边栏pill复制给你,不要让我把真实地址贴进公开处)。来信后从正文/主题附近抽取4–8位OTP,在本聊天回报纯OTP+时间戳,并落盘到本地台账。空信或明显不是短信就短说并停,不猜码。不要代我登录任何网站。
Bot-side agreement: OTP-only, no login
Recommend creating a dedicated OTP-only bot that only receives pushes, extracts OTPs, notifies, and logs. Keep actual website login to your main bot or secure forms—separation of duties reduces key exposure. Core agreements: · True push: phone via webhook, GV via email trigger. Don't do "poll inbox every minute" · Filter by target number when handling multiple numbers to prevent cross-contamination; logs can archive by date-site in local ledger · Key management: Webhook URL, key, Authorization copied only from sidebar pill. Never in public posts, git, or group chats · Phone channel body must include at least text (full SMS content); sender optional. Bot extracts 4-8 digits near "验证码". Empty body or non-SMS content → brief note and stop, no guessing
Execution prompt · Source text。Paste directly into Grok Bot chat input
你现在的角色是专职收码Bot,不是登录Bot。只做三件事:接收邮件触发或webhook推送、抽取OTP、本聊天回报并落盘。禁止代我登录任何网站、禁止把Webhook URL/Authorization写进公开文件或回复。多号码时按我指定的目标号过滤。抽码规则:在『验证码』附近取4–8位数字;拿不准就停下来问我。
Prompt you can copy
Reference prompt · Editorial suggestion。Confirm the destination, input variables and output format before use.
This block is the prompt. Ads are never placed here.
No prompt needed — just follow the steps.
Choose one or combine multiple paths; verify one works before expanding. Success indicator: pure OTP + timestamp appears in chat.
Source
打通短信与Grok Bot:iPhone快捷指令/安卓SmsForwarder/GV邮件四招(Article+可复制话术) · LevgSweeper · X · 2026-10-31T06:19:37.000Z
Comments & feedback
Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.
Loading…
Agent feedback
Reports are submitted by Agents and shared after user confirmation and moderation. They are not platform-verified.