Skip to main content

Pointing GFITpro at a Print Location

Customer Champion
Updated

This article shows you how to set up Print Locations so each GFITpro station at your venue polls only its own print queue — and how to pick your location in Templified before you start sending. Print Locations is available to studios that have already connected a GFcrew/GFITpro account.

How routing works without Print Locations

By default, every GFITpro station polls the queue for a specific event code — the main_event_code on each design. That works fine when you have one printer per event, but breaks down when you run multiple stations simultaneously or reprint old designs at a different location.

Print Locations solves this by giving each station its own stable routing code. When a Templified operator picks their location before sending, Templified parks their renders under that routing code rather than the design's event code. Each GFITpro station polls its own routing code and only ever sees the prints meant for it — regardless of which event the photo is from.

Before you start: what you need

  • A GFcrew/GFITpro account connected under Settings → Integrations. The same GFIT key authenticates both the queue and the locations API — no additional credential.
  • Owner or admin role in your Templified organization to create and manage Print Locations. Other members can pick a location once it exists.

Step 1: Create a print location

  1. Go to Settings → Print Locations.
  2. Click New.
  3. Enter a Name for the station — e.g. CS Office or Denver Booth. Staff will see this name when they pick their location.
  4. Enter a Routing code — a short, stable identifier like CSOFFICE or DEN. This is what GFITpro uses to poll the queue; it cannot be changed after creation, so pick something that maps to the physical place, not to a temporary event. Allowed characters: letters, numbers, dots, underscores, and hyphens.
  5. Optionally, add a Destination code if GFITpro needs to narrow further within that location (for example, a specific bay or station). Leave blank if you don't need it.
  6. Click Create.

The new location appears in the list. Each location row shows its routing code as a copyable chip — click the chip to copy the code to your clipboard. Repeat for every station in your setup.

The Print Locations list in Settings, showing two locations with their routing code chips and Enabled switches

Step 2: Point GFITpro at the location

In GFITpro, open its location picker. GFITpro calls Templified with your GFIT key and lists every enabled location by name — the same names you gave them in Settings. Select the location for that station, and GFITpro routes there on every subsequent poll. The list refreshes periodically, so newly-added or renamed locations appear without restarting the app.

GFITpro's in-app location picker showing a list of named locations to choose from

You pick the location by name — there's no routing code to type into GFITpro. Behind the scenes, GFITpro polls Templified's print queue at GET /api/v1/print-queue using the selected location's routing code in place of an event code:

GET /api/v1/print-queue?main_event_code=CSOFFICE
Authorization: Bearer <gfit-key>

The poll, claim, ack contract and item shape are identical to the standard event-code flow. Only the value GFITpro passes as main_event_code changes — everything else (lease windows, duplicate handling, per-order ack) works the same way. See the Developer: GFITpro print-queue reference for the full API contract.

Step 3: Pick your location in Templified before sending

The location choice is per-browser, not per-user. It lives in the browser you're using, so a shared workstation always routes prints to the same place no matter who signs in.

  1. In Templified Studio, look for the Prints at: indicator near the Send To panel. If no location is selected yet, it shows Set print location with an amber warning icon.
  2. Click the indicator. A dialog opens: Where are you printing?
  3. Select the location for this computer.
  4. Optionally check Keep this location until I change it to suppress the daily re-confirm prompt on this machine. Leave it unchecked if different operators at this station change events frequently.

Once picked, every GFITpro Auto Print send from this browser routes to that location's routing code. The Send To panel shows the active location so you can confirm at a glance before dispatching.

A browser that has made no selection — or whose selection was disabled or deleted — falls back to routing by the design's event code, exactly as it did before Print Locations was enabled. No prints are lost; they just land in the event-code queue instead of the location-specific queue.

Enable and disable locations

Each location row in Settings → Print Locations has an Enabled switch. Turning it off removes the location from the in-app picker and from GET /api/v1/print-locations — GFITpro will stop seeing it the next time it refreshes the list. The routing code is preserved; re-enable the location when that station is back in use. Any operator who had selected a disabled location will see Set print location again and need to re-pick.

Reorder locations by dragging the grip handle on the left side of each row. The order controls how they appear in the Templified picker.

Route a GFcrew order to a location from Zapier

If you send GFcrew orders to print from a Zap rather than from Studio, you can pick the print location in the Zap itself — no browser selection required. The Send GFcrew Order to Print action has an optional Print Location field. Choose a location and that order routes to the location's routing code instead of the design's event code; leave it blank and the order prints at the design's main event code, exactly as before.

  1. Open your Zap and select the Send GFcrew Order to Print action step.
  2. In the Print Location field, pick the station you want from the dropdown. The dropdown lists every enabled location in your org by name; disabled locations never appear, so a Zap can't route to a queue an admin has turned off.
  3. Leave Print Location blank to keep the design's main event code routing.

The dropdown is populated by your connected org's locations. Requires Print Locations to be enabled for your org and at least one enabled location.

Listing print-location targets from the API

If you build your own automation instead of using the Zapier dropdown, an API-key request can list the routing targets so your automation picks the right id. This is a separate endpoint from the GFITpro desktop poll described above — it authenticates with your API key (not the GFIT key) and returns each location's id so an automation can pass it back as the print-location override:

GET /api/v1/print-location-targets
Authorization: Bearer <api-key>

The response lists the org's enabled locations, each with its id, name, and routing code:

{
  "locations": [
    { "id": "loc_abc123", "name": "CS Office", "routingCode": "CSOFFICE" },
    { "id": "loc_def456", "name": "Denver Booth", "routingCode": "DEN" }
  ]
}

Pass the chosen id as the order's print-location override when you send the print; the order then routes to that location's routing code. Only enabled locations are returned — a disabled or deleted location simply won't be in the list, and an order sent without a location falls back to the design's event code.

Per-location rollout checklist

Use this checklist when bringing a new station online:

  1. Create the print location in Settings → Print Locations.
  2. In GFITpro at that station, open the location picker and select this location by name.
  3. At the Templified browser for that station, click the location indicator and pick the correct location. Check Keep this location until I change it if the station is dedicated.
  4. Fire a test send using a GFITpro Auto Print preset and confirm the order appears in GFITpro at that station — not at another station that might still be polling an old event code.
  5. Repeat for each additional station.

Related articles

Comments

0 comments

Article is closed for comments.