Setting up a Webhook destination

This article shows you how to connect a webhook endpoint so Templified pushes a JSON notification to your server every time a design is exported from Studio. Once the webhook is connected, you can attach it to a Send-To Preset and receive render results automatically in Zapier, Make, n8n, or any HTTPS service.

What you need

An HTTPS endpoint that can receive POST requests — your own server, a Zapier catch hook URL, a Make (formerly Integromat) webhook, or any HTTPS listener.
Owner or admin role in your organization. Members can use presets that include a Webhook destination, but cannot add or change the webhook configuration.

Configure your webhook URL

The Webhook card in Settings → Integrations showing the Webhook URL, HMAC secret, Enabled toggle, Save & enable button, and Send test button

Go to Settings → Integrations.
Find the Webhook card.
In the Webhook URL field, paste your HTTPS endpoint — for example https://hooks.zapier.com/hooks/catch/…. The URL must use HTTPS.
Optionally, enter a value in the HMAC secret field. When set, Templified signs each request with a SHA-256 HMAC and includes the signature in the X-Templified-Signature header (format: sha256=<hex>). Your server can verify this signature to confirm the request came from Templified. Leave the field blank to skip signing.
Make sure the Enabled toggle is on.
Click Save & enable. The card immediately shows Enabled in green.

Test the connection

After saving, click Send test. Templified posts a sample request to your URL and shows the HTTP status code and response body inline. A 2xx response confirms the endpoint is reachable. If the test fails, check that your URL is publicly accessible and that any firewall or authentication on your server accepts requests from Templified.

The Send test button is disabled while there are unsaved changes — save first, then test.

What gets pushed: the notification body

Every time a design is exported from Studio, Templified sends an HTTP POST to your URL with Content-Type: application/json. The body is a JSON object with the following fields:

Field	Type	Description
`event`	string	Always `"studio.export"`
`exportedAt`	ISO 8601 string	Timestamp of the export
`orgId`	string	Your organization identifier
`instanceId`	string or null	The design ID, or `null` for renders submitted via the API without a design
`templateId`	string	The template the design is based on
`designName`	string	The design's name
`folder`	string	The Studio folder the design lives in
`imageUrl`	string	Public URL of the finished render image
`qty`	number (optional)	Number of copies requested; absent if 1 (default)
`mainEventCode`	string or null (optional)	Main Event Code set on the design, if any
`destinationEventCode`	string or null (optional)	Destination Event Code set on the design, if any
`playerId`	string or null (optional)	Player identifier, if present on the design
`textLayers`	array	One object per text layer: `{ name, content }` — the layer name and its resolved text value

Your server must respond with any 2xx status code within 10 seconds. Templified retries failed deliveries up to three times with increasing delays before marking the delivery as failed.

Using the webhook in a preset

The preset editor with a Webhook destination row showing the note 'Sends to your organization's configured webhook URL'

Once the webhook is configured, you can add it as a destination in any Send-To Preset. To do this:

Go to Settings → Send-To Presets and open or create a preset.
Click Add destination and choose Webhook.
The editor confirms the destination sends to your organization's configured webhook URL. There are no per-preset fields to fill in — the URL is set once at the integration level.
Click Save.

When a team member fires this preset, Templified renders the design and pushes the notification to your webhook alongside any other destinations attached to the preset (for example, a Dropbox folder). Your endpoint receives one POST per send regardless of how many destinations the preset contains.

To change the endpoint later, return to Settings → Integrations and update the Webhook URL. The change takes effect immediately on the next send.

Async sends and the 202 response

When Templified dispatches a preset, the send itself may complete asynchronously — meaning the export is queued and processed in the background. In that case the server returns a 202 Accepted response to the sending client rather than waiting for all destinations to finish. Your webhook endpoint is still called once the render completes; the timing is not instantaneous but the notification is guaranteed (subject to retry limits above).

If you are calling the Templified API directly and need to handle asynchronous responses, see the Developer API reference for details on the 202 async response shape and how to poll for job status.

Remove the webhook

To disconnect the webhook, open Settings → Integrations, find the Webhook card, and click Remove. This also removes the webhook destination from any preset that used it. Sends that had this webhook destination will still complete to any other destinations on the same preset.