Apify Strawberry

Someone still has to set key-value store record. It does not have to be you

Hand a companion the outcome. It reads the Apify (OAuth) key-value store records, does the 7-operation version of the job, and stops for your click on anything that changes a record.

Open the key-value store record. Check it against something else. Write the change. Move to the next one. That is the Apify (OAuth) afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a key-value store record until you approve it.

What it can do is exactly what Apify (OAuth) exposes to an account you authorise and nothing beyond it: 7 operations, 3 reads and 4 writes. In practice that means it can set key-value store record, run a task and run a task synchronously, and work across the key-value store records, actors and dataset items.

The Apify (OAuth) API stops at Apify (OAuth). 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 key-value store records come from?

3 of the 7 operations are reads. Your account, not a guess at it: a companion can scrape single URL, get key-value store record and get dataset items, and the full list below is the whole list, with nothing inferred from Apify (OAuth)'s documentation.

The key-value store records are what most of this inventory is about, alongside the actors. A companion can hold all 7 of these operations and forty open tabs in the same pass, which is how an afternoon of Apify (OAuth) admin becomes a queue you review.

  • Scrape Single URL
  • Get Key-Value Store Record
  • Get Dataset Items

Which key-value store records wait for your approval?

All 4 write operations wait for you. A companion can set key-value store record, run a task and run a task synchronously, and each one is staged on an approval card first: you see the key-value store record, the field and the new value before it lands in Apify (OAuth).

Nothing in Apify (OAuth) is sent, changed or deleted on your behalf without that click, and a rejected card leaves the key-value store record exactly as it was. The gate is the same one on every surface, described at security.

  • Set Key-Value Store Record
  • Run Task
  • Run Task Synchronously
  • Run Actor

What does the recurring key-value store records pass look like?

Yes. Saved as a routine, the Apify (OAuth) key-value store records 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 engineering admin, the Apify (OAuth) key-value store records sweep among them, and finished runs are published at real runs.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

Yes. Connect your Apify (OAuth) account and a companion works 7 operations in it, with every change staged for your approval. You authorise the connection yourself and the credential is held encrypted where Strawberry never receives it.

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

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide