Gravity Forms
+ Keygen Premium

Turn every form submission into a Keygen software licence. The Gravity Forms Keygen Premium Add-on takes each submission and, through the Keygen API, issues a licence under the policy you choose, storing any metadata you map from your form fields — a buyer email, an order id, a plan name. It can optionally create a Keygen user from the submission and attach the licence to them, so a sign-up, a purchase or a trial request mints a ready-to-use licence key the moment the form is submitted.

It is built for anyone who sells or distributes software and runs their licensing in Keygen: indie developers, SaaS teams, plugin and app makers who want a licence created automatically from a form instead of by hand. Decide per feed which policy to use, which fields become licence metadata, and whether to also create and attach a Keygen user. Because you connect with your own Keygen account, the add-on works with hosted Keygen at api.keygen.sh or with a self-hosted Keygen instance at your own base URL. The issued licence key and licence id are kept with the entry and available as merge tags for your notifications — so the buyer gets their key by email straight away.

You connect it with your own Keygen account id and an admin or product API token. The token is encrypted before it is stored on your site, it is never shown again and never written to an entry or a log; the issued licence key is stored with the entry to back the merge tag and is shown only masked in the entry notes. The add-on only ever contacts the Keygen API at the base URL you set. A Test connection button on the settings page confirms your account and token by reading your policies, without issuing anything, and the design is safe to retry: a licence is issued once per entry, even if a submission is resent.

When a form is submitted and the feed condition is met, the add-on resolves the policy (the feed's policy id, or the default from the settings), builds the licence metadata from the fields you mapped, and — if you turned on Create a user — first posts a Keygen user built from the submission. It then posts one request to create the licence under that policy, with the optional user attached and the metadata on the licence, to the Keygen API with your token in the Bearer Authorization header. The host is fixed to the base URL you set (api.keygen.sh for hosted, or your self-hosted host), a redirect is never followed, and the token never travels in the URL or the body. The issued licence key is stored on the entry to back the {keygen_license_key} merge tag, a clear note records the result with the key masked, and the action runs once per entry so a retry never mints a second licence.