Send your first webhook
Goal: install Webhooks Pro, configure one webhook, and see a real Jira event arrive at an external URL. Time: about 5 minutes (plus install). You'll need: Jira admin permission, plus an HTTPS endpoint that can accept a JSON
POST. If you don't have one yet, use webhook.site — it gives you a free, public test URL in one click
1. Install Webhooks Pro
If the app isn't installed yet:
Open Jira → Apps → Find new apps.
Search for Webhooks Pro.
Click Try it free (or Buy it now).
Confirm the install.
Jira administrators can open Webhooks Pro under Settings (⚙️) → Marketplace apps → Webhooks Pro → Webhooks.
(Full install detail: Install Webhooks Pro from Marketplace.)
2. Create the webhook
On the Webhooks page, click Create webhook.
Fill in the General Configuration:
| Field | Value |
|---|---|---|
1 | Name |
|
2 | Active | On |
3 | Description | (leave empty for now) |
Fill in the URL Configuration:
| Field | Value |
|---|---|---|
4 | HTTP Method |
|
5 | Webhook URL | The URL you got from webhook.site (or your own endpoint) |
6 | Payload Template |
|
Leave HTTP Headers and URL Parameters empty. Skip the Security (HMAC signing) section for now — you can add a signing secret later, see HMAC signing and secrets.
3. Pick at least one event
Open the Events tab. There are four sub-tabs — start with Issue Related Events.
Tick Issue created and Issue updated. Skip the JQL filter for now (everything in your Jira will fire). You can narrow it later — see JQL filtering.
At least one event is required before you can save.
4. Save
Click Save in the top-right (or press Ctrl+S / ⌘S).
The first time you point a webhook at a new host, Forge will ask the Jira admin to approve outbound network access to that host. Approve it once — Webhooks Pro can now reach that destination for the rest of the app's life.
If approval is rejected, the save fails with a clear message. See Approve egress to your endpoint.
5. Trigger an event
Open any Jira issue. Make a small edit — change the priority, post a comment, anything that's covered by the events you ticked.
Now go back to Settings (⚙️) → Marketplace apps → Webhooks Pro → Webhook Logs.
Within a few seconds you should see a new row:
Green 2xx status — the receiver accepted the body.
Click the row to expand the full request and response — URL, headers, body, the receiver's response, and timing.
If you used webhook.site, you'll also see the payload land in the webhook.site browser tab.
Why "a few seconds" and not "instantly"? Webhooks Pro debounces fast bursts of edits to the same entity, so a burst of changes lands as one delivery. See Debounce and coalescing.
6. (Optional) Try Send Test
Re-open your webhook in edit mode. There's a Send Test button at the top.
It fires a delivery with a synthetic issue payload — useful when you want to validate the receiver without making a real Jira change. The result is shown right in the form (status code + round-trip time).
You're done
You now have:
One webhook listening for issue events
A delivery log you can replay from
Forge egress approval for that destination
Where to go next
Filter what gets sent — JQL filtering
Shape the JSON body — Payload templates
Send to Slack / GitHub / PagerDuty — Recipes and use cases
Sign every delivery — HMAC signing and secrets
Schedule a periodic webhook — Scheduled webhooks
If something goes wrong — and the delivery shows red, network error, or never appears at all — start at Diagnose a failing delivery. It's the shortest path from "log row is wrong" to "fixed".