Configuring each destination type in a preset

This article walks you through the settings for each destination type you can attach to a Send-To preset: Dropbox, Webhook, GFcrew, and GFITpro Auto Print — so you know exactly what to fill in before your first send.

Before you start

Destination types only appear in the preset editor if the matching integration is already connected. Connect Dropbox or a Webhook under Settings → Integrations. GFcrew and GFITpro Auto Print appear automatically once your organization's GFIT key is connected there. If you haven't done that yet, see Connecting integrations.

Dropbox

A Dropbox destination drops each finished render into a folder in your connected Dropbox account. You control both where the file lands and what it's named, using two fields.

Folder path and File name

1. In the preset editor, click Add destination and choose Dropbox.
2. In the Folder path field, enter the Dropbox path where files should land — for example /Renders/Spring 2026. Variables are allowed (see below).
3. In the File name field, enter the filename pattern — for example {design}.jpg. Variables are allowed here too.
4. Click Save. Both fields are required; the Save button stays disabled until both are filled.

A Preview row below the fields shows the full resolved path using sample values, so you can confirm the pattern before saving.

Path variables

Both the Folder path and File name fields accept variables in curly braces. Click a variable chip to insert it at the cursor. The available variables are:

A typical folder path for event-based sports photography looks like /Renders/{main_event_code}_MainEvent, which produces a separate folder per event automatically. If a variable is unset at send time, a pre-flight prompt asks you to fill it in before dispatching. See Pre-flight prompts: missing variables and event codes.

Webhook

A Webhook destination pushes each finished render to an HTTP endpoint you control. There are no per-destination settings to fill in here — the endpoint URL is configured once at the integration level under Settings → Integrations → Webhook URL. When you add a Webhook destination to a preset, the editor confirms: Sends to your organization's configured webhook URL.

1. Click Add destination and choose Webhook.
2. Confirm the note about the org-level URL, then click Save.

If you need to change the endpoint, go to Settings → Integrations and update the Webhook URL there.

GFcrew (partner)

A GFcrew destination uploads the finished render to GFcrew, where it lands under the event you point it at. Whether that event is also switched live is a separate choice — see Activate event below. GFcrew destinations are only available to organizations with a GFIT key connected.

Event codes

1. Click Add destination and choose GFcrew.
2. For Main Event Code: check Pull from design to use the code set on each design at send time, or uncheck it and type a fixed code to always use the same event. Leave empty to pull from the design.
3. For Destination Event Code: same choice — pull from the design or enter a fixed code.

When a code is set to pull from the design but the design has none, a pre-flight dialog asks you to supply it before sending. Event codes can also be derived automatically from the Studio folder name if the folder follows the ####_MainEvent naming pattern.

Activate event

Activate event sits below the two event code fields and is checked by default. Leave it on to make the destination event active in GFcrew after upload — that's what puts the photos in front of customers. Uncheck it to upload the photos without changing the event's active state, which is what you want when you're staging an event ahead of time, adding late photos to an event you've already closed, or letting someone else decide when the gallery goes live.

The photos upload either way. The only thing this option controls is whether Templified flips the event's active state as part of the send.

Add Image to Roster

Check Add Image to Roster to link the uploaded photo to the rostered player. This requires the use of the Roster tab in GFcrew — the photo is matched to the player's roster entry so it shows up on that player's record.

Send quick-buy text

Checking Add Image to Roster reveals a nested Send quick-buy text option, also checked by default. With it on, and if the roster contains the parent's phone number, the parent receives a text with a direct quick-buy link to this image. Uncheck it to link the image to the player without texting — the photo is still tagged to the rostered player, GFcrew just doesn't send an SMS.

The Message field appears only when both Add Image to Roster and Send quick-buy text are on. Compose the text the parent receives there. Include <url> somewhere in the message — GFcrew replaces it with each photo's quick-buy link. The message is capped at 300 characters, and a counter under the field tracks how many you've used.

The Message field also accepts variable chips such as {org_name}, {main_event_code}, {design}, {folder}, {date}, and {layer:LayerName} to personalize the text. Click a chip to insert it at the cursor.

Create "Quick Buy"

Check Create "Quick Buy" to print a separate sample copy of the photo carrying the GFcrew quick-buy link as a QR code. The QR appears only on the handout; the photo sent to GFcrew stays clean. This option fires a separate render using a linked template you choose — the template must have exactly one photo layer (which receives this photo) and one QR code layer (which receives the quick buy link).

Enabling this requires setting up a Linked Templates entry for the print template on each design.

How the copy gets printed: you don't add anything else to the preset. When the Quick Buy render finishes, Templified queues it to GFITpro Auto Print automatically, under this GFcrew destination's event codes. The GFITpro desktop app polling that main event code claims the handout and prints it — so make sure the app is running at your print station and watching the same event code the destination sends to. The Quick Buy copy is a second render for billing purposes; see What counts as a render? (Billing FAQ).

The print template can also carry text pulled from the source design, so the handout shows real values instead of literal placeholders. For each text layer on the print template that is marked Dynamic and named identically to a text layer on the source design — for example a layer named Photo Number — Templified copies that source layer's resolved content onto the printed copy. Tokens in the source text are expanded first, so a source layer holding {designName} or a photo filename token like {team.filename} prints the actual design name or the original photo's filename rather than the token text.

To use this, name the print template's text layer exactly the same as the matching layer on the source design, and mark that print-template layer Dynamic. Names must match exactly. Any print-template text layer without a same-named source layer keeps whatever text it was designed with.

GFITpro Auto Print (partner)

A GFITpro Auto Print destination parks each finished render in a server-side print queue. The GFITpro desktop app installed at your print station polls that queue by event code or location code, claims renders one at a time, and prints them automatically. GFITpro destinations are only available to organizations with a GFIT key connected — the same key authenticates both sides, so no additional setup is needed.

1. Click Add destination and choose GFITpro Auto Print.
2. For Main Event Code: check Pull from design or enter a fixed code. GFITpro uses this code to route prints to the correct station queue.
3. For Destination Event Code: same choice.
4. Under Send Multi-Page as, choose how two-page designs are delivered (see below).
5. Click Save.

If Print Locations (Beta) is enabled for your organization, you can additionally route GFITpro prints to a named physical location. See Print Locations (Beta): routing prints to a physical station.

Send Multi-Page as

A two-page design — a front and a back, like a memory mate or a plaque insert — can reach the print station in one of two shapes:

• Multi-page PDF — one PDF containing every page. This is the default.
• Multiple JPGs — each page as its own JPG, named …_Front.jpg / …_Back.jpg. Only affects 2-page designs.

Pick Multiple JPGs when your print station handles images but not PDFs — a common situation, since many lab and kiosk printers accept JPGs directly and choke on a multi-page PDF. With this on, a front-and-back product arrives as two ready-to-print images rather than one file someone has to open, split, and re-export.

The two filenames share an identical base name and differ only in the _Front / _Back suffix, so an operator can pair the pages at a glance and sort them together in a folder listing. Both pages come from the same send — one order, two files — and are queued to the same GFITpro destination under the same event codes, so nothing changes about how the desktop app claims them.

One-page designs are unaffected: they send as a single image regardless of this setting.

The same choice is available on the Zapier Send GFcrew Order to Print action, so an automated print order can request per-page JPGs too. See Zapier actions reference.

Add-time validation

Templified validates destination settings when you click Save in the preset editor:

• Dropbox — both Folder path and File name must be non-empty. Save is disabled until both are filled.
• GFcrew with Add Image to Roster and Send quick-buy text both on — the Message must be non-empty and must contain <url>. Save is disabled otherwise. With Send quick-buy text off there is no message to validate, so Save stays available.
• Webhook and GFITpro Auto Print — no required fields in the preset editor; validation happens at send time if a required event code is missing.

Variables that reference event codes are validated at send time, not save time. If a code is missing when you send, a pre-flight prompt lets you fill it in. See Pre-flight prompts: missing variables and event codes.

Related articles

• Send-To Presets: save a multi-destination send
• Sending overview: how delivery works
• Pre-flight prompts: missing variables and event codes
• The Send-To Queue: stage an event, send all at once
• Print Locations (Beta): routing prints to a physical station