Skip to main content

Send WhatsApp Messages Automatically Using Apple Shortcuts

Apple Shortcuts is a great automation tool, but when it comes to WhatsApp, the default Send Message via WhatsApp action has some limitations. It only allows sending messages to individual contacts (not groups) and always requires user interaction to press the send button.


In this tutorial, I’ll show you an alternative method that works for both individual contacts and groups without requiring manual confirmation.


Steps to Automate WhatsApp Messages in Shortcuts


1. Send a Message Manually First


Before setting up the shortcut, open the WhatsApp app and manually send a message to the contact or group you want to automate. This step ensures that WhatsApp registers the recipient in the action list later.


2. Add a Custom WhatsApp Action in Shortcuts


Now, let’s configure the Shortcut:

1. Open the Shortcuts app and create a new shortcut.

2. Tap Add Action and search for WhatsApp.

3. Instead of selecting a specific action, tap on the WhatsApp app name itself.

4. Scroll down to the Others section, and you should see a custom action to send messages.




3. Configure the Message and Disable User Interaction

1. Select the custom WhatsApp action.

2. Enter the message you want to send.

3. To send messages automatically without needing confirmation, toggle off Show When Run




4. Run the Shortcut


Now, whenever this Shortcut runs, it will send the message directly to the selected contact or group without requiring you to tap the send button in WhatsApp.


Final Thoughts


This method provides a seamless way to automate WhatsApp messaging, making it useful for reminders, alerts, or scheduled messages. If you need to send messages at specific times, consider combining this Shortcut with the Automation feature in the Shortcuts app.


Try it out and let me know how it works for you!


Labels:

Comments

Post a Comment

Popular posts from this blog

Ignoring Cancel Signals and Continuing Processing in a Spring WebFlux App

In a  Spring WebFlux  application, request processing is reactive, meaning that when a client  cancels a request  (e.g., due to a timeout or manual cancellation),  Spring immediately stops execution  by propagating a  cancel signal  in the reactive stream. However, in some cases,  we want to ensure that processing continues , even if the client disconnects. This is especially important when: Database updates  or  external API calls  must be completed to avoid an inconsistent state. Long-running operations should  not be interrupted . Logging, auditing, or side effects must still be processed. How to Keep Processing After a Cancel Signal To  decouple  HTTP request processing from the  application logic , we can use the  .cache()  operator. This ensures that the  execution continues , even if the client drops the connection. Understanding  .cache()  in Reactor <T> Flux...
Post a Comment
Read more

Use Your Own Router When Your ISP Router Doesn’t Support Bridge Mode

Many internet service providers (ISPs) require you to use their provided router, and in some cases, these routers don’t support bridge mode. This can be frustrating if you want to use your own high-performance router for better speed, security, or customization. A common workaround is to place your second router in the DMZ (Demilitarized Zone) of the ISP-provided router. In this guide, I’ll explain how to set up your ISP’s router to work with your own router while minimizing issues. How This Works 1. Setting Up DMZ Mode Since your ISP’s router does not support full bridge mode, we’ll use DMZ to forward all traffic to your second router. This allows your better router to handle most of the network management, firewall, and routing tasks. 2. Dealing with Double NAT What is Double NAT? Your ISP’s router continues to perform NAT (Network Address Translation) for devices connected to it. Your second router will also perform NAT for devices connected to it. This is called double ...
Post a Comment
Read more