Loops.so StrawberrySomeone still has to update contact. It does not have to be you
It reads every contact your Loops.so account holds, drafts the changes that follow, and hands you a card for each one before a single contact moves.
Open the contact. Check it against something else. Write the change. Move to the next one. That is the Loops.so afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a contact until you approve it.
What it can do is exactly what Loops.so exposes to an account you authorise and nothing beyond it: 8 operations, 3 reads and 5 writes. In practice that means it can update a contact, send a transactional email and send an event, and work across the contacts, custom fields and events.
The Loops.so API stops at Loops.so. 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.
Can it list mailing lists on its own?
3 of the 8 operations are reads.
Your account, not a guess at it: a companion can list mailing lists, list custom fields and find a contact, and the full list below is the whole list, with nothing inferred from Loops.so's documentation.
The contacts are what most of this inventory is about, alongside the custom fields. A companion can hold all 8 of these operations and forty open tabs in the same pass, which is how an afternoon of Loops.so admin becomes a queue you review.
- List Mailing Lists
- List Custom Fields
- Find Contact
What happens before it can update contact?
All 5 write operations wait for you.
A companion can update a contact, send a transactional email and send an event, and each one is staged on an approval card first: you see the contact, the field and the new value before it lands in Loops.so.
Nothing in Loops.so is sent, changed or deleted on your behalf without that click, and a rejected card leaves the contact exactly as it was. The gate is the same one on every surface, described at security.
- Update Contact
- Send Transactional Email
- Send Event
- Delete Contact
- Create Contact
Can it update contact on a schedule?
Yes.
Saved as a routine, the Loops.so contacts 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 messages, the Loops.so contacts 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