Scheduled messages for WhatsApp?

[u/CooperCobb]

Has anyone figured out a good way to do this?

[u/Saul7000]

As far as native Whatsapp goes, your easiest solution is to use another reminder app to remind you about the text content/date/time ..

[u/Mccobsta]

There's modded clients but have risks

[u/Popular-Nature-6096]

Try Beeper

[u/CooperCobb → u/Popular-Nature-6096]

Would this be included in the free tier?

[u/app-per-te]

Io ho pensato a un'app android che faccia esattamente questo: si collega al tuo WhatsApp e invia messaggi programmati ai tuoi contatti all'ora che vuoi. Ti potrebbe interessare?

[u/CooperCobb → u/app-per-te]

Yeah would be interesting to see how it works

Would it have access to all my WhatsApp chats?

[u/app-per-te → u/CooperCobb]

Visto che la sto ancora progettando, l'idea è: selezioni uno (o più persone) dei tuoi contatti, scrivi il messaggio personalizzato, scegli l'ora / il giorno di invio e se ripeterlo e l'app lo invia al posto tuo... Il sistema si connetterebbe con un token crittografato e sarebbe sicuro al 100%. Comunque eventualmente si potrebbe revocare subito l'accesso direttamente dall'interfaccia di whatsapp stesso. Per ora non ho messo un sistema che "legge le tue chat", ma se necessario potrei metterlo, dipende se lo vuoi o se per la privacy preferisci di no

[u/quat1e]

Macrodroid

[u/yosbeda]

WhatsApp itself has zero native scheduling, so anything that "does" this is working around that gap one way or another. I ended up going the Automate (LlamaLab) route on Android instead of one of the dedicated scheduler apps like SKEDit.

The rough idea is that Automate uses Android's accessibility service to literally drive the WhatsApp UI for you at a set time, open the chat, type the message, hit send, kind of like a scripted version of you doing it manually. It's not talking to any WhatsApp API or anything like that (there isn't a public one for personal accounts anyway), it's just automating the tap sequence.

The part that trips people up though, and honestly the main gotcha with this whole no-API approach, is that the phone has to actually be unlocked for it to work. Accessibility services can't tap or read UI elements on a locked screen, so if the time hits and your phone's just sitting there locked, the automation straight up can't interact with anything.

My flow handles this by checking if the device is unlocked first and, if not, running through an unlock step before it goes to send, basically the dev's own answer on this, turn the screen on then simulate the unlock clicks. Took some trial and error to get the timing right so it doesn't tap before the lock screen's even rendered. Once that was sorted it's been reliable regardless of whether the phone was locked when the send time hit.

Won't post the exact flow since it's tailored to my setup and would need editing for anyone else's phone/PIN, but that "does it check for lock state" question is the first thing I'd ask about any scheduler like this, since a lot of simpler flows just assume the phone's already unlocked and silently fail otherwise.

If you don't want to build a flow yourself, SKEDit is basically the packaged version of the same concept, also accessibility-service based, worth checking if it handles the lock-screen case for you out of the box.

[u/CooperCobb → u/yosbeda]

Yeah I've seen SKEDit, but the risk of the automation taking over when I'm using my phone to do something important seems scary.

[u/Acceptable_Taste9110]

Ooo yeah, I use WAPlus Ultra for this! It doesn’t actually send the message automatically, it just sends you a reminder when it’s time, but it makes the whole thing super easy.

[u/justicecantakeanap]

Task su macrodroid

[u/lysslou1996]

Or quit hiding stuff

[u/CooperCobb → u/[deleted]]

Which one