Batch Relay

Integrations · reviewed July 31, 2026

Connect the workflow without losing the source of truth.

Batch Relay connects studio commerce and production data to supported labs and automation tools. This page states what is live, what is finishing production rollout, and what remains in pilot so studios can plan without guessing.

Check availability How connections are protected

Live

WHCC · RPL · API

Available to onboarded workflows, with the broad production rollout completing next week.

Coming soon

Zapier · n8n

Both automation connections are actively being tested with pilot workflows.

Onboarding model

One real event

Availability is confirmed against the products, data, volume, and exceptions your studio actually uses.

Live connections

Available for production onboarding

“Live” means the connection is part of the supported Batch Relay production path for approved, onboarded workflows. It does not mean every provider product or API use case is automatically enabled. The first event still verifies catalog mapping, asset requirements, delivery rules, credentials, and exception handling.

Live

WHCC

White House Custom Colour

Live · production onboarding

Batch Relay maps supported studio products, prepared assets, delivery choices, and validated order data into the WHCC fulfillment path. Product and shipping rules are confirmed during onboarding so an event is tested against the actual catalog being sold.

  • Supported provider connection for print fulfillment
  • Provider-specific product and option mapping
  • Eligible-order validation before submission
  • Order and fulfillment context retained in Batch Relay
Read the partnership profile
Live

RPL

Richmond Pro Lab

Live · rollout completing by August 7, 2026

Richmond Pro Lab is a supported fulfillment connection. The production rollout is completing during the week of August 3–7, with early studio events monitored through provider formatting, submission, acknowledgement, and downstream status handling.

  • Supported Richmond Pro Lab production path
  • RPL-specific product and order translation
  • Monitored first-event onboarding during rollout
  • Provider acknowledgement and exception visibility
Read the partnership profile
Live

API

Batch Relay Developer API

Live · production rollout

The Batch Relay API exposes the provider-neutral order workflow used by first-party surfaces and approved integrations. It supports environment-scoped API access, quoting and order submission, required idempotency, and durable order and fulfillment state.

  • Provider-neutral catalog and fulfillment contracts
  • Environment-scoped credentials and authorization
  • Idempotent quote and submit workflow
  • Structured status and error responses for recovery

Automation pilots

Coming soon, with real workflows already in pilot.

Zapier and n8n are not being described as broadly self-service today. Pilot partners help prove authentication, field mapping, retries, error handling, and documentation before general availability. Both connections use the Batch Relay API as the durable boundary rather than carrying provider credentials directly.

Coming soon · in pilot

Zapier

The Zapier connection is in pilot with selected workflows. The goal is to let studios trigger Batch Relay activity from familiar business tools without placing lab credentials or provider-specific logic inside individual Zaps.

Current pilot focus: Pilot work is validating authentication, field mapping, safe retries, and clear failure messages before broader access.
Coming soon · in pilot

n8n

The n8n connection is in pilot for teams that need more control over multi-step automation. The current path is organized around preparing, quoting, and submitting print orders through the Batch Relay API rather than embedding a single lab workflow in the node.

Current pilot focus: Pilot work is validating reusable credentials, item handling, privacy-safe logs, idempotency, and production-grade error recovery.

What an integration is responsible for

An integration moves structured work between systems. It does not make incomplete data complete, replace a lab's production schedule, or turn every provider product into an interchangeable SKU. Batch Relay keeps those boundaries explicit.

  1. 1

    Studio source data

    Roster, package, purchaser, image, delivery, and event context enter through the studio workflow.

  2. 2

    Batch Relay validation

    The platform resolves product rules, required fields, assets, provider compatibility, and visible exceptions.

  3. 3

    Provider or automation handoff

    A supported lab adapter or approved automation connection receives the contract intended for that system.

  4. 4

    Durable status and recovery

    Order identifiers, handoff state, provider responses, and exceptions remain connected for tracking and issue resolution.

Availability notes

Statuses were reviewed July 31, 2026. Provider, product, region, and pilot availability can change. Batch Relay confirms the supported path during event onboarding and updates this page when a connection changes stage.

Connect one real workflow

Bring the event and the systems around it.

Tell us which lab, trigger, destination, and handoff you need. We will confirm current availability and map the smallest production-ready path.

Plan your first eventReview trust architecture