Spectra
Developer ToolsDrive the Spectra asynchronous creative export pipeline, inspecting design projects, layouts, and templates. Agents render creative variants at volume without a designer per asset.
What This Integration Enables
Spectra is not a render endpoint with a template on the end of it. It is a creative production pipeline, and the unit of work is a job rather than a picture. A project carries a layout of frames, an HTML template with its CSS custom properties, locale string tables, theme variable sets, content variable slots, and a version history of saved snapshots. Create Export queues that project across a set of locale and theme combinations, with content variations layered on top, and returns immediately with a queued status. The job moves to processing and then to completed or failed, and the output is a set of artifacts and a zip, not a single URL.
That shape is what makes Spectra the right connector when the same creative has to exist in eleven markets and three themes, and every one of those variants has to be traceable to a version of the design. It is also what makes the run consequential. Agents can discover the whole configuration surface first with Get Export Options, List Locales, List Themes, and List Content Variables, then follow the job with Get Export Status or react to the On Export Finished trigger, then pull artifacts into FlowRunner file storage with Download Export Artifact. FlowRunner's contribution is the moment before the queue: a digital andon cord on the one operation in this connector that commits the whole matrix at once.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A localized campaign rendered across every market in one job
Approved copy for a seasonal campaign arrives as rows in Google Sheets, one row per market. The agent calls Get Export Options to read which locales, themes, and content variable keys the project actually exposes, checks every row against those keys, and resolves the pinned version from List Project History. It states the matrix, gets confirmation, and queues a single export that renders every locale and theme combination. The creative team stops assembling market variants by hand and starts reviewing a variant count.
Artifacts routed onward the moment the pipeline finishes
The On Export Finished trigger fires when a job reaches a terminal state. On completion the agent calls List Export Artifacts, downloads each file into FlowRunner file storage with Download Export Artifact, and uploads the set to the brand folder in Dropbox where the media agency picks it up, then posts the manifest and the variant count to the channel in Slack. On failure the same trigger routes the failure message to the person who owns the project rather than leaving a job that quietly never delivered.
Reproducing a historical creative exactly
A market asks for the version of an asset that ran last quarter, in a size that was not exported at the time. Because List Project History records each saved snapshot with its version number and whether it was a manual save, an autosave, or an export snapshot, the agent renders from that version rather than from the current project state. Get Project Template can archive the exact markup, CSS variables, and locale tables alongside the artifacts, so what shipped stays reconstructable even after the live project has moved on. Where the requested snapshot predates a brand change, the agent flags the discrepancy and asks whether to render the historical design or the current one before it queues anything.
Human-in-Loop Highlight
Create Export is the one-way door on this connector. It queues a job that fans a project out across every locale and theme combination and every content variation supplied, and once it is queued the pipeline runs the whole matrix. A wrong version snapshot, a locale table that was not updated with the new legal line, or a content variation that leaves a required slot empty does not fail loudly on one asset. It produces a complete, well-formed zip in which every variant is wrong, and the correction is a full re-render. So the agent resolves the matrix before it commits and stops: "Project autumn-launch, version 47 saved by R. Ellery on 12 September. 11 locales by 3 themes with 4 content variations comes to 132 variants. Locale fr-CA has no value for the disclaimer_text slot and will render the project default. Queue the export, or hold while that string is added?" Once the answer comes back the job runs unattended, and the On Export Finished trigger brings the artifacts home.
Agent Capabilities
17 actionsProjects
5- List Projects Lists the Spectra design projects the API key can reach, optionally narrowed to a single team, each with its identifier, slug, description, owning team and organization, and timestamps. This is the starting point, because every other operation needs a project identifier.
- Get Project Retrieves a single project by identifier with its name, slug, description, ownership, and timestamps. Used to confirm a project still exists and read its metadata before an export is planned against it.
- Get Project Layout Returns the canvas dimensions and frame layout of a project, listing every frame with its label, description, position, width, and height. Used to know which creative sizes a job will produce before requesting it.
- Get Project Template Returns the HTML template behind a project, optionally with its CSS custom properties, locale string tables, theme variable sets, and content overrides. Used to inspect or archive the exact markup a project renders without waiting for an export job.
- List Project History Lists the saved snapshots of a project in reverse chronological order with a version number, the author, and whether each was a manual save, an autosave, or an export snapshot. Version numbers from this list are what pin an export to a known state.
Assets
2- List Project Assets Lists the assets attached to a project with filename, MIME type, byte size, checksum, uploader, and a content URL. Narrow the result by MIME type prefix or filename search to locate a specific image, font, or data file.
- Get Asset Content Fetches the contents of a text-based project asset with its MIME type and filename. Binary assets such as raster images are read through the content URL from List Project Assets instead.
Export Configuration
4- List Locales Lists the locales configured on a project and marks the primary one. These identifiers are the values used in the locale and theme combinations passed to an export.
- List Themes Lists the themes configured on a project and marks the primary one. Used alongside locales to build the combination set a job will render.
- List Content Variables Lists the content variable slots a project exposes with their keys and default values. These keys are the fields accepted inside content variations, so this is the reference an agent validates incoming data against.
- Get Export Options Returns everything an export request can be built from in one call: available locales, available themes, content variable slots with defaults, and the primary locale and theme. Used as the pre-flight check so a job is built from discovered identifiers rather than assumed ones.
Exports
5- Create Export Queues an asynchronous export job and returns immediately with an export identifier and a queued status. Supply locale and theme combinations to render several variants at once, content variations to produce data-driven copies, and a version to render a historical snapshot rather than the current state. This is the operation that commits the whole matrix.
- Get Export Status Reads the state of a single export job as it moves from queued to processing and then to completed or failed. On completion the response carries the variant count and the zip artifact with its object key and authenticated download URL.
- List Exports Lists the export jobs recorded against a project, newest first, with status, timestamps, variant count, rendered locales and themes, zip artifact, and any failure message. Used to audit export history or to find the most recent completed job without holding an identifier.
- List Export Artifacts Lists every file produced by a completed export job with its object key, filename, byte size, upload timestamp, and authenticated download URL. Object keys from this list are what a download step needs.
- Download Export Artifact Downloads one artifact by object key into FlowRunner file storage, returning a URL that later steps can attach, upload, or forward. Used to move finished creative out of the pipeline and into wherever it is consumed.
Account
1- Verify API Key Validates the configured API key and returns its metadata, including the owning user, the key name, whether it is enabled, its permission set, any expiry date, and the current rate-limit window with remaining requests. Used as a connection check and to read remaining quota before a batch of exports.
Triggers
1 triggersEvent Triggers
1- On Export Finished Fires once for every export job of a project that reaches a terminal state since the previous poll, so a flow can react as soon as rendering finishes instead of polling in a loop. Choose whether to react to completed exports, failed exports, or both. The first poll records existing exports as the baseline and emits no events. Used to route artifacts onward on success and to raise a failed job to its owner instead of letting it go unnoticed.
Frequently Asked Questions
What can FlowRunner do with Spectra?
FlowRunner agents can run Verify API Key, List Projects, and Get Project in Spectra, plus 14 more actions.
Does connecting Spectra to FlowRunner require OAuth?
No. Spectra connects to FlowRunner with an API key, no OAuth flow required.
Can Spectra trigger a FlowRunner workflow automatically?
Yes. Spectra supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Spectra
$100 in credits. No card required. Connect in minutes.