Use case

Personalized videos, triggered by your app

Render a personalized clip the moment something happens: a signup, a renewal, a milestone, a year in review. One reactive template, one MP4 per user, fired from your own events.

An app event firing a webhook that renders a personalized clip for one user

Personalized video is stuck as a once-a-year stunt

Everyone loves a 'year in review', but building one is a project, so it happens once and never for the small moments in between.

Too much effort to do often

A hand-built personalized video is a one-off project. So it ships once a year, if at all, and never for the everyday moments.

No way to react in real time

The interesting moments, a signup, a renewal, a streak, happen continuously. A manual process cannot answer them as they occur.

Engineering rebuilds it each time

Without a template, every campaign is bespoke rendering code, so each new idea starts from scratch.

How it works with Bluepic

1

Design the moment once

Build one animated template in Studio, a welcome, a thank-you, a milestone, with the name, a stat, and an avatar connected as input fields.

2

Wire it to an event

Call the render from your backend's webhook, a scheduled job, or a Zapier / Make / n8n step that fires when the event happens.

3

Render and deliver per user

Each event renders one personalized MP4 for that user. Read the result URL and drop it into an email, an in-app message, or a push.

A concrete example

Call the render from your own backend when an event fires, or from a no-code step in Zapier, Make, or n8n. Pass the user's details as data:

// inside your "user.anniversary" event handler
await fetch("https://api.bluepic.io/api/render", {
  method: "POST",
  headers: { Authorization: "<your API key>", "Content-Type": "application/json" },
  body: JSON.stringify({
    templateId: "<your celebration template>",
    data: { name: user.firstName, years: user.tenureYears, avatar: { src: user.photo } },
    format: "mp4",
  }),
});
// read the stream to the `end` event for the hosted MP4, then email or push it

Rendering the stream is covered in generate video via API.

Why an API changes the economics

Always-on, not once a year

The same template answers every moment, so personalized video becomes a standing capability instead of a special project.

Real-time, per user

Render on the event, for that person, with their data. A milestone can become a clip in their inbox minutes later.

One template, no rebuilds

New campaigns are new data against the same template, not new rendering code. Change the design once and every future clip inherits it.

Automate a moment worth celebrating

Design the template once, then let your events render the clips.