Render destinations
The finished file lands where it needs to be — automatically.
Skip the "download, then re-upload somewhere else" step. Tell a render where it should end up — hosted storage, Google Drive, an inbox, or a webhook — and it gets delivered there the moment it's generated.
Paid plans only — see plans
Four places to land
Hosted storage with a URL, Google Drive, an email address, or a webhook — pick whichever fits the workflow.
Signed, so receivers can trust it
Webhook deliveries are signed with your API key's stable secret, so the receiving end can verify it actually came from you.
You always know what happened
A delivery hiccup never loses the render — you still get the file back, plus a clear delivery.ok flag to react to.
What people build with this
Invoices straight to email
Generate the PDF and email it to the customer in the same call — no separate mail step in your automation.
Reports into shared Drive folders
Land a fresh report in a Google Drive folder your team already checks, without a manual upload.
Assets into your own pipeline
Push finished renders to a webhook so your own backend can pick them up and continue the workflow.
Frequently asked
What destinations are supported?
Four: hosted storage (get back a URL), Google Drive, email, and webhook delivery of a signed payload.
Do I still get the file back if I set a destination?
Yes — the render response still includes the file (or a delivery confirmation), so a delivery issue never means you lose the output.
How do I verify a webhook delivery actually came from Templates On?
Every webhook payload is signed with your API key's stable webhook secret, so you can verify authenticity on your end.
Skip the download-and-reupload step for good.
Tell a render where it belongs. It shows up there on its own.
Create your free account