14 days left 13/1000 Executions Assistant Overview Personal Chats View all Automatic OTP code autofill Multi-page loan application form Admin Panel Templates Insights Help Settings Continue Thought for 22s The saved draft may differ from what ran. I'll rebuild from the current source and test it. Thought for 14s The draft is saved, but I haven't fixed the failure. Verification was simulated, so it doesn't prove the live form works. What failed: executions 4 and the earlier failed runs stopped at the first node, Loan Application - Page 1. The error was "No Respond to Webhook node found". That version had the form trigger set to respond through a later node, and n8n didn't find one. What I did: I re-saved the workflow from its current source. The saved draft differs from the published version. It doesn't carry that response setting. In a simulated run, all 5 nodes executed (4 form pages plus the completion screen). That run only injected test data. It didn't open the real form. What's unconfirmed: the live form at https://mkopo.app.n8n.cloud/form/loan-application still runs the older published version. That version has the error until you publish the draft. I haven't confirmed the draft behaves differently, because only a real submission can show that. Open the form in your browser and submit all four pages. I'll check the resulting execution and publish the draft if it completes. If it still fails, I'll change the trigger's response setting. Still failed Thought for 10s I published the draft. Execution 7 still failed because it ran the old published version (e34f7bef…), which was set to "respond via Respond to Webhook" but has no such node. The draft doesn't have that setting. I've now made the draft the live version. I haven't confirmed the fix on a real submission. Open https://mkopo.app.n8n.cloud/form/loan-application and submit the first page. If it errors again, tell me and I'll check the new execution. On otp page I need automatic filling up without manual typing the code,,,the format of code to be pick is ,,,You are being registered in Mixx by Yas Super App, use the code Op5KdcxOvsDDnQoIdkT3 to complete registration. Do not share the code with anybody. For more info contact us on 100. DWvV9aXqDR Finished thinking How should the code get into the OTP page? Browser autofill only (autocomplete one-time-code): the user taps the suggestion; works on some phones, not guaranteed for this message format Finished thinking You stopped this run I need when applicants receive that message with those format I need to automatically pick without manual typing then the applicants click there browser to allow them automatically picked Finished thinking I can't make this fully automatic with the n8n Form node. The Form node can't add the autocomplete="one-time-code" attribute that browsers look for. Its tags are blocked in HTML fields, and custom CSS can't add attributes. n8n form pages are also hosted on n8n's domain, so I can't add my own script. What does and doesn't work on your applicants' phones: Web OTP API (automatic pick with a browser permission prompt): the SMS must end with @mkopo.app.n8n.cloud #code. Your message comes from Yas and doesn't have that line, so this won't trigger. It also works only in Android Chrome. Keyboard suggestion: Android and iPhone often show the code above the keyboard when a field looks like an OTP field. The applicant taps it once. I can improve the odds by renaming the field label to "One-time code (OTP)" and adding a placeholder. This isn't guaranteed. Fully automatic: this needs the SMS forwarded to n8n by an SMS-forwarder app or SMS gateway webhook. n8n would pull the code with the pattern use the code (\S+) to complete (it gives Op5KdcxOvsDDnQoIdkT3 from your sample) and pre-fill page 4. I can build it, but it needs the SMS to reach n8n, which you chose against earlier. Do you want me to rename the page 4 field to improve keyboard suggestions? Or should I build the SMS-forwarding route? Fully automatic,,when applicants phone detect format of message like that it's should capture card automatically filled Finished thinking I can't make this fully automatic inside n8n, and I don't want to build something that looks automatic but isn't. Phone detection isn't something n8n controls. The phone's keyboard or browser decides whether to offer an SMS code. n8n form pages don't give it the signals it looks for, and I can't change that. Forwarding the SMS to n8n won't work either. The message goes to the applicant's phone, not to you. n8n would only see it if every applicant installed an SMS-forwarder app, which isn't realistic. The practical route to browser autofill is a custom page for the OTP step. It would use autocomplete="one-time-code" and the Web OTP API. The page would send the code to n8n. Two limits apply: Home for the page: it has to live on a web page you host, not on the n8n form. n8n webhook pages block scripts on many setups, so I can't promise it would work there. SMS format: Web OTP only auto-picks when the SMS ends with a line like @yourdomain #code. Your sender, Yas, controls that wording, so you would need to ask them to add it. Without that wording change, the best option is the one-tap keyboard suggestion. I can improve its chances by renaming the page 4 field to "One-time code (OTP)". Do you want me to make that change? No Understood. I haven't changed anything, and the published form stays as it is. The OTP field still needs manual typing. Automatic pickup needs one of three things: an SMS that ends with @yourdomain #code, SMS forwarding to n8n, or a custom-hosted OTP page. If you want any of these later, tell me which one and I'll build it. I need custom hosted otp page Thought for 31s I've built the new flow as a draft. The published form still has the old OTP page. It needs one value from you before it can work. What changed: Pages 1 to 3: the n8n form keeps pages 1 to 3. After the KRA PIN page, the applicant is redirected to your hosted OTP page. The phone number is added to the URL as ?phone=…. New webhook: POST https://mkopo.app.n8n.cloud/webhook/loan-otp receives { "phone": "...", "code": "..." } from your page and replies { "ok": true }. It accepts requests from any website. At the moment it only confirms receipt. It doesn't check the code or store it. What you need to do: enter the URL of your hosted OTP page in the setup panel, in the Build OTP Page URL field. The URL of the hosted OTP page doesn't exist yet. I haven't built that page. What I haven't verified: only the webhook path was tested, and with simulated input. The form-to-redirect path was not reached. The workflow isn't published, so applicants still see the old form. For your OTP page: Use . Call navigator.credentials.get({ otp: { transport: ['sms'] } }) to pick up the code. POST the code to the webhook above. Web OTP only works in Android Chrome, and the SMS must end with @your-domain #code. Ask Yas to add that line. I can write that OTP page as a single HTML file for you. Do you want it? How to get my URL of my hosted otp page Finished thinking You get that URL by putting an HTML page on a web host. The host gives you the address. I can write the page, but I can't host it for you. Free options that take a few minutes each: Netlify Drop: go to app.netlify.com/drop and drag the HTML file onto the page. You get a URL like https://your-site.netlify.app. Cloudflare Pages: upload the file in the dashboard. You get https://your-site.pages.dev. GitHub Pages: put the file in a repository and turn on Pages. You get https://yourname.github.io/repo. Once the page is online, paste its full address into the Build OTP Page URL field in the setup panel. Use the address of the page itself, for example https://your-site.netlify.app/index.html. Because Web OTP needs the SMS to end with @your-domain #code, the domain in that line must match this host. Ask Yas to add it once you have your final address. Do you want me to write the OTP page as a single HTML file now? It would read the phone number from the link, accept the code, and post it to the n8n webhook. Yes Thought for 9s I wrote the OTP page to otp-page/index.html in the workspace. I haven't tested it in a browser or against the live webhook. What the page does: It reads ?phone= from the link and shows it. The code field uses autocomplete="one-time-code". On Android Chrome it requests the SMS through Web OTP, then fills and submits the code automatically. If someone pastes the whole SMS, it extracts the code with the pattern use the code … to complete. It posts { phone, code } to https://mkopo.app.n8n.cloud/webhook/loan-otp, then shows "Application received." Limits: Webhook not live: that webhook only works after you publish the workflow. The publish step still needs the URL setup below. Automatic fill: Web OTP only fills automatically when the SMS ends with @your-domain #Op5KdcxOvsDDnQoIdkT3. Without that line, applicants type or paste the code. Ask Yas to add it. Nothing stored or checked: the webhook only confirms receipt. It doesn't check the code or store the application. Next steps: Host the file with Netlify Drop and copy the URL. Paste that URL into Build OTP Page URL in the setup panel. Tell me when that's done. I'll test and publish the workflow. I can't attach the file here. If you can't find it in the workspace, tell me and I'll paste the full HTML into the chat. I need my html which I can host on netlify Here is the full file. Save it as index.html, then drag it onto app.netlify.com/drop.
Page 4 of 4: enter the code sent to .
Page 4 of 4: enter the code sent to .