# Upload OVH Object Store

<!-- meta: type=ovh-upload-object-storage; location=Cloud › OVH; category=Step (action); platforms=Joomla and WordPress (where applicable) -->

## Overview

Upload OVH Object Store is a **Step (action)** in **Cloud › OVH**. Uploads an object to OVHcloud Object Storage (S3-compatible PutObject).

When the flow reaches this step, JOrchestrator executes **Upload 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

Upload 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 **Upload OVH Object Store** to a flow:

- Automate "Upload 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 → **Upload OVH Object Store** → **Send Email** or CMS update
2. **Scheduled trigger** → **Upload OVH Object Store** → **Debug** (while testing) → production action

## How to set it up

S3 access key, secret, and region from your CMS plugin settings → OVH. Body as plain text or base64.

## Good to know

Create S3 credentials in the OVH control panel for the target region (e.g. gra, rbx, sbg).

## Properties panel

The designer shows these tabs for this node:

| Tab | Purpose |
|-----|---------|
| **Info** | Plain-language description and output payload fields for downstream steps |
| **General** | Canvas label and read-only node ID |
| **AI** | Optional assistant to help draft settings from plain language |
| **Design** | Node-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 key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `_nodeId` | Node ID | `node-id` | No | — | — |
| `_payloadFields` | Available Fields | `payload-panel` | No | — | — |

### User-configured — General tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `label` | Label | `text` | No | — | Node label |

### User-configured — Design tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `bucket` | Object Storage container | `payload-text` | **Yes** | — | my-container |
| `objectKey` | Object key | `payload-text` | **Yes** | — | path/to/file.json |
| `body` | Body | `textarea` | **Yes** | — | File content or {{node_id.field}} |
| `contentEncoding` | Body encoding | `select` (`text` \| `base64`; default: `text`) | No | — | — |
| `contentType` | Content-Type | `select` (`application/octet-stream` \| `application/json` \| `text/plain` \| `text/html` \| `text/csv` \| `text/xml` \| `application/xml` \| `application/pdf` \| `application/zip` \| `application/gzip` \| `image/jpeg` \| `image/png` \| `image/gif` \| `image/webp` \| `image/svg+xml` \| `video/mp4` \| `audio/mpeg` \| `audio/wav`; default: `application/octet-stream`) | 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
`{{upload_ovh_object_store.success}}`.

| Field key | Type | Description |
|-----------|------|-------------|
| `success` | boolean | Whether the operation completed successfully. |
| `bucket` | string | Cloud storage bucket name. |
| `objectKey` | string | Object key/path within the bucket. |
| `url` | string | Public HTTP URL to a resource on the site. |
| `etag` | string | Entity tag (checksum) from cloud storage. |
| `bytesWritten` | number | Number of bytes written to storage. |
| `message` | string | Human-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.
- **Body** (`body`) must be filled before the flow can be saved.

## Related nodes

Other steps in the same area of the palette:

- **List OVH Object Store** (`ovh-list-object-storage`) — Cloud › OVH
- **Retrieve OVH Object Store** (`ovh-retrieve-object-storage`) — Cloud › OVH