Skip to main content

Connecting GFcrew (GFIT key)

Customer Champion
Updated

This tutorial shows you how to paste your GFIT key into Templified to connect your organization to GFcrew and GFITpro — and what to do if you need to disconnect.

What the GFIT key unlocks

A single GFIT key connects both partner integrations at once:

  • GFcrew — send finished renders to the GFcrew customer storefront so parents can view and buy photos immediately.
  • GFITpro Auto Print — park renders in a server-side print queue that the GFITpro desktop app polls and prints hands-off at your station.
  • Automatic designs from paid orders — when a parent pays for an order on the GFcrew storefront, Templified can build the matching Studio design for you. See Build designs automatically from paid GFcrew orders.
  • Photos into your flows — GFITpro can feed captures straight into Templified Flows using the same GFIT key it already sends to the print queue, so nobody has to copy a connection URL between the two apps. All you need on the Templified side is Flows enabled for your organization, plus somewhere for the photos to land: either a Default flow or a routing rule that matches. Both are set on the Routing tab of the Flows page — see Connecting a photo source to your flows (Connection & Routing). If neither exists, GFITpro reports No flow is set to receive photos; if Flows is not enabled for your organization, GFITpro says so and points you at Templified support.
  • GFcrew rosters on your phone — the Templified Tether phone app lists your GFcrew main events and looks up their rosters, so you can pick the player you are shooting. See Templified Tether: capture from your phone. Events you create inside Templified carry their own rosters and work in Tether without a GFIT key; only the GFcrew-sourced events and rosters need the key.

Once connected, both GFcrew and GFITpro Auto Print become available as destination choices inside every Send-To preset your organization creates. You do not need a separate key for each.

Connecting also makes your Studio folders easier to scan: any top-level folder that matches a GFcrew event shows the friendly Main Event name as a subtitle beneath the folder, so you recognize the event by name instead of just its code. See Folders & subfolders for how this appears in the folder list.

If your organization does not have a GFIT key, these destinations do not appear in Templified. Contact your GFcrew/GFITpro account representative to obtain one.

Who can connect or disconnect

Connecting and disconnecting integrations requires the owner or admin org role. Members can use connected integrations but cannot change them.

Connect using your GFIT key

The GFcrew / Pro integration card in Settings showing the GFIT Key input field and Connect button
  1. In Templified, open Settings → Integrations.
  2. Find the GFcrew / Pro card. Its status shows Not connected until a key is saved.
  3. If your organization is offered a choice of GFcrew deployments, the card shows a GFcrew environment picker above the key field. Choose Production (api.gfcrew.com) unless your key was issued against GFcrew's staging site, in which case choose Staging (app.stg.gfcrew.com). Almost everyone picks production. When there is only one deployment available to you, the picker is hidden and production is used automatically.
  4. In the GFIT Key field, paste the key your GFcrew representative provided. The field is masked for security.
  5. Click Connect. Templified verifies the key with GFcrew and, on success, displays your tenant name and ID with a Connected badge.

[Screenshot coming: The GFcrew environment picker on the integration card, open to show the Production and Staging choices above the GFIT Key field]

A GFIT key belongs to one GFcrew deployment. Pick the one your key was issued for: if the key and the environment do not match, the connection is rejected, Test connection fails, and roster lookups come back empty because Templified is asking the wrong GFcrew for events it does not have.

⚠️ REVIEWER: verify the environment picker is visible to production customers before publishing — the card renders it only when more than one GFcrew deployment is offered to the organization.

If the key is rejected, double-check that you copied the full value — GFIT keys start with a UUID-style prefix such as 452c4152-…. Contact your GFcrew representative if the error persists.

Test the connection

Once connected, the card shows which GFcrew deployment the stored key belongs to, so you can confirm it at a glance without disconnecting: a Staging GFcrew tag appears next to the Connected badge when the key is a staging key, and no tag means production. Switching environments is not a setting you can flip — disconnect, then reconnect with a key issued for the deployment you want.

After connecting, click Test connection on the card to confirm the link is still valid. A success message confirms Templified can reach GFcrew. Run a test any time you suspect the key may have been rotated on the GFcrew side.

Disconnect

The GFcrew / Pro card showing Connected status with tenant name and the Disconnect button

To remove the integration:

  1. Open Settings → Integrations.
  2. On the GFcrew / Pro card, click Disconnect.
  3. Confirm the dialog. Templified removes the key immediately.

Disconnecting invalidates the GFIT key for all uses within Templified at once — GFcrew sends, GFITpro Auto Print and GFITpro's ability to feed photos into your flows all stop working the moment the key is removed. Any Send-To presets that include a GFcrew or GFITpro Auto Print destination remain saved, but those destinations will not fire until you reconnect with a valid key.

Related articles

Comments

0 comments

Article is closed for comments.