Redis automation with Bizomate
Your own apps already read Redis for caches, counters and queues. Bizomate writes to it from any workflow — set a key with an expiry, count an event, push a job onto a list, publish a message — and reads it back to decide what happens next. Every run leaves a record of what it read and wrote.
At a glance
| Label | Value |
|---|---|
| Plans | Every plan |
| Connect | Host, port and password, or a rediss:// address |
| Starts runs | No trigger — starts from another app, a schedule or a webhook |
| Kind | Connected app · Database |
What a workflow can do with it
Reads the value kept under a key
Keeps a value under a key, for a time if you like
Leave Expires after (seconds) empty and the key never expires. A list or object from an earlier step is kept as JSON.
Removes a key and what it holds
One key, as written; a pattern is not expanded.
Adds to the number kept under a key
By 1 unless you say otherwise; a negative number takes away, and a decimal works too.
Adds a value to one end of a list
Takes the value off one end of a list
The keys that match a pattern
* matches anything. 1,000 keys by default, up to 10,000.
Sends a message to everyone subscribed to a channel
Keeps a value in one field of a hash
Reads one field of a hash
Questions about Redis
Which Redis services work?
Redis Cloud, Upstash, Azure Cache for Redis, Amazon ElastiCache with a public address, or a Redis server of your own — any of them, as long as it is on the public internet.
Can a change in Redis start a workflow?
No. Redis has no trigger in Bizomate. Start the workflow with a schedule, a webhook or another app, and use the Redis steps inside it.
Does Bizomate send admin commands to my server?
No. The steps read and write keys, lists, hashes and channels; admin commands are never sent.
Does it work with a Redis cluster?
Yes. A cluster has only database 0, so leave Database empty. Every node the cluster names is checked first, and one on a private network is refused.