Node reference

Retrieve OVH Object Store for Joomla and WordPress

Retrieve OVH Object Store is a Step (action) in Cloud › OVH. Downloads an object from OVHcloud Object Storage (S3-compatible GetObject).

Node reference

Overview

Retrieve OVH Object Store is a Step (action) in Cloud › OVH. Downloads an object from OVHcloud Object Storage (S3-compatible GetObject).

When the flow reaches this step, JOrchestrator executes Retrieve OVH Object Store against your linked site or an external integration, using the field values you set on General and Design. Downstream steps can read the output payload fields defined for this node.

Why use this node

Retrieve OVH Object Store is a action step in the Cloud › OVH group. Action steps run in the middle or end of a flow. They perform work on your CMS, call external services, or transform data for the next step.

Typical reasons teams add Retrieve OVH Object Store to a flow:

  • Automate "Retrieve OVH Object Store" as part of a larger Joomla or WordPress workflow
  • Replace manual ovh work with a repeatable, logged flow step
  • Chain with triggers, logic, and messaging nodes on the same canvas

Example workflows

Common patterns on the canvas:

  1. Trigger or Webhook → upstream steps → Retrieve OVH Object Store → Send Email or CMS update
  2. Scheduled trigger → Retrieve OVH Object Store → Debug (while testing) → production action

How to set it up

Bucket, key, and region; credentials from Node Configuration → OVH.

Good to know

Large objects increase flow runtime — pair with Upload Media using {{node_id.body}} when bodyEncoding is base64.

Properties panel

The designer shows these tabs for this node:

TabPurpose
InfoPlain-language description and output payload fields for downstream steps
GeneralCanvas label and read-only node ID
AIOptional assistant to help draft settings from plain language
DesignNode-specific configuration fields

System (automatic — not edited by the user)

These fields are managed by the designer or runtime — you do not type into them directly:

Property keyLabelTypeRequiredVisible whenNotes
_nodeIdNode IDnode-idNo——
_payloadFieldsAvailable Fieldspayload-panelNo——

User-configured — General tab

Property keyLabelTypeRequiredVisible whenNotes
labelLabeltextNo—Node label

User-configured — Design tab

Property keyLabelTypeRequiredVisible whenNotes
bucketObject Storage containerpayload-textYes—my-container
objectKeyObject keypayload-textYes—path/to/file.json
bodyEncodingResponse body encodingselect (auto | text | base64; default: auto)No——

CMS site configuration (not on this node's properties panel)

Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under Node Configuration, not per step on this node. Link the flow to a domain before testing CMS-backed fields.

Output payload fields

After this step runs, later nodes can reference these fields using placeholders such as {{retrieve_ovh_object_store.success}}.

Field keyTypeDescription
successbooleanWhether the operation completed successfully.
bucketstringCloud storage bucket name.
objectKeystringObject key/path within the bucket.
bodystringFile bytes — base64 when Body encoding is auto/base64. Use {{node_id.body}} in Upload Media.
bodyEncodingstringHow body is encoded: base64 or text.
contentTypestringMIME type from OVH Object Storage.
etagstringEntity tag (checksum) from cloud storage.
byteLengthnumberSize of retrieved content in bytes.
messagestringHuman-readable status, error, or result summary.

Validation rules

  • Object Storage container (bucket) must be filled before the flow can be saved.
  • Object key (objectKey) must be filled before the flow can be saved.