Store record in default store in Apify
A documented Apify operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Store record in default store
- PUTChanges data · Default key-value store
api.apify.com/v2/actor-runs/{runId}/key-value-store/records/{recordKey}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Apify operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Apify operations
- Create webhookPOST · changes data
- Create schedulePOST · changes data
- Run task synchronously and get dataset itemsPOST · changes data
- Create ActorPOST · changes data
- Create datasetPOST · changes data
- Create request queuePOST · changes data
- Create key-value storePOST · changes data
- Store record (POST)POST · changes data
Questions
- Can HumDay store record in default store in Apify?
- Yes. This operation is published in Apify's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Apify data?
- Yes — this is a PUT operation, so it changes something in Apify. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Apify account.
Where this came from
Read from the API description Apify publishes themselves at api.apify.com/v2/openapi.json. The description above is the provider’s own wording, not ours.