Integration

Lamina + Google Drive

Deliver run outputs into a Drive folder with brand-locked filenames, labels, and team-shared permissions.

The Lamina + Google Drive integration delivers generated assets and brand-locked variant sets into a Drive folder using the Drive v3 API with OAuth. lamina.distribute creates files, applies labels, and shares the folder with your team — so creative ops, marketing, and agencies access AI generations without an extra DAM.

What you can do

  • Write generated assets to a Drive folder via the Drive v3 API
  • Apply Drive Labels (campaign, brand, run id, score) for downstream filtering
  • Generate filename templates from brief, brand, and ratio (e.g., homestead-ss26-hero-16x9-v2.png)
  • Share the destination folder with editor or commenter permissions
  • Append a metadata JSON sidecar so external tools can re-hydrate run context

Setup

  1. 1

    Authorize Lamina against your Google Workspace

    OAuth requests drive.file scope so Lamina can only touch files it creates or is granted access to.

  2. 2

    Pick a destination folder and labels

    Choose the Drive folder for outputs and select / create Drive Labels for campaign and brand metadata.

  3. 3

    Distribute a run

    Call lamina.distribute with target { kind: 'gdrive', folderId, filenameTemplate, labels, sharePolicy }.

Example

gdrive-distribute.ts

await lamina.distribute(shoot.assets, {
  targets: [{
    kind: "gdrive",
    folderId: "1A2B3C...",
    filenameTemplate: "{brand}-{campaign}-{role}-{ratio}-v{n}.{ext}",
    labels: { campaign: "ss26", brand: "homestead" },
    sharePolicy: "workspace-edit",
  }],
});

How it works

Lamina uses the Drive v3 API to upload assets, apply Drive Labels, and set sharing permissions. Filenames are templated against brief, brand, and ratio so a folder full of generations stays sortable. A metadata sidecar (run id, brand-fit score, seed, model graph) accompanies each file so any external tool — a Sheets-based review tracker, a Looker dashboard — can re-hydrate context.

When to use it

Use this integration when your team works out of Drive (most agencies do) and a separate DAM is overkill. Pairs well with Slack notifications: distribute to Drive, post a thread, approve in-channel.