Users love a badge they earned, and they share the ones that look good. The problem is generating one per user, per milestone, without a design queue. This workflow closes that gap. Your app already knows when someone hits a milestone, so let it fire a webhook and get a finished badge back.
How it works
- A milestone webhook fires from your app. When a user unlocks something, POST a small JSON payload to the workflow webhook with the achievement name, the user, and a date.
- A badge is rendered from the payload. Orshot reads those fields and renders a PNG from your template. Long names and short ones both fit because the text resizes to the layout.
- You get a hosted image URL back. The render returns as an Orshot URL. Drop it into your app, a share card, or an email. It works anywhere a link works.
Why badges bring traffic back
A shared badge is a link with your product on it. Every user who posts one is putting your name in front of people who trust them, and each of those people can click through. You are not buying that reach, you are rendering it, one earned badge at a time.
Who builds this
SaaS and app teams
A badge on a milestone screen or in a lifecycle email, generated from the event you already track.
Learning platforms
Course and streak badges learners can post, each rendered from the completion payload.
Community products
Reputation and contributor badges that members show off, made the moment they are earned.
Creator tools
Achievement cards your users share, turning their wins into links back to your product.
