Connect the next step

Mockups that fit
your workflow.

Connect your approved artwork, orders and catalog records through standard HTTP actions. Generate tracked images and collections, then deliver authenticated files to your existing storage or publishing workflow.

FROM EVENT TO IMAGEExample workflow
↗Your trigger

New artwork or an order

Good things grow source artworkGeometric color study source artwork
{ }Render API

Template + design + settings

Background render job
◎Signed webhook

Verify the completion event

Continue your workflow

HTTP workflows available; no native node required

n8n

n8n connects to Mockups Generator through HTTP Request nodes using a bearer credential. The supplied workflows submit background work with stable idempotency keys, wait with a bounded polling loop and download a PNG or collection ZIP as binary data.

Read the detailed guide →

Custom HTTP scenarios available

Make

Make connects through its HTTP modules. Submit a JSON background render, save its job ID, check completion in bounded runs and download the finished file with an API-key keychain. Upload the returned file data to Drive, Dropbox or your storefront's own module.

Read the detailed guide →

API and webhook recipes available

Zapier

For authenticated calls, prefer API by Zapier when available because credentials are stored in its connection. Use nested JSON to submit a background render and persist its job ID. Handle completion in a separate polling or callback flow, then transfer an actual file to your destination.

Read the detailed guide →

Copyable scripts or external no-code orchestration

Airtable

Airtable records can drive Mockups Generator through an automation Run a script action or an external n8n/Make workflow. Submit quickly, store Job ID on the record, and check status in later runs. Attachment download URLs expire and protected result URLs cannot be used directly as public attachment inputs.

Read the detailed guide →

HTTP flows and custom connector starter

Microsoft Power Automate

Power Automate can submit JSON render jobs through an authenticated HTTP action or the supplied Swagger 2.0 connector. Store the accepted job ID, poll its status with a bounded Do until loop and send the downloaded binary body to a storage action. Tenant policies and connector licensing apply.

Read the detailed guide →

Relay.app closed in September 2026

Relay.app

Relay.app is no longer an available automation platform. Its former HTTP-based mockup integrations can be rebuilt in n8n, Make or Power Automate with the same template IDs, owned artwork and REST contracts. Recover job identity from your own records and treat missing history as a reconciliation task, not a reason to blindly render everything again.

Read the detailed guide →