Integration documentation
Automation guides
and downloads.
Choose your platform for exact credential settings, JSON requests, completion checks, file handling and recovery. Downloadable examples contain placeholders and require your own inputs and connections.
Reviewed . These integrations use each platform’s HTTP capabilities. Native marketplace apps are not required.
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.
- Single-render n8n workflow
Importable n8n JSON: Import into n8n, select Header Auth credentials and edit template, slot, artwork and run key. Downloads one finished image.
- Updated collection n8n workflow
Importable n8n JSON: Uses explicit artwork-role mapping, preflight, safe resubmission, bounded status checks and a binary ZIP download.
- Reviewed-plan n8n workflow
Importable n8n JSON: Submit an already approved plan_id and plan_hash without regenerating the review on a retry.
- Shared Postman collection
Postman JSON: Importable requests for assets, JSON jobs, reviewed plans, recovery and file downloads. Set your key locally.
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.
- Make HTTP module mapping
Configuration JSON: Field-by-field configuration and JSON request examples for HTTP v4. This is a setup recipe, not an importable Make blueprint.
- Shared Postman collection
Postman JSON: Importable requests for assets, JSON jobs, reviewed plans, recovery and file downloads. Set your key locally.
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.
- Zapier request and field mapping
Configuration JSON: Submission, completion and delivery mappings. This is a setup recipe, not a published Zap template or native app.
- Shared Postman collection
Postman JSON: Importable requests for assets, JSON jobs, reviewed plans, recovery and file downloads. Set your key locally.
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.
- Airtable submit script
JavaScript: Paste into Run a script. Reads mapped inputs and an API-key secret, then exposes jobId and status without logging the key.
- Airtable status script
JavaScript: Checks one existing job per run and returns status, error and the canonical protected result URL.
- Airtable field schema
CSV field checklist: Create or map these fields in a Mockup jobs table. Contains no actual records or credentials.
- Shared Postman collection
Postman JSON: Importable requests for assets, JSON jobs, reviewed plans, recovery and file downloads. Set your key locally.
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.
- Power Automate custom connector starter
Swagger 2.0 JSON: Importable Swagger 2.0 definition for JSON render jobs, status, recovery, collection review and account queries. Enter a bearer credential in a private connection.
- HTTP flow setup and mappings
Configuration JSON: Configure submission, explicit polling, deadline and file delivery. This recipe is not a managed solution package.
- Shared Postman collection
Postman JSON: Importable requests for assets, JSON jobs, reviewed plans, recovery and file downloads. Set your key locally.
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.
- Relay.app migration mapping
Migration checklist JSON: Map former trigger, HTTP call, review, completion and delivery responsibilities to active tools. Not an executable Relay workflow.
- Replacement n8n render workflow
Importable n8n JSON: A starting point for rebuilding the HTTP render path after configuring new credentials.
- Shared Postman collection
Postman JSON: Importable requests for assets, JSON jobs, reviewed plans, recovery and file downloads. Set your key locally.
Choose the right source format
The three n8n files are importable workflows. The Postman collection is importable into Postman. The Swagger 2.0 file is a starter for a Power Automate custom connector. Airtable scripts are copyable actions. Make, Zapier and Power Automate recipe JSON files describe settings; they are not native scenario or flow exports.
For collections, review assignments and samples before submitting the saved plan token. Preserve the token and run key on retries. Follow the n8n collection walkthrough.
Relay.app reports it shut down in September 2026. Its guide covers migration to an active platform. Official Relay.app notice.
Use signed completion webhooks when your receiver can verify the raw-body HMAC, deduplicate events and perform authenticated status lookups. The website iframe editor uses its separate website-key contract.