This article explains what the Templified Zapier app does, how to authenticate it with an API key, and which triggers and actions are available — so you can wire Templified into your existing Zaps without reading through the full API documentation.
What the Zapier app lets you do
The Templified Zapier app connects your Zaps to the same rendering and Studio pipeline used by the dashboard and the REST API. You can:
- Generate finished images from any template, filling in text, photo, and QR-code fields per-run.
- Create editable designs in Studio automatically — either alongside a finished render or on their own — so a Zap can produce a design that a photographer can still open and adjust.
- Add player photos to a team composite one at a time, with automatic slot management and retake support.
- Run Background Removal and photo correction on a source photo before passing it to a render step.
- Render all templates in a design group in one action and receive results for each member template.
- Trigger a Zap when a design is sent from Studio.
The app uses the same pay-as-you-go balance as every other render surface — each image render deducts from your organization's balance, and Background Removal carries an additional surcharge.
Connecting the app: API key authentication
The Templified Zapier app authenticates with an API key that you create in the dashboard. The key is sent as a Bearer token on every Zapier request — there is no OAuth flow.
- In the Templified dashboard, go to Settings → API Keys.
- Click Create API Key.
- Give the key a descriptive name (for example, Zapier Production) and click Create Key.
- Copy the key immediately — it starts with
tmpl_and is shown only once. Store it somewhere safe. - In Zapier, when you add or reconnect the Templified app, paste the key into the API Key field and click Yes, Continue. Zapier verifies the key against your account and labels the connection with your organization name.
You can create multiple keys — for example, one for Zapier and one for direct API calls — and revoke any key at any time from the API Keys page without affecting the others.
Triggers
Triggers are the "when this happens" side of a Zap. The Templified app provides one trigger and several dropdown triggers used as data sources by action steps.
Design Exported (instant)
Fires when a design is sent from Templified Studio. This trigger uses a real-time subscription, so Zapier receives the notification as soon as the export completes.
The trigger provides: the design name, the Studio folder it lives in, the rendered image URL, text layer values, and any event codes or player identifier set on the design. Use this trigger to push a finished design to a downstream system — for example, send the image URL to a CRM or notify a Slack channel when a design is ready.
Actions
Actions are the "do this" side of a Zap. Each action maps to an API endpoint and handles the asynchronous nature of rendering automatically — Zapier waits for the render to finish before passing the result to the next step.
Create Image
Generates a finished image from a template. After you select a template, the step shows a field for each dynamic layer in that template — text fields, photo URL fields, and QR code fields. Fill in the values your Zap provides, and the action returns the rendered image URL when complete.
Optional fields on this action:
- Send To — route the finished image to a connected destination (Dropbox, GFcrew, or your outbound webhook) directly from the action. Send-To presets are not available here; use Create Editable Design & Render if you need preset fan-out.
- Send To Qty — how many copies to request at that destination.
- Player Identifier — an arbitrary identifier (jersey number, student ID) stored on the render and included in webhook notifications and export data.
- Main Event Code and Destination Event Code — GFcrew Pro only. Stored on the render and sent when you export to GFcrew or your outbound webhook.
Create Editable Design & Render
Creates a finished render and saves an editable design in Studio at the same time. The design is placed in a Studio folder you specify (the path is created automatically if it doesn't exist). You can open the design in Studio later to adjust it.
This action also supports Send To with full preset support — including presets that fan out to multiple destinations such as Dropbox and GFcrew. Use Create Editable Design & Render when you need preset fan-out or want the design to be editable after the Zap runs.
Set Overwrite Existing to yes if the Zap runs on a schedule and should update the design in place rather than create a new one each run.
Create Editable Design Only
Creates an editable design in Studio without immediately rendering a finished image. The design is placed in the folder path you provide and can be opened in Studio to fill in photos and text manually. Use this action when you want to pre-create a set of designs from a data source and let a photographer complete them in Studio.
Because nothing is rendered, this action has no Send To field — send the design later from Studio, or use Create Editable Design & Render if you want the render and the delivery in one step.
Create or Update Team Photo
Adds one player photo to a team composite design. On the first call for a given folder path and design name, the action creates the design and places the photo in the first available slot. Subsequent calls add each additional player photo into the next slot. If you include a Player Identifier, a repeated identifier replaces that player's existing photo in place — which is how retakes work.
This action is designed to be called once per photo in a loop. The design accumulates photos slot by slot; you send all the team's photos and the composite fills in automatically.
Background Removal
Pre-processes a source photo and returns a cut-out image URL plus face and content detection data. Use this action as a step before a render action when you want to pass a clean, background-free photo into a template that uses face placement. The action's output includes the extracted image URL, which you map into the photo field of a subsequent Create Image or Create Editable Design & Render step.
It has two toggles. Remove Background is on by default and outputs a transparent PNG. Apply Photo Correction is off by default and applies colour and exposure correction using the default profile. Alongside the extracted image URL, the step also returns the detected face and content boxes, whether the subject is wearing glasses, and how many faces were found.
Create Images From Template Group
Renders every template in a design group in a single action. Select the design group, fill in the shared fields (a player name, photo URL, or other values common to all member templates), and the action waits until the entire batch finishes before returning. The output contains one result per member template, each with its own rendered image URL.
Use this action when a single subject (a player, a team) needs multiple related images rendered at the same time — for example, a 5×7, a trading card, and a banner all from one Zap step.
Send GFcrew Order to Print (GFcrew accounts)
Translates a GFcrew order to a linked print-ready design and dispatches it to a Send-To preset. This action is specific to accounts connected to GFcrew and requires a linked template relationship to be set up in the template editor. See Linked templates for setup details.
How API keys relate to Zapier
Every action and trigger in the Zapier app uses the API key you provided when you connected the app. The key authenticates as your organization — there is no per-user permission layer inside the Zapier app. Any action the key can perform, the Zap can perform.
The same API key can be used simultaneously in the Zapier app and in direct API calls from your own code. If you revoke the key, both the Zap and any code using that key stop working immediately. Create separate keys if you want to revoke access to one integration without affecting the other.
To view all active keys or create a new one, go to Settings → API Keys in the Templified dashboard.
Comments
0 comments
Article is closed for comments.