Relay.app's official notice says the service shut down in September 2026 and permanently deleted accounts, workflows and run history. You cannot create or run a new Relay.app mockup workflow. Use configurations you preserved elsewhere to rebuild the automation in a supported tool.
By Mockups Generator · Relay.app closed in September 2026
New artwork or an order
Template + design + settings
Background render jobVerify the completion event
Continue your workflowExamples contain placeholders, not live credentials. Follow the format label: configuration recipes are instructions, while workflow and connector files can be imported into their platform. Platform account permissions and a small live test are required.
Migration checklist JSON
Relay.app migration mappingMap former trigger, HTTP call, review, completion and delivery responsibilities to active tools. Not an executable Relay workflow.
Importable n8n JSON
Replacement n8n render workflowA starting point for rebuilding the HTTP render path after configuring new credentials.
Postman JSON
Shared Postman collectionImportable requests for assets, JSON jobs, reviewed plans, recovery and file downloads. Set your key locally.
Locate source-table fields, downloaded configuration copies, request examples and destination storage. Relay's shutdown notice says its account and run history were deleted, so do not rely on logging back in to export them. Identify records that already store a Mockups Generator Job ID or completed output.
Use authenticated GET /api/v1/render-jobs/{id} for each known render and /bulk-jobs/{id} for known collections. Recent-job lists can help when an ID is missing, but they are capped and are not a full historical audit. Check destination files and source statuses to decide which work really needs rebuilding.
Choose n8n for importable HTTP workflows and binary routing, Make for visual scenarios and file modules, or Power Automate for a Microsoft-centered source and destination. Keep your business approval and record identity rules rather than mechanically copying the names of discontinued steps.
Create a named key in your account for the new platform and put it in that platform's credential store. Revoke the old Relay-specific key when it is no longer needed. Update any callback receiver's signing-secret configuration as part of your own credential review.
Use JSON POST /api/v1/render-jobs for single images. For current multi-artwork collections, preflight explicit areas, review their assignments and persist the plan token before submission. Store the accepted job ID and operation key in a system that remains available independently of the automation run.
Old Relay callback URLs are no longer usable. Use bounded authenticated polling, or configure a new receiver with raw-body signature verification and event deduplication. Download each protected result through the new credential and upload its bytes to destination storage.
Test one new event, one duplicate event and one failed destination upload. Confirm that duplicates keep the same server job and delivery retries do not create another paid image. Monitor the first scheduled run before processing an entire backlogged catalog.
The official Relay.app homepage is the authority for availability: it reports a September 2026 shutdown and permanent deletion of service data. Older search results and cached HTTP tutorials may still describe the former product. This page intentionally supplies a migration path rather than instructions for an account or HTTP action that can no longer be used.
The downloadable mapping describes responsibilities rather than a fake native import. Recreate each step with a tool that is currently available, then retest the business condition and output.
| Field or condition | Mapping or action |
|---|---|
| Former business trigger | n8n trigger, Make source module or Power Automate trigger |
| Custom HTTP render request | Authenticated JSON background submission |
| Human review | Approval of sample and exact reviewed assignments |
| Completion webhook | New verified receiver or authenticated polling |
| Run deduplication | Persisted source-event key, server idempotency key and event_id guard |
| File handoff | Authenticated download followed by destination file upload |
Owned templates and artwork, completed jobs and output files are resources of your Mockups Generator account, separate from the discontinued automation service. Their continued availability depends on the account and resource lifecycle. Credentials, source event mappings and externally stored job IDs let you rebuild the HTTP client; missing Relay history cannot be recovered by this app.
Before creating a new job, check whether its source record already has a completed image or stored job ID. For an accepted reviewed collection, reuse the same token and idempotency key if you retained them. A newly generated review is a new request fingerprint. If identity is missing, reconcile available source and destination records manually before deciding to render again.
The n8n guide includes importable single-render and collection workflows. The Make guide maps its current HTTP credential and download modules. The Power Automate guide includes a Swagger 2.0 custom connector starter. Airtable can remain your approval and tracking database while any of these tools performs the HTTP and file steps.
Platform requirements were checked against these official sources on . API examples are checked against the current application. Validate credentials, imports and destination behavior in your own platform account.
No. Relay.app's official site reports that it shut down in September 2026. This guide is for rebuilding previously configured automation in another platform.
No. It can expose accessible resources and jobs in your Mockups Generator account, but does not store or recover Relay.app account data or workflow definitions.
The n8n guide provides inactive importable JSON workflows. Power Automate has a Swagger 2.0 connector starter. Make and Zapier have clearly labeled HTTP setup recipes.
Review the workflow and requirements before creating your next output.
