Connecting a photo source to your flows (Connection & Routing)

This article shows you how photos reach your flows — from the Templified Tether app, or from an outside photo system — and how to decide which flow each incoming photo runs. You set this up on two tabs of the Flows page: Connection and Routing.

Connection versus a per-flow webhook

A per-flow webhook (covered in Triggering a flow by webhook) gives each flow its own address. That is ideal for a single automation, but the address is tied to that one flow.

A connection works at the organization level instead. Captures from the Templified Tether app arrive this way automatically, and you can optionally add one private connection URL that an outside system posts every photo to. That URL never changes when you rebuild, rename, or replace a flow — you set the address once and use routing rules to decide where each photo goes. Either way, every photo lands in the same set of routing rules.

Before you start

The Flows tab must be enabled for your organization.
You must be an owner or admin. The Connection and Routing tabs are hidden for members, because incoming photos launch billable runs.
You need at least one saved flow to route photos into.

The Connection tab

Open the Flows page and select the Connection tab. It holds two independent parts — the Templified Tether card and an optional external connection — and both feed the same routing rules.

Templified Tether is connected automatically

The first card, Templified Tether, has nothing to configure. It shows Connected automatically and explains that the Tether app links to your organization when your team signs in — there's no webhook URL to copy. Captures land here and follow your routing rules, alongside any external system connected below.

So if the Tether app is how you shoot, you can skip straight to the Routing tab. Nothing on this tab needs to be turned on first.

Templified Tether card showing Connected automatically above the optional external connection card

Connect an external system (optional)

The second card is headed Connect an external system. Create a connection URL only when something besides the Tether app sends you photos — GFITpro camera tethering, or a custom app of your own. The card asks Also sending photos from another system?, and the note under the button spells out that it's optional: Optional — Templified Tether works without it.

Pick your source:
- GFITpro — camera tethering, where the field names are already known.
- Custom / other — any app that can post a photo.
Click Create connection URL. Templified generates a private URL your photo system posts each photo to.

Once a URL exists, the card shows a Connected status with the source name, the URL with a copy button, and this reminder:

Anyone with this URL can send photos into your flows — treat it like a secret.

Two controls sit below the URL:

Regenerate — issues a new URL. The old one stops working immediately, so update your sending system afterward.
Revoke — turns the connection off without deleting your flows or rules.

Fields we'll receive

Every photo can arrive with data fields (team, name, jersey number, and so on) that your flows and routing rules can use. The Fields we'll receive panel, in its own card at the bottom of the tab, shows which fields to expect, each as a chip with a friendly, readable label. You never face a blank list: because Tether is always connected, its field vocabulary is always shown.

No external connection yet — the panel lists the fields Templified Tether captures send, such as Team Name, Jersey Number, and First Name.
GFITpro — the panel widens to the GFITpro field list plus the Tether-only fields, so both sources are covered at once. The common, routable fields show first; a More fields link (with a count of how many are hidden) expands the rest and flips to Fewer fields. Two GFITpro fields are spelled out to keep them clear: Main Event Name and Main Event Code.
Custom / other — the Tether fields stay listed, and your webhook's real deliveries add to them. Send one test photo to your URL, then click Detect fields. The field names from that delivery appear alongside the Tether fields and become available in the routing rule picker.

Once photos have actually arrived, the panel adds ✓ Confirmed by recent deliveries. below the chips.

These friendly names are display labels only. Routing rules still match on the raw field name each photo actually sends — hover a chip to see that raw key.

Route photos to the right flow

Switch to the Routing tab to decide where each incoming photo runs. The tab stacks two cards: the Routing rules table on top, and the Default flow catch-all below it.

Routing rules

The Routing rules table sends photos that match a field condition to a specific flow. Rules are checked from top to bottom — the first match wins, and if nothing matches, the Default flow runs.

Click Add rule.
Choose a field from the picker (populated with your GFITpro or detected field names, shown as friendly labels), or choose Custom field… to type one.
Choose a condition — for example is, is not, contains, or is between — and enter the value it compares against.
Pick the target flow for photos that match.
Reorder rules with the drag handle so the most specific ones sit on top. Toggle a rule off to archive it without deleting.
Click Save rules.

Every enabled rule needs a field, a value, and a target flow before you can save. Any rule that's still incomplete is highlighted amber with the message Finish each highlighted rule — pick a field, enter a value, and choose a flow — before saving., and Save rules stays disabled until it's complete. To set a rule aside half-built, toggle it off — an archived rule can stay incomplete.

Default flow

The Default flow is the catch-all — where a photo goes when no rule above matches. Pick a flow from the dropdown, or leave it on None — name a flow in each request if the sending system will name the flow itself.

You can also set the default flow without leaving the flow editor. When your organization has a GFITpro connection, a saved flow's start step shows a GFITpro connection section with its routing status. If the flow isn't routed yet, click Set as default flow there to make it the catch-all in one click — the same section also links back to Open Connection settings.

Either way, a single request can override routing by including a flow field (a flow name or id) in its body.

Route an event straight from Studio

You don't have to open the Routing tab to route an event. In Studio, each event carries a flow button that writes the routing rule for you.

If the event already routes somewhere, the button reads Open flow and takes you straight to that flow.
If it doesn't route anywhere yet, the button reads Create flow and opens a dialog titled Route this event to a flow.

The dialog offers three choices:

Create a new flow — starts a blank flow named after the event and opens the editor.
Use an existing flow — routes this event's photos to a flow you already built.
Duplicate an existing flow — copies a flow, then routes this event to the copy.

Pick a flow if the option needs one, then confirm — the button reads Create flow & route, Duplicate & route, or Create route depending on your choice. Templified adds a rule matching Main Event Name to that event name and puts it at the top of your rules list, so it can't be shadowed by a broader rule above it. You'll see the confirmation Photos for “<event>” now route to <flow name>. If someone already routed the event, you'll get Photos for “<event>” are already routed instead and nothing is duplicated.

Creating or duplicating a flow drops you into the flow editor so you can build it; routing to an existing flow leaves you in Studio. The button appears for owners and admins when Flows is enabled for your organization.

See what arrived

Every photo posted to your connection URL is logged on the Activity tab, with its status and the flow it ran. If a delivery failed or you need to run it again, you can replay it there — Templified starts a fresh run from the stored photo.

That includes photos that arrive with no matching rule and no default flow: the photo is kept, not lost. Add the missing rule (or set a default flow), then replay those deliveries — one at a time or in bulk — and each one routes against your current rules. For the replay steps, see The Flows Activity tab (delivery log).