IFTTT vs Pokobot
A wire between two services, or something you can talk to.
IFTTT made automation approachable. One trigger, one action, a sentence you can read out loud: if this, then that. For turning the porch light on around sunset or logging your workouts to a spreadsheet, it is still hard to beat, and the simplicity is the whole reason it works.
People reach for it for reminders too, because a date and time trigger is right there in the list. It will do the job in the loosest sense. It will also be roughly on time, unable to hold a conversation about what it is reminding you of, and at some point it will stop, and nothing will tell you.
The short answer
IFTTT is a wire between two services and Pokobot is a conversation. That difference decides most of this. An applet has no memory: it fires, and that is the end of it, so there is no way to ask what is pending, no way to say “actually make it seven”, and no way to have it keep chasing until you say the thing is done. It is also polled rather than scheduled, so a nine o'clock reminder is a reminder somewhere around nine, which is fine for a thermostat and less fine for medication. And applets decay quietly when a connection expires or a service changes, producing no output at all, which is indistinguishable from a week where nothing needed doing. For lights, sensors and logging, IFTTT is the right tool and this is not. For reminders it is a wire being asked to do a job that needs state.
Head to head
| IFTTT applets | Pokobot | |
|---|---|---|
| Lights, sensors and devicesIFTTT applets | Its actual home turf, and genuinely good at it | Nothing. It has no idea your house exists |
| SimplicityIFTTT applets | One trigger, one action, readable in a sentence. Almost no learning curve | Also simple, but it is only ever reminders |
| Connecting consumer servicesIFTTT applets | Hundreds of them, and a free tier that covers a few applets | Google Calendar. That is the entire integration list |
| What it costsIFTTT applets | Free for a small number of applets, and Pro is inexpensive | 7 days free, then a small subscription (from ₹59/month in India) |
| Arriving at the actual minutePokobot | Triggers are polled, so “9pm” means somewhere around 9pm | Scheduled. 9pm means 9pm |
| Reaching WhatsAppPokobot | No WhatsApp service. You are building it out of webhooks and a provider | WhatsApp is what the product is |
| Changing your mindPokobot | Go and edit the applet. There is nothing to reply to | Say “actually make it 7pm” and it follows along |
| Seeing what is pendingPokobot | Applets are wires, not a list. There is nothing to check | Send “list” and read what is coming |
| Noticing that it stoppedPokobot | A dead applet sends nothing, and silence looks like a quiet week | Someone is paid to notice that messages have stopped going out |
Keep IFTTT for what it was built for
None of this is an argument against IFTTT generally. It is very good at the thing it was designed for, which is joining consumer services together with as little ceremony as possible, and it is cheap enough to be worth having around.
For all of the following, use IFTTT and ignore everything else on this page.
- Anything with hardware in it: lights, plugs, thermostats, doorbells, sensors.
- Logging and archiving. Save this to a sheet, back that up, file it somewhere.
- Joining two consumer apps that will never officially support each other.
- Anything where being a few minutes late genuinely does not matter.
- Doing all of that for free or close to it.
An applet cannot hold a conversation
This is the structural gap, and it is not a missing feature so much as a missing concept. An applet is stateless. It fires when the trigger says so, it does the action, and it remembers nothing, because remembering was never in the model.
Reminders need state constantly, and you notice the moment you try. You want to know what is coming up, which means somewhere holding a list. You want to move one to seven o'clock without opening a settings page. You want to cancel the third one. You want it to keep going until you say it is handled, rather than firing once into the void. None of that is expressible as a wire between two services.
In a chat all of it is just replying. That is also what makes fast repeats workable: 35.8% of the reminders set here go off more than once a day, and every one of them can be stopped, moved or windowed by sending a sentence rather than by editing an automation.
listactually make it 7pmcancel 2Roughly on time is a different product
IFTTT checks its triggers on a schedule rather than firing at an exact instant, so an applet set for nine o'clock runs at some point after nine. Usually not long after. Sometimes noticeably later, and the delay is not something you control.
For most of what IFTTT does this is completely irrelevant. Nobody minds if the porch light comes on four minutes after sunset, or the workout gets logged at twenty past. The design is right for the workload.
Reminders are the workload where it stops being right, because the moment is the product. A medication reminder that drifts is a medication reminder you start ignoring, and a nudge that arrives after the meeting started is not a nudge, it is a note about something you missed.
There is no WhatsApp service
Worth being concrete, because this is where most people trying this actually get stuck. IFTTT does not have a WhatsApp action. You cannot pick it from the list, because it is not in the list.
The route people end up taking is a webhook out to a provider that can send WhatsApp messages, which means an account with that provider, a verified sender, and approved message templates before anything can be delivered. At which point you have built a small integration and IFTTT is one component in it rather than the solution.
The alternative is to have the applet push a notification through IFTTT's own app instead, which works and lands you back in the notification tray, which is the surface this whole product exists to get out of.
The applet that stopped in March
Automations rot. A service connection expires and wants re-authenticating. An app changes something on its side. A service gets deprecated and the applets that used it are quietly archived. All of this is normal and none of it is really IFTTT's fault.
What makes it dangerous specifically for reminders is the shape of the failure. A broken applet does not do something wrong, it does nothing, and nothing is exactly what a week with no obligations also looks like. There is no error in front of you, no red mark, no message that failed to send.
So the discovery mechanism is missing something important, and then working backwards. People often find that the applet had been dead for weeks, and that every reminder they thought was handled in that period was never sent at all. That is a worse outcome than not having set it up in the first place, because in the meantime you stopped keeping track yourself.
Where each one belongs
IFTTT is for wiring services together, where both ends are systems and the timing is approximate. That is a real and useful job and it is not one a chat bot can do at all.
Reminders sit on the other side of the line because they are a small ongoing conversation rather than a one-way trigger. They get postponed, cancelled, listed, repeated and adjusted, and every one of those is a reply rather than a config change.
If you already have applets doing sensible automation work, leave every one of them alone. The only ones worth replacing are the ones you built to nag yourself, which are the ones most likely to have quietly stopped anyway.
Questions, answered
- Can IFTTT send WhatsApp messages?
- Not directly. There is no WhatsApp service in IFTTT to choose. Getting there means a webhook out to a provider that can send on WhatsApp, which needs its own account, a verified sender and approved templates. Most people who try end up sending an IFTTT app notification instead, which puts the reminder back in the notification tray.
- Are IFTTT reminders on time?
- Approximately. Triggers are polled rather than fired at an exact instant, so a nine o'clock applet runs at some point after nine, usually soon after and sometimes not. That is a sensible design for lights and logging and a poor one for anything where the specific minute is the point.
- Why did my IFTTT applet stop working?
- Usually a connection that expired and needs re-authenticating, or a service that changed or was deprecated, in which case applets using it get archived. The hard part is that a stopped applet produces silence rather than an error, so most people find out by missing something rather than by being told.
- Can I cancel or reschedule an IFTTT reminder?
- Only by editing the applet, because there is nothing to reply to. An applet has no memory of what it has sent and no list of what is coming, so there is no equivalent of “move that one to seven” or “cancel the second one”. In a chat those are just messages.
- Is IFTTT cheaper than a reminder bot?
- Yes, and that is a fair reason to try it first. The free tier covers a few applets and Pro is inexpensive. What you are trading is punctuality, the ability to change a reminder by replying, and any warning at all when the thing has stopped running.
- Should I delete my applets?
- No. Anything doing real automation, particularly anything touching devices, should stay exactly as it is. The ones worth reconsidering are the applets built purely to remind you of something, which are both the worst fit for the model and the ones most likely to have already stopped without your noticing.