Datastore
Datastore Wrk Actions read and write account-level storage that persists across Launches: environment variables, table rows, and queues.
What it is
Unlike data that flows through a single Launch in the Data Library, values in Datastore remain available until you change or delete them. These Wrk Actions let a running Wrkflow create, retrieve, update, and delete that shared storage.
Good for
- Shared configuration (API base URLs, feature flags) via environment variables
- Structured records that multiple Wrkflows create, query, and update
- Handing off work items between Wrkflows with Datastore queues
- Logging results or maintaining mapping tables at scale
What it does
- Environment variables: create, retrieve, and update named values available account-wide
- Tables: create, retrieve, query, update, import, and delete rows
- Queues: add, retrieve, search, update, and delete queue items with locking and status lifecycle
For one-time transforms that do not need to persist, see Data Manipulation. For platform orchestration, see Wrkflow Tools.
Go deeper
Platform tour
- Datastore: environment variables, tables, and queues in the UI
Reference
Related concepts
- Data Library Items: Launch-scoped data vs account-level Datastore