To prepare branded campaign images from Airtable, keep each original image separate from its partner-specific copy, apply the approved logo with miniExtensions, and review the actual output before sharing it. Link every copy to its campaign, partner, and intended placement so the release team can distinguish similar files.

This workflow suits a small marketing team preparing co-branded announcement graphics or partner campaign packs. Its useful outcome is an identifiable, reviewed image for a particular recipient and channel, without replacing the reusable source photograph.

Start with a specific partner and placement

Imagine fictional Cedar Studio preparing a seasonal campaign with two partners: Harbor Books and Meadow Market. Both use the same approved background photograph, but each needs a different logo. Harbor wants a landscape newsletter image; Meadow needs a portrait social graphic. The team must keep the partners’ files separate and check the logo against both compositions.

A campaign coordinator chooses approved sources and records the requested placement. A production editor prepares each branded copy. A reviewer checks the visual and intended use before a coordinator sends the pack. These roles can belong to one person, but processing, approval, and distribution remain separate decisions.

Start with an Airtable base connected to miniExtensions, permission to process the source artwork and logos, and a plan appropriate for the workload. Confirm the current limits before preparing a large batch. This example describes a workflow to configure and check; it does not report a completed test.

Give every branded variant its own record

Use four tables so one source can support several clearly identified outputs:

  • Campaigns: Campaign Name (primary single line text), Campaign Reference (single line text), Planned Release (date), and Coordinator Note (long text).
  • Partners: Partner Name (primary single line text), Approved Logo (attachment), Logo Version (single line text), Brand Guidance (long text), and Approval Reference (URL or single line text).
  • Source Assets: Source Reference (primary single line text), Original Image (attachment), Composition (single select: Landscape, Portrait, Square), and Source Notes (long text).
  • Branded Variants: Variant Reference (primary single line text), Campaign (single link), Partner (single link), Source Asset (single link), Source Copy (attachment), Branded Output (attachment), Intended Placement (single line text), Logo Version Used (single line text), Processing Settings (long text), Processing Error (long text), Review State (single select: Prepare, Review, Approved, Revise, Superseded), Reviewer (single line text), Reviewed On (date), and Sent On (date).

The coordinator copies the selected source into Source Copy on each variant. That is a manual preparation step here, not an assumed transfer from a linked record or lookup. Keep Original Image untouched in Source Assets, and never map the generated output to either source field.

Create a variant such as “Seasonal | Harbor Books | Newsletter | v1.” For Meadow’s portrait placement, use the separately approved portrait composition. A logo overlay does not decide how to crop a landscape photograph into an effective portrait image. Resolve that composition first.

Translate brand guidance into processing settings

For one partner at a time, configure the miniExtensions Add Logo to Image automation. Upload that partner’s approved file as Logo Image. Map Source Images Field to Source Copy and Output Images Field to Branded Output. A transparent PNG is the documented recommendation for the logo.

Choose Logo Position, Logo Opacity, Logo Size (%), and Edge Padding (px) to suit the placement. Logo Size uses the source image’s smaller dimension. Record the choices in Processing Settings and the exact approved version in Logo Version Used. Map the optional Error Message Field to Processing Error for troubleshooting.

The Partner relationship documents who the variant is for. It does not automatically select a different Logo Image for every record. Keep each run scoped to the partner matching the uploaded logo and verify that mapping before execution. For repeated production, maintain clearly identified configurations rather than relying on someone to remember which logo is currently loaded.

Process a small selection before the campaign pack

Prepare one representative variant first. Check its source attachment, partner, logo version, and intended placement. Use the automation’s supported record-selection controls to limit the run to the sample, following the Run section guide. Verify the actual selected record before starting.

Inspect the resulting attachment and any error text. A successful run shows that processing produced an output; staff still decides whether to move the variant to Review. This design does not automatically update Review State, request approval, email a partner, or publish a campaign.

Repeat with a contrasting composition before expanding the selection. A white logo that works on a dark corner may disappear against another image. The same percentage can produce an unsuitable visual balance across different dimensions.

Approve the visual and its intended use

Open the full output alongside the source. Check the correct partner, logo version, legibility, clear space, crop, and important image details. Look for an opaque background behind the logo, accidental coverage of a face or product label, and a mark that sits too close to an edge.

Preview the output in the intended newsletter or social layout when possible. A platform may crop the image differently from the Airtable thumbnail. Record concrete revision notes, such as “Move the logo away from the product label,” instead of approving solely because a file exists.

The reviewer records Approved, their name, and Reviewed On only after accepting that specific variant. Logo placement does not establish copyright ownership, access control, authenticity, or permission to use a partner’s brand. Those approvals remain part of the team’s separate agreement and review process.

Handle a revised logo without stale outputs

If Harbor supplies a newer logo, create a new variant revision with an empty output field and keep the previously approved copy available. Review it again before replacing the release file.

Many miniExtensions automations skip records with existing output by default. Existing Data Handling can be set to Overwrite for deliberate reprocessing, but that can process eligible records on each run. Preserve accepted files and check the selection before using it. A changed logo or source does not prove an existing output has been refreshed.

Release only the reviewed variant

Use an internal release view requiring Approved and a populated Branded Output. The coordinator checks campaign, partner, placement, and revision before distributing the exact file through the team’s normal process. Record Sent On afterward; an entered date is not an automated delivery receipt.

Before adopting the workflow, check two partners with different logos, a portrait and landscape source, a rejected output, and a revised logo. Verify that originals remain unchanged and that rejected or superseded variants stay out of the release selection. The result is a manageable partner campaign pack with traceable choices and human visual acceptance.