Hand the Zip Archive API compress files to a companion
Zip Archive API exposes 1 operation and a companion can work it: compress files. Anything that changes a record waits for your click.
Open the compress file. Check it against something else. Write the change. Move to the next one. That is the Zip Archive API 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 Zip Archive API exposes to an account you authorise and nothing beyond it: 1 operation, 1 read and no writes. In practice that means it can compress files.
The Zip Archive API API stops at Zip Archive API. 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 Zip Archive API compress files does a companion see?
The only operation there is reads.
Your account, not a guess at it: a companion can compress files, and the full list below is the whole list, with nothing inferred from Zip Archive API's documentation.
The compress files are what most of this inventory is about, alongside the compress files. A companion can hold that operation and forty open tabs in the same pass, which is how an afternoon of Zip Archive API admin becomes a queue you review.
- Compress Files
Nothing writes back. So what moves the compress files?
Through the screens you already use.
Zip Archive API exposes no write operation to a connected account, so a companion drives Zip Archive API in the session you are already signed into instead, filling the same forms you would to move a compress file, and anything consequential stops for an approval card before it happens.
That is the ordinary case rather than the exception. Most of what a compress file in Zip Archive API touches has no API pointed at it, and a companion is useful precisely because it does not need one.
Can the compress files pass run every Monday?
Yes.
Saved as a routine, the Zip Archive API compress files 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 product and engineering playbook catalogues the other recurring shapes of the site work, the Zip Archive API compress files 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