Install Webhooks Pro from Marketplace
Webhooks Pro is distributed exclusively through the Atlassian Marketplace. There is no side-load, no manual upload, no JAR. Install from the Marketplace; new versions arrive through the standard upgrade path.
Who can install
A Jira site admin (Atlassian organisation admin) — same person who can install any Marketplace app. Project admins and regular users can't.
If you don't have admin permission, ask your Jira admin to install Webhooks Pro and grant you access. After install, anyone with Admin permission on the Jira site can configure webhooks; non-admins don't see the app at all.
Install in 4 clicks
In Jira, click the Apps menu in the top navigation → Find new apps.
Search for Webhooks Pro.
Click the result, then Try it free (or Buy it now if you've already purchased).
Confirm the install dialog.
Atlassian shows the list of Jira API scopes the app declares — these are the minimum permissions Webhooks Pro needs to subscribe to events and send outbound HTTP. Review them and confirm.
After install, Jira administrators can open Webhooks Pro under Settings (⚙️) → Marketplace apps → Webhooks Pro.
What happens on install
Storage initialised in your tenant. Webhooks Pro stores everything (webhooks, payload templates, logs, settings) inside Forge's per-app storage on Atlassian's infrastructure. Nothing is sent to UX Software.
A 30-day free trial starts automatically the first time you install on a site. See How the Webhooks Pro trial works.
No outbound traffic yet. The app cannot reach any external URL until a Jira admin approves the destination — see Approve egress to your endpoint.
The default payload template (named
Default) is created so your first webhook works without configuring a template.
After install
Open Settings (⚙️) → Marketplace apps → Webhooks Pro → Webhooks and follow Send your first webhook.
To check trial status, SEN, or billing details, open Webhooks Pro → Settings → About → Subscription.
Upgrades
New versions of Webhooks Pro ship through the Atlassian Marketplace. Upgrades are automatic unless your organisation has explicitly disabled auto-upgrades on the Marketplace settings.
When a new version is available, Atlassian shows it in Settings (⚙️) → Marketplace apps → Manage apps. Release notes for each version live on What's new in Webhooks Pro.
You can also subscribe to release-note updates from the Webhooks Pro Marketplace listing page.
Uninstalling
Settings (⚙️) → Marketplace apps → Manage apps → Webhooks Pro → Uninstall.
Uninstalling deletes Webhooks Pro's data for this site — webhook configurations, payload templates, delivery logs, settings, the lot. There is no undo. If you may reinstall later, Export your webhooks first (button on the Webhooks list) — the JSON bundle is self-contained and can be re-imported.
Workflow post-function bindings on Jira workflows survive uninstall as orphan references; they stop firing immediately because the app that handles them is gone. Reinstalling restores the bindings if the workflow definition still names them.
Multi-site / multi-tenant
A licence is issued per Atlassian site (e.g. your-company.atlassian.net). If your organisation runs several Jira sites, each one needs its own install + its own subscription. Configurations and logs do not sync across sites — each site is a separate tenant from Webhooks Pro's point of view.
To replicate a configuration across sites, Export from one site and Import on the others (Settings → Backup).
Related
Send your first webhook — go straight to a working delivery.
Approve egress to your endpoint — the per-host approval Forge requires.
How the Webhooks Pro trial works — what changes when the 30 days are up.
Subscription states and SEN — find your SEN, read the in-app subscription card.