State Management
Persistent Key-Value storage that works across Triggers, Steps, and Functions
State is persistent key-value storage that works across all your Triggers, Steps, and Functions. Set data in one Trigger, read it in another. Works across TypeScript, Python, and JavaScript.
How It Works
State organizes data into groups. Each group can hold multiple items with unique keys.
Think of it like folders and files:
- groupId = A folder name (like
orders,users,cache) - key = A file name inside that folder
- value = The actual data
State Methods
| Method | What it does |
|---|---|
state.set(groupId, key, value) | Store an item in a group. Returns StreamSetResult with new_value and old_value |
state.get(groupId, key) | Get a specific item (returns null if not found) |
state.list(groupId) | Get all items in a group as an array |
state.delete(groupId, key) | Remove a specific item |
state.clear(groupId) | Remove all items in a group |
state.update(groupId, key, ops) | Atomic update with UpdateOp[] |
Atomic Updates
Use state.update() for atomic operations on state items. This is useful when you need to increment counters, update specific fields, or perform multiple changes atomically.
Available Update Operations
| Operation | Description | Example |
|---|---|---|
set | Set a field to a value | { type: 'set', path: 'name', value: 'New Name' } |
increment | Increment a numeric field | { type: 'increment', path: 'count', by: 1 } |
decrement | Decrement a numeric field | { type: 'decrement', path: 'stock', by: 1 } |
Real-World Example
Let's build an order processing workflow that uses state across multiple Steps.
Step 1 - API receives order:
Step 2 - Process payment:
Step 3 - View all orders (Cron job):
When to Use State
Good use cases:
- Temporary workflow data - Data that's only needed during a flow execution
- API response caching - Cache expensive API calls that don't change often
- Sharing data between Steps - Pass data between Steps without enqueuing it in events
- Building up results - Accumulate data across multiple Steps
Better alternatives:
- Persistent user data - Use a database like Postgres or MongoDB
- File storage - Use S3 or similar for images, PDFs, documents
- Real-time updates - Use Motia Streams for live data to clients
- Large datasets - Use a proper database, not state
Remember
- Organize data using groupId (like
orders,users,cache) - Each item needs a unique key within its groupId
- Use
list(groupId)to retrieve all items in a group state.set()returns{ new_value, old_value }(StreamSetResult)- Use
state.update()for atomic operations like increment/decrement - State works the same across TypeScript, Python, and JavaScript
- Clean up state when you're done with it
- Use databases for permanent data, state for temporary workflow data
Project Structure
Learn about Motia's project structure, file organization, and automatic step discovery system for building scalable workflow applications.
Real-time Streams
Push live updates from your backend to connected clients without polling. Perfect for AI responses, chat apps, and long-running tasks.