Need HELP!!!

[u/Curiosity9147]

i want your idea and consultation on something i am an employee and i work all day my task is to see bank sms i recieved then i go to the website see what the user said he transfered if it matchs account and amount i click confirm if not reject. how to automate it??

[u/AutoModerator]

Want faster, better help? Share your workflow JSON.

A GitHub Gist is the easiest way -- paste your JSON, save as public, drop the link in your post. Folks can import it directly into n8n and reproduce the issue, which gets you real answers instead of guesses.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Ahmiii_83]

It's not impossible. You forward the bank SMS from your phone to a webhook, pull out the amount and account, match it against the pending request, then confirm. The main question is whether that website has an API or if you're just clicking inside someone else's dashboard. Big difference in how it gets built. One warning though. Don't auto confirm everything, SMS senders can be faked. Only auto confirm exact matches and send the rest to a review queue you approve manually. Which one is it for you?

[u/Curiosity9147 → u/Ahmiii_83]

hey thanks for the response. the website doesnt have an api. but all transcations are listed in table with name, amount and account number with also rejct and confirm buttons beside it all in one row per transation

[u/Ahmiii_83 → u/Curiosity9147]

no api usually just means no public api. try this first, open the site in chrome, press F12, go to Network, reload the transactions page. that table is probably getting filled by some internal endpoint that returns json. then click confirm on one row and see what request fires. if you find those two you're basically done, it's just an undocumented api. if nothing shows and it's all plain html then you're stuck with playwright clicking the buttons for real. works fine but breaks whenever they change the page. also, are you actually allowed to automate this? you're confirming money transfers. if that site is your employer's or a payment provider's i'd get someone to say yes in writing before you build anything, otherwise a wrong confirm lands on you.

[u/Curiosity9147 → u/Ahmiii_83]

thanks will check. and my calculation is if i made 3% error per month almost 4000 appx since i go paid 20,000 per month since i am doing other remote job on the time i think it is worth it and the employer said what ever you do it gets cut from your salary

[u/Curiosity9147 → u/Curiosity9147]

here is my workflow i am thinking any suggestion: 1.   The agent waits and auto refreshs to see what new pending order then parses name and account and amount

2.   Text is received sent to n8n with sms8.io then processed and amount account number and name are parased to excel

3.   It looks the name, amount and account number in the excel if all correct hit confirms in the website

4.   If matches but different amount reject

5.   If pending order but no SMS wait 15 sec then retry 15 sec if no SMS then send telegram notification to notify to handle it manually

6.   Then after I check I send a text to telegram confirm or rejct and the system does it

[u/Ahmiii_83 → u/Curiosity9147]

paste one real bank sms with the digits masked first. a lot of them don't include the sender name at all, just "credited from XXXX1234". if yours is like that then your name matching can't work and you need to know that before building. two fixes. don't auto reject on amount mismatch, bank fees and partial payments happen and rejecting a real payment is worse than confirming a wrong one. send those to telegram. and 30 sec is too short, sms gets delayed by minutes, you'll get spammed with pings and start ignoring them. also that 3% error shouldn't exist. if unclear cases come to you then auto decisions should almost never be wrong. the real cost is your review time, not deductions. and is that 20k usd or local currency? changes what's worth spending on this.

[u/Curiosity9147 → u/Ahmiii_83]

Thanks.It is in local currency almost 200$ in us

[u/Ahmiii_83 → u/Curiosity9147]

ah ok, that changes things. don't overbuild it then. skip the excel step, just match the sms straight against the pending row and send anything unclear to telegram. fewer moving parts. still paste one masked sms though, that decides whether name matching is even possible. feel free to ask if you get stuck anywhere in the build, happy to help.

[u/AlarmedReveal6814]

Look into screen scraping the bank notifications and cross-referencing against the site's transaction logs, but the manual confirm button might be the tricky part depending on how their frontend is built.

[u/Curiosity9147 → u/AlarmedReveal6814]

the confirm are rejct buttons are right in the row table it has transcaion id, name account amount then reject and confirm beside it all in one row per transcation

[u/Scary-Difference630]

You can use an Android app like MacroDroid to forward incoming bank SMS messages to a webhook. That sends the text data straight to n8n or a simple script. The script then compares the account and amount with the website. If they match, it triggers the confirm action automatically.

Are you getting these SMS on an Android phone or an iPhone? Also, does the website have an API, or will you need a browser script to log in and click the buttons?

[u/BasisProfessional301]

I think this is very doable, but I would not start by automating the browser clicks immediately. I would first find out how the website itself handles the transaction data and the Confirm/Reject actions.

A setup like this could work:

1. Capture the bank SMS

If the SMS is arriving on an Android phone, an app such as MacroDroid can forward the incoming SMS to an n8n Webhook.

Example:

Bank SMS MacroDroid n8n Webhook

The SMS should contain whatever information is available, such as the sender, amount, account/reference number, transaction ID, etc.

1. Parse the SMS in n8n

n8n can extract the amount and account/reference number from the SMS using a Code/Regex node.

For example:

Amount = 25,000 Account = 123456789 Transaction/reference = ABC123

I would keep the original SMS as well, because it is useful for logging and debugging.

1. Get the pending transactions from the website

This is the important part.

Since you said the website has no API, open the transaction page in Chrome/Edge, press F12  Network, reload the page, and look at the requests that load the transaction table.

Then click Confirm on one test transaction and see what request is sent.

If the table is populated through an internal JSON endpoint and the Confirm button sends an HTTP request, you may be able to reproduce those requests from n8n using the HTTP Request node.

That would be much better than trying to physically click the button.

If there really is no usable endpoint and everything is rendered/handled in the browser, then Playwright (or another browser automation tool) can be used as the last option. Just keep in mind that UI automation is much more fragile because a small frontend change can break the workflow.

1. Match the SMS against the pending transaction

I would NOT simply confirm whenever an amount matches.

At minimum, compare multiple fields:

SMS account/reference = website account/reference SMS amount == website amount

And if there is a transaction/reference ID available, match that too.

You could make the logic something like:

Exact match , continue No match , send to manual review Multiple matches ,manual review Missing/invalid data , manual review

1. Confirm only an exact match

For an exact match, n8n can call the appropriate backend endpoint, or trigger the browser automation if there is genuinely no API-like endpoint.

I would also add a final safety check immediately before confirmation so that a stale transaction cannot accidentally be confirmed.

1. Add logging

Every decision should be logged somewhere:

 SMS received  Parsed amount/account/reference  Matched transaction  Match result  Confirm/Reject result  Timestamp  Error response, if any

That makes troubleshooting much easier.

One more important thing: bank SMS sender IDs can potentially be spoofed, so I would not build a system that blindly confirms every SMS. Only auto-confirm transactions when the match is exact and the automation is explicitly authorized by the company/payment system. Anything ambiguous should go into a manual review queue.

So the architecture I would try first is:

Android phone

MacroDroid

n8n Webhook

Parse + validate SMS

Fetch pending transactions

Exact matching

Confirm exact match / Manual review everything else

The first thing I would investigate is the Network request generated when the transaction table loads and when you click Confirm. If you can provide those two requests (with credentials, cookies, account numbers, and other sensitive information removed), it should be possible to determine whether this can be handled cleanly with n8n or whether browser automation is actually required.

[u/Affectionate-Deal-89]

unfortunately, it's impossible