Google Memorystore for Redis
Manage Memorystore Redis instances: list, export, failover (Google OAuth2).
OCNORA ships 7 typed Google Memorystore for Redis operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Memorystore for Redis
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Memorystore for Redis
Operations, grouped by what they do to your data.
Create and send 1
Read and search 3
Update 1
Delete and cancel 1
Other operations 1
A sample Google Memorystore for Redis workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Memorystore for Redis trigger is needed.
- 2Export Instancememorystore.export_instanceExport a Redis instance RDB snapshot to a gs:// URI (returns the operation).
- 3Create Instancememorystore.create_instanceCreates a Redis instance based on the specified tier and memory size.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 7
- Create InstanceCreates a Redis instance based on the specified tier and memory size.memorystore.create_instance
- Delete InstanceDeletes a specific Redis instance.memorystore.delete_instance
- Export InstanceExport a Redis instance RDB snapshot to a gs:// URI (returns the operation).memorystore.export_instance
- Failover InstanceInitiate a manual failover of a Standard-tier Redis instance.memorystore.failover_instance
- Get InstanceGet a Memorystore Redis instance (host, port, state, full resource).memorystore.get_instance
- List InstancesList Memorystore Redis instances in a region (or all regions with '-').memorystore.list_instances
- Update InstanceUpdates the metadata and configuration of a specific Redis instance.memorystore.update_instance
Google Memorystore for Redis questions
- How does OCNORA authenticate with Google Memorystore for Redis?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Memorystore for Redis?
- 7 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Memorystore for Redis operation I need is not listed?
- Where Google Memorystore for Redis has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Memorystore for Redis?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Memorystore for Redis calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Memorystore for Redis workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.