Redis Connector

Connect Redis so Applied can run controlled Redis commands from Flows.

Use this Connector when a workflow needs low-latency lookup or update access to data stored in Redis.

Common use cases

• Look up cached customer or order context.
• Read feature or entitlement flags stored in Redis.
• Update a key after a customer confirms a change.
• Run operational checks with a narrow command set.

Redis commands can change data immediately. Start with read-only commands and use the narrowest Redis ACL possible.

Before you begin

Before connecting Redis, make sure:

• You know the Redis host and port.
• You know the database number Applied should use.
• You have a Redis username and password, or password-only access for older Redis deployments.
• Your network allows Applied to reach Redis.
• Your team has decided which Redis commands Applied may run.

If your Redis database is private, configure network access before creating the Connector.

Get Redis connection details

For Redis Cloud, connection details are available from the database page.

1. Open the Redis Cloud database.
2. In the Configuration tab, find the endpoint in the General section.
3. In the Security section, copy the username and password.
4. Note whether TLS is required.
5. Note the database number if your setup uses one.

For self-managed Redis, ask the infrastructure owner for the equivalent host, port, database number, username, password, and TLS requirements.

Configure Redis access

Redis ACLs can restrict commands, key patterns, and Pub/Sub channels. Create a dedicated Redis user for Applied when possible.

Examples:

• Use read-only command categories for lookup-only workflows.
• Limit key patterns to the prefixes Applied needs.
• Grant write commands only for workflows that should mutate Redis.
• Avoid broad allcommands or unrestricted key access unless your team has explicitly approved it.

Connect Redis in Applied

1. Open Connectors.
2. Click New.
3. Choose Redis.
4. Enter the host.
5. Enter the port.
6. Enter the database number.
7. Enter the Redis username and password if prompted.
8. Create the connection.

Applied’s Redis resource form uses host, port, username, password, and database configuration.

Validate the connection

After setup:

1. Run PING or another harmless read-only command.
2. Confirm the command succeeds against the intended Redis database.
3. Test one expected lookup command against a non-sensitive key.
4. If write commands are enabled, test with a disposable key first.

Common issues

Applied cannot connect

Check network allowlists, private endpoint routing, host, port, and TLS requirements.

Authentication fails

Confirm the username and password match the Redis user. Redis Cloud commonly uses default as the username unless RBAC has been customized.

Commands fail after connecting

Review the Redis ACL for the connected user. The user may authenticate successfully but lack permission for the command or key pattern.

Provider docs

• Connect to a Redis Cloud database 
• Redis ACLs 
• Redis TLS 

Next steps

• PostgreSQL Database
• Snowflake Connector
• Understanding Connectors