Flow quick start (video): from camera to finished design

This quick start takes you from zero to a working automation in one sitting: photos leave your camera, arrive in Templified, and come out the other side as finished designs — no clicking per photo. The video (about 14 minutes) walks through the whole setup using GFITpro as the photo source, but the same steps work with any app that can send a photo over the web.

The three setup steps

The first time you open the Flows page, a setup checklist walks you through the same three steps the video covers:

1. Connect a source — create your organization's Connection URL so photos can flow in.
2. Create a flow — build at least one pipeline photos can run through.
3. Route photos to flows — pick a default flow or add a routing rule.

Each checklist item jumps to the tab that owns it, and the checklist collapses to a "Setup complete" strip once all three are done.

Before you start

• The Flows tab must be enabled for your organization.
• You must be an owner or admin — the connection settings launch billable runs, so they are hidden for members.
• You need at least one template ready to render (see Creating and editing a template).

Step 1 — Connect a source

1. On the Flows page, open the Connection tab.
2. Under What's sending you photos? choose GFITpro.
3. Click Create connection URL and copy the URL that appears.
4. In GFITpro, open Tethering settings. Under Options, turn on Enable Webhook URL and paste the connection URL into the Webhook URL field.

Treat the URL like a password — anyone who has it can send photos into your flows. If it ever leaks, click Regenerate to issue a fresh one.

Because you chose GFITpro, the Fields we'll receive panel is preloaded with the data each photo arrives with — Team Name, Jersey Number, First Name, and so on. Your flows can drop these straight into template text fields as {variables}.

Step 2 — Create a flow

1. Switch to the Flows tab and click New flow. The editor opens with a Photos start step already on the canvas.
2. Name your flow at the top of the editor.
3. Drag a Remove Background step from the palette onto the canvas and connect the Photos step to it.
4. Drag a Create Editable Design & Render step onto the canvas, connect Remove Background to it, and choose your template in its config panel.
5. Fill the template's text fields with {variables} from the photo's data — for example {firstName} {lastName} for a name field, {jerseyNumber} for a jersey field. Click the { } button inside a field to pick from the available fields. Photo fields are filled automatically by the pipeline.
6. Under Output, set the Folder and Design name (these accept {variables} too) so each finished design lands where you expect in Studio.
7. Click Save.

That's the whole pipeline: each arriving photo gets its background removed, then becomes an editable Studio design rendered from your template. You can add more later — text steps, branches, a Create Team Photo step, a Send To destination — but this is enough to see the loop working. For a deeper tour of the builder, see Building your first flow.

Step 3 — Route photos to flows

Routing decides which flow each incoming photo runs. The fastest path: click your saved flow's Photos start step — when your organization has a GFITpro connection, the config panel shows a GFITpro connection section — and click Set as default flow. From now on, every photo that arrives at your connection URL runs this flow.

You can do the same from the Routing tab by picking your flow under Default flow. When you later run different flows for different teams or events, add Routing rules there — see Connecting a photo source to your flows (Connection & Routing).

Send a test photo

1. Capture (or resend) one photo from GFITpro.
2. On the Flows page, open the Activity tab — the delivery appears with its status and the flow it ran.
3. Open your flow and click Runs to watch the run: each step lights up as it processes.
4. When the run completes, open Studio — the finished design is waiting in the folder you set on the Create Editable Design & Render step, named by your Design name pattern. From there it behaves like any other design: open it to tweak, or send it anywhere with Send To.

If a delivery doesn't run — no default flow set yet, or a rule didn't match — the photo is kept, not lost. Fix the routing and replay it from the Activity tab.

Not using GFITpro?

The same setup works with anything that can send a photo over the web:

• On the Connection tab, choose Custom / other instead of GFITpro. Send one test photo to your URL, then click Detect fields so the photo's data fields become available to your flows and routing rules.
• Or skip the organization-level connection entirely and give a single flow its own address — see Triggering a flow by webhook.

Related articles

• What is Flow? (automation pipelines)
• Building your first flow
• Connecting a photo source to your flows (Connection & Routing)
• Triggering a flow by webhook
• The Flows Activity tab (delivery log)