ConnectWyze

Creative Automation

ConnectWyze Creative Automation turns a structured data source into a library of branded images — one per item, across every template and artboard size you configure.

What it is

Creative Automation connects three building blocks:

  • Data Source — a live dataset (API endpoint, CSV, manual table, merged dataset, or background-removal processor) that produces one row per item you want to render.
  • Template — the visual canvas (layout, text layers, image layers, brand colours) that defines what a finished image looks like.
  • Workflow — the bridge that maps data source fields to template variables and runs the render.

When you run a workflow, ConnectWyze iterates over every active item, populates the template variables with that item's data, renders a pixel-perfect image via headless Chromium, and stores the result in your workspace storage. Re-running the workflow updates only items whose data has changed.

When you'd use it

  • You manage a product catalogue of hundreds or thousands of SKUs and need a consistently branded image for each one.
  • Your marketing team publishes new offers daily and wants ready-to-use social assets generated automatically.
  • You need the same creative in multiple sizes (Square, Story, Banner) without maintaining separate templates.
  • Your data lives in an external system (e-commerce API, Google Sheets, CSV export) and you want image generation to trigger automatically when the data source updates.
  • You want to A/B test two template designs across your entire catalogue.

Quick start (user)

End-to-end in five steps

  1. Create a data source at /dashboard/creative/data-sources. Choose the type that matches your dataset (API, CSV, Manual, Merged, or Background Removal). Configure the source and trigger your first sync to populate items.
  2. Create a template at /dashboard/creative/templates. Add text and image layers, and set Variable names on the layers you want populated from data source fields.
  3. Create a workflow at /dashboard/creative/workflows. Select the data source, select the template, and open the Field Mapping panel to map each template variable to the matching field.
  4. Click Run to start a generation run. Progress appears in Runs (/dashboard/creative/runs).
  5. When the run finishes, open Creatives (/dashboard/creative/creatives) to browse, download, or export the generated images.

Pipeline overview

Source (API / CSV / Manual / Merged / BG Removal)
    │
    ▼
Data Source ───────────────────────────────────────────
    │  items: [{ externalId, data: { col_a, col_b, … } }]
    ▼
Workflow
    │  field mapping: col_a → layer variable "headline"
    │  field mapping: col_b → layer variable "product_image"
    │  (optional) conditional rules → pick template per item
    ▼
Template(s) + Artboard(s)
    │
    ▼  Playwright + Sharp render engine
GeneratedImage[]
    └── stored in workspace storage (R2 / S3 / GCS)
         URL written to Creatives and export feeds

Core concepts

Concept Summary Docs
Data Source Holds items, schema, tags, and media. Data Sources
Data Source Merging Combine two or more data sources by joining on a shared key. Data Source Merging
Template Visual canvas with named variable slots on each layer. Templates
Workflow Maps data source → template; runs and schedules generation. Workflows
Runs & Creatives Monitor active runs and access generated images. Runs and Creatives
Generate API Render a single image from a template via REST API. API Keys and Generate API
Background Removal Strip image backgrounds before they reach the template. Background Removal

How generated images are stored

Every rendered image is written to your workspace storage (Cloudflare R2 by default; configurable to custom R2, AWS S3, or GCS). Re-running a workflow overwrites images at the same deterministic path for the same item + template + artboard combination. A cache-buster query string forces CDN and browser refresh.

Credits

Each fresh render consumes one credit. Unchanged items are skipped and do not consume credits. Background-removal renders consume one credit per unique source image (identical URLs are served from cache for free). Cache hits on the generate API also cost zero credits.