Google Cloud Memorystore for Memcached
Google Cloud Memorystore for Memcached API is used for creating and managing Memcached instances in GCP (Google OAuth2).
OCNORA ships 6 typed Google Cloud Memorystore for Memcached 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 Cloud Memorystore for Memcached
- 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 Cloud Memorystore for Memcached
Operations, grouped by what they do to your data.
Create and send 1
Read and search 2
Update 2
Delete and cancel 1
A sample Google Cloud Memorystore for Memcached workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Memorystore for Memcached trigger is needed.
- 2Get Instancememorystore_memcached.get_instanceGets details of a single Instance.
- 3Apply Parametersmemorystore_memcached.apply_parametersApplyParameters restarts the set of specified nodes in order to update them to the current set of parameters for the Memcached Instance.
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 6
- Apply ParametersApplyParameters restarts the set of specified nodes in order to update them to the current set of parameters for the Memcached Instance.memorystore_memcached.apply_parameters
- Create InstanceCreates a new Instance in a given location.memorystore_memcached.create_instance
- Delete InstanceDeletes a single Instance.memorystore_memcached.delete_instance
- Get InstanceGets details of a single Instance.memorystore_memcached.get_instance
- List InstancesLists Instances in a given location.memorystore_memcached.list_instances
- Update InstanceUpdates an existing Instance in a given project and location.memorystore_memcached.update_instance
Google Cloud Memorystore for Memcached questions
- How does OCNORA authenticate with Google Cloud Memorystore for Memcached?
- 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 Cloud Memorystore for Memcached?
- 6 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Cloud Memorystore for Memcached operation I need is not listed?
- Where Google Cloud Memorystore for Memcached 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 Cloud Memorystore for Memcached?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Memorystore for Memcached 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 Cloud Memorystore for Memcached 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.