Refiner StrawberryEvery identify user in Refiner, pulled into one sheet
2 read operations and no writes: a companion can track event and identify user in Refiner and hand back the identify users with the source on each row.
Open the identify user. Check it against something else. Write the change. Move to the next one. That is the Refiner afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing changed until you say so.
What it can do is exactly what Refiner exposes to an account you authorise and nothing beyond it: 2 operations, 2 reads and no writes. In practice that means it can track event and identify user, and work across the identify users and track events.
The Refiner API stops at Refiner. 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.
Which Refiner identify users does a companion see?
All 2 operations read.
Your account, not a guess at it: a companion can track event and identify user, and the full list below is the whole list, with nothing inferred from Refiner's documentation.
The identify users are what most of this inventory is about, alongside the track events. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of Refiner admin becomes a queue you review.
- Track Event
- Identify User
It can track event. Can it act on what it finds?
Through the screens you already use.
Refiner exposes no write operation to a connected account, so a companion drives Refiner in the session you are already signed into instead, filling the same forms you would to move a identify user, and anything consequential stops for an approval card before it happens.
That is the ordinary case rather than the exception. Most of what an identify user in Refiner touches has no API pointed at it, and a companion is useful precisely because it does not need one.
Does the identify user sweep have to be asked for every time?
Yes.
Saved as a routine, the Refiner identify users 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 research and analysis playbook catalogues the other recurring shapes of the responses, the Refiner identify users 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