Automate a collection export

Use this n8n workflow to check a one-template collection, submit it once, wait for completion, and download its ZIP and manifest. It uses standard HTTP nodes. Store publishing is a separate integration.

Download n8n workflow
  1. Upload a template and artwork in your workspace. The template must be ready. Copy its ID from the editor URL and obtain the artwork ID from GET /api/v1/assets.
  2. In n8n, choose Import from File and select the downloaded JSON. The workflow starts manually and is inactive by default.
  3. Create a Header Auth credential: name Authorization, value Bearer YOUR_API_KEY. Select it in every HTTP Request node: Preflight, Submit collection, Read status and Download collection. Create the key under API access.
  4. Edit Workflow settings: set the server URL, template ID, asset ID and a unique run key for this intended collection. The simple example fills the first artwork area. For several independent areas, replace assets with explicit design_sets and map role_slots on the template.
  5. Run manually. Preflight must pass before submission. The last node returns the ZIP in its collection binary field. The ZIP contains the images and manifest.json.
  6. Rerun with the same inputs and run key after a lost response. The API returns the existing job. Reusing a key with changed inputs returns 409. Use a new key only when intentionally creating another export.

Recovery and billing

The workflow polls every five seconds and stops polling after 30 minutes. The server job continues. A failed or stopped job reports its ID; open that collection in the workspace to retry failed images or continue unfinished work. Finished images remain available, and their render credits are not charged again.

For event-driven integrations, submit a public webhook_url. Verify HMAC-SHA256 of the exact raw request body using your signing secret. Deduplicate by event_id before applying changes. Network errors, 408, 425, 429 and 5xx responses retry up to eight times; other unsuccessful responses require review. Delivery history and replay are in API access. Result URLs require your own API credential; the notification does not contain one.

Output profiles

Choose from GET /api/public/output-profiles. Profiles fit the entire scene on a white canvas without cropping. A profile overrides image width. Each planned image uses one render credit when completed. Flat print files are prepared separately in the editor and are not included in this workflow.

This template has API contract coverage in our test suite. Verify import, credentials and a small run in your n8n installation before scheduling larger collections.

n8n references: Import workflows, HTTP Request settings, Wait node.