IFTTT StrawberryThe IFTTT events nobody wants to work through
It reads every event your IFTTT account holds, drafts the changes that follow, and hands you a card for each one before a single event moves.
Open the event. Check it against something else. Write the change. Move to the next one. That is the IFTTT afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a event until you approve it.
What it can do is exactly what IFTTT exposes to an account you authorise and nothing beyond it: 2 operations, no reads and 2 writes. In practice that means it can trigger event with values and trigger an event with JSON.
The IFTTT API stops at IFTTT. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Where do the events come from?
In the tab.
IFTTT exposes no read operation to a connected account, so a companion opens IFTTT in the session you are already signed into and reads the screens you would.
The events are what most of this inventory is about, alongside the events. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of IFTTT admin becomes a queue you review.
Which events wait for your approval?
All 2 write operations wait for you.
A companion can trigger event with values and trigger an event with JSON, and each one is staged on an approval card first: you see the event, the field and the new value before it lands in IFTTT.
Nothing in IFTTT is sent, changed or deleted on your behalf without that click, and a rejected card leaves the event exactly as it was. The gate is the same one on every surface, described at security.
- Trigger Event with Values
- Trigger Event with JSON
Can it trigger event with values on a schedule?
Yes.
Saved as a routine, the IFTTT events pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the operations, the IFTTT events sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents