OtherReal-timeUpdated May 2026

Upstash

Upstash serverless Redis and Kafka

Upstash is the serverless Redis (and Kafka) database — pay-per-request pricing model (vs traditional Redis which charges for provisioned capacity). Used by serverless/edge workloads where you want Redis without managing a Redis instance. Tiny Command exposes two actions, no triggers: Get Key (fetch a value by key — string, list, hash, etc. depending on key type), Set Key (set a value with optional TTL expiry). The connection uses an Upstash database URL + REST token (Upstash's REST API wraps Redis commands as HTTP). The REST-API-over-Redis design is the differentiator — most Redis clients use the binary RESP protocol over TCP, which is awkward for serverless functions. Upstash's HTTP API works from anywhere HTTP works, including Cloudflare Workers, Vercel Edge Functions, and Tiny Command workflows. For "Redis from serverless without connection-pool headaches", Upstash is the right pick.

Connect Upstash

0triggers

2actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Upstash can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Get Key	Reads a value by key from an Upstash Redis database. Use as lightweight serverless state, rate-limit counter, or cache for cross-workflow data.	1 fields	View →
Set Key	Sets a key/value pair in Upstash Redis with optional TTL. Pair with Get Key to share state between workflow runs or to build a poor-man's feature flag.	3 fields	View →

Recipes

Pre-built Upstash workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Upstash → Slack alerts

AI-triage every Upstash event, ping the right channel only when it matters.

Upstash → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Upstash → Notion database

Turn Upstash into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Upstash once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Upstash field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Upstash integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Upstash to Tiny Command?

Open the Tiny Command workflow builder, drop in a Upstash node, and click Connect. Authorize Upstash once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Upstash triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Upstash today. Use Tiny Command's universal Webhook or Schedule trigger to start Upstash workflows, then run any Upstash action you need.

What Upstash actions can I run from a workflow?

2 Upstash actions are available out of the box, covering other operations like "Get Key". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Upstash integration real-time?

Upstash actions execute synchronously inside your workflow. Tiny Command waits for Upstash's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Upstash with Tiny Command?

No. Every Upstash trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Upstash API endpoint directly.

How much does the Upstash integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Upstash integration itself has no per-app surcharge.