ActionUpstashUpdated September 2026
How do I read a value from Upstash Redis?
Short answer: You can get key in Upstash by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Upstash Get Key action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Key key | string | Required | Key |
Sample request
{"key": "{{trigger.key}}"}
Returns
{"result": "stored_value"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Get Key.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get Key.
What does the Get Key action do in Upstash?
Reads a value by key from an Upstash Redis database. Use as lightweight serverless state, rate-limit counter, or cache for cross-workflow data.
What inputs does Get Key require?
Required: Key. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Upstash returns an error?
The run history shows the failed step with its input and the error message Upstash returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get Key support batch operations?
Run Get Key inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Upstash's rate limits.
More actions