Redis JSON Documents connector.

Read, write and delete JSON documents or fixed JSON paths using Redis JSON commands through one bounded client connection per action.

Download connector See all connectors

Connector download

Download Redis JSON Documents

Versioned ZIP for your CXFabric tenant.

Register the ZIP in your tenant, or add a new version if the connector is already installed.
Create or select a credential if the action requires one.
In a Draft flow, add an available action, choose its version, connect it, and map inputs.
Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version history

v0.1.0.1Latest · 2026-10-05 · Implemented source
Uses exactly one connector IIFE with explicit named operation functions. Actions, inputs, credentials, results, deadlines, ID and UUID are unchanged; earlier ZIP bytes are preserved.
Full release notes View download
v0.1.0.0Earlier · 2026-10-05 · Implemented source
Read, write and delete JSON documents or fixed JSON paths using Redis JSON commands through one bounded client connection per action. New independent registration; legacy flows require deliberate remapping. Hosted import and live service validation remain pending.
Full release notes View download

Included in this version

Implemented in v0.1.0.1. Use a separate flow trigger; no webhook trigger is included.

Read a fixed JSON path; missing keys return found false.

Set one JSON object at a fixed path after explicit confirmation.

Delete a selected JSON path after explicit confirmation.

Vendor API

Implementation considerations

Supported scope: Read, write and delete JSON documents or fixed JSON paths using Redis JSON commands through one bounded client connection per action.
Select a Redis credential with endpoint hostname, port, username when required, and password. Enable TLS for hosted deployments. The server must implement JSON.GET, JSON.SET and JSON.DEL. Fixed paths select bounded document areas; verify that selected responses fit the documented limit.
No reconnects, background connection pool, arbitrary commands or wildcard JSON paths. Set and delete require confirmation. The native driver receives a response before the connector checks the 1 MiB response limit; use only trusted servers and bounded document paths. Whole connect/command deadlines destroy the owned connection. A timed-out write can still have been applied; reconcile before retrying.
New independent connector registration. Existing legacy flows require deliberate action and credential remapping. Hosted import and live service validation remain pending.

Support

Tell us what you need to connect or change.