How to connect a Google Cloud Storage bucket

Inwista can write finished transcripts and rendered videos straight into a Google Cloud Storage bucket, using HMAC interoperability keys tied to a service account you control. A good fit when your media workflow already lives on GCP — everything Inwista produces arrives as objects in your own project.

What you'll need

• A GCS bucket Any storage class and region works. Lowercase names without dots keep things simple.
• A service account with bucket access Create a dedicated service account and grant it Storage Object Admin on this bucket only — Inwista needs to list, create and overwrite objects, nothing more, and nothing on the rest of your project.
• HMAC interoperability keys In Cloud Console, go to Cloud Storage → Settings → Interoperability and create an HMAC key for that service account. You'll get an access ID starting with GOOG and a secret — the secret is shown once, so copy it right away.
• Inwista administrator + subscription Integrations are managed by workspace administrators and included in every paid plan.

Connect the bucket

In My workspace → Integrations, click Connect on the Google Cloud Storage card and enter the HMAC access id (the GOOG… value), the HMAC secret and the Bucket name.

Before saving anything, Inwista performs a signed list request against the bucket to confirm the keys and bucket match — misconfigured permissions surface immediately, not at your first delivery. Verified credentials are stored encrypted at rest.

Object organisation

Output lands under a Inwista/ prefix, organised per project: the current files live at Inwista/{project name}/ and are replaced in place on re-delivery (each write creates a new object generation, so bucket versioning works with it if you've enabled it). With Keep delivery history on, every delivery additionally writes a timestamped copy under revisions/ inside the project prefix.

Formats and file naming are configured under Manage — pick any combination of SRT, VTT, TTML, HTML, CSV, DOCX and PDF, and shape names with the project, date and language template variables.

Automating deliveries

The two switches in the integration settings — Deliver new transcripts automatically and Deliver video exports automatically — turn the bucket into a live sink for everything Inwista produces. For one-off pushes, select Google Cloud Storage in the export dialog's Save to selector instead.

Like S3, this integration is delivery-only: source media comes into Inwista via upload or the consumer cloud integrations.

Disconnecting and key rotation

Disconnect any time from Manage — existing objects stay untouched. To rotate, mint a new HMAC key in the Interoperability settings, reconnect with the new pair, then deactivate and delete the old key in Cloud Console. Deactivating the HMAC key on Google's side immediately severs Inwista's access, independent of anything stored in Inwista.