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 so it appears in the customer side immediately. 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.

Add Image to Roster

Check Add Image to Roster to link the uploaded photo to the rostered player. When the player's parent has a phone number in the roster, GFcrew texts that parent a direct quick-buy link to the photo. Checking this option reveals an SMS message field where you compose the text the parent receives. Include <url> somewhere in the message — GFcrew substitutes each photo's buy link there. The message is capped at 300 characters.

The SMS message field also supports tokens such as {main_event_code} to personalize the text per event.

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.

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. 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.

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 on — the SMS message must be non-empty and must contain <url>. Save is disabled otherwise.
• 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 a shoot, send all at once
• Print Locations (Beta): routing prints to a physical station