This tutorial shows you how to create a design group, add templates to it, and trigger a single batch render that produces one finished image per template — so you can deliver a complete product set (5×7, wallet, poster, digital) from one API call or Zapier step.
What is a design group?
A design group is a named collection of templates that renders all at once. Instead of submitting one render call per size or layout, you submit one call against the group and get back a set of finished images — one per member template — tied to a single batch ID.
Typical use: a team-photo package where every athlete needs a 5×7 print, a digital download, and a wallet strip from the same photo and name fields. Build the three templates once, add them to a design group, and every future order renders all three in one step.
Design groups appear on the Templates tab alongside individual templates and can be organized into folders.
Create a design group
- Open the Templates tab in the top navigation.
- Select the folder where the group should live from the folder tree on the left.
- Click the New button in the top-right corner of the content area, then choose New Design Group.
- In the dialog, type a Design group name and confirm the folder. Click Create.
Templified navigates directly to the design group's detail page after creation.
Add templates to the group
On the design group detail page, the Templates section lists the group's current members. To add a template:
- Click Add Template in the top-right of the Templates section.
- In the picker dialog, use the folder filter dropdown to narrow the list — choose All folders or a specific folder. This is useful when your library is large.
- Click a template row to add it immediately. The template appears in the member list without closing the dialog, so you can add several in sequence.
- Close the dialog when done.
Templates already in the group are hidden from the picker. To reorder members, drag the grip handle on the left of any row. To remove a member, hover the row and click the trash icon, then confirm.
Folder filter in the picker
The Add Template picker opens pre-filtered to the folder your group lives in. Switch to All folders or another folder using the dropdown at the top of the picker if your templates are spread across multiple folders.
Page-2 templates cannot be group members
If a template is the second page of a two-page template, it cannot be added to a design group. Only stand-alone templates and page-1 templates are eligible. The picker automatically excludes page-2 rows, so they will not appear in the list.
Consolidated fields
Below the member list, the Consolidated Fields section shows every dynamic field across all member templates — the union of names and photos that the group expects. These are the field names you pass in the fields object when submitting a batch render.
If two templates share an api_field_name (for example, both have a layer named Photo), the group uses that single key to fill both layers from one value.
Navigate to a design group
From the Templates tab, design group cards appear in the grid alongside template cards. Click a design group card to open its detail page. You can also use the three-dot menu on a card to rename, move to a different folder, or delete the group.
Submit a batch render (API)
The design group detail page includes an API Reference section with your group's ID and a ready-to-copy example request. The endpoint is:
POST /api/v1/design-groups/create
Required fields in the request body:
| Field | Type | Description |
|---|---|---|
group_id |
string | The design group ID (shown on the detail page). |
fields |
object | Key-value pairs matching the consolidated field names. Photo fields take a public image URL; text fields take a string. |
batch_webhook_url |
string (optional) | An HTTPS URL that receives a single callback once every render in the batch reaches a terminal state. Use this for Zapier steps that need one resume signal for the whole batch. |
webhook_url |
string (optional) | An HTTPS URL that receives a callback per individual render as each one completes. |
A successful request returns HTTP 202 with a batch_id, a poll_url, and a jobs array containing one entry per member template.
curl -X POST https://studio.templified.io/api/v1/design-groups/create \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"group_id": "YOUR_GROUP_ID",
"fields": {
"Photo": "https://example.com/player.jpg",
"Name": "Jordan Smith",
"Jersey": "24"
},
"batch_webhook_url": "https://example.com/webhooks/batch-done"
}'
Poll the returned poll_url to check overall batch status, or wait for the batch_webhook_url callback — whichever fits your workflow.
Comments
0 comments
Article is closed for comments.