Skip to main content
The Zapier integration for Batch Relay creates print orders directly through the Batch Relay API.

​
Connect Zapier

Create a connection with a Batch Relay API key.
  • br_test_... keys create Sandbox test orders.
  • Live br_... keys create Production orders.
Both key types use https://api.batchrelay.com. Zapier derives the order environment from the key, and the API verifies it against the stored key record. There is no separate Environment selector in Zapier.

​
Create Print Order

Use Create Print Order when an earlier Zap step provides print data. It accepts a Prints line-item group with aligned values for:
  • Print SKU
  • Quantity
  • Image URL
One action run creates one Batch Relay order. Map line-item arrays when several prints should ship together. Do not loop over individual prints that belong in the same shipment. Each loop run would create a separate quote, shipping charge, and order. Print SKU values are catalog values such as print-5x7|paper=lustre. The integration looks up the current product revision and options before it quotes the order.

​
Create Manual Print Order

Use Create Manual Print Order for staff-entered or one-off orders. Choose the number of distinct print rows, from 1 through 20, then fill in a Print SKU, Quantity, and Image URL for each row. All print rows share one customer, delivery address, return address, shipping service, and provider choice. Quantity means copies of that one row. Add another row when the image or SKU differs.

​
What happens when a Zap runs

The action builds the order, requests a Batch Relay quote, then submits that quote as one order. Zapier does not expose separate quote and submit steps. Batch Relay is the source of truth for catalog revisions, eligible products, shipping, tax, platform fee, total price, provider routing, billing, and fulfillment status. Use a stable External Order ID from the triggering system. Batch Relay uses it as the idempotency key, so an unchanged Zap retry returns the same quote and order instead of creating a duplicate. Use a new External Order ID for a reprint or intentional replacement.

​
Images, catalog, and shipping

Provide a public or signed HTTPS Image URL. Batch Relay copies the image during quoting and freezes the bytes used for fulfillment. The URL only needs to remain available while the action runs. The integration loads products from the live Batch Relay catalog and shipping services from the live shipping catalog. The quote still decides whether a product and service are valid for the destination and returns the exact price. Current shipping services are:
  • economy_untracked
  • economy
  • expedited
  • standard_one_day
  • priority_one_day

​
Provider routing

Leave Provider blank to let Batch Relay route the entire order. If you select a provider, it applies to the whole order, never a single print row. The API returns any availability or compatibility issue directly. Zapier does not hold provider credentials or send provider-native payloads.

​
Triggers

There is currently no support for Zapier’s triggers. More to come here in the future. (reach out with what you would expect to see, we’re listening!)

​
Before you turn on a live Zap

Test the whole flow with a br_test_... key first. Confirm the recipient and return addresses, shipping service, image URLs, and External Order ID. Replace it with a live br_... key only when you are ready for a live order.