Support
Answers to common questions. Can't find what you need? Reach out directly.
Email support
Monday–Friday, 9:00 AM–5:00 PM EST. Response within 24–48 business hours.
Covered
- Installation, configuration, and setup in Jira Cloud
- Webhook payload formatting and provider troubleshooting
- License, renewal, and Marketplace billing inquiries
- Bug reports, security disclosures, feature requests
Not covered
- Custom software development or custom API integration coding
- Administration of third-party monitoring tools beyond webhook payload config
Does ForgeHook use my Jira Automation rule runs?
No. ForgeHook runs on Atlassian Forge and interacts directly with the Jira Cloud REST API. It uses 0 Jira Automation runs.
Where do I find my inbound webhook endpoint URL?
Go to your Jira Cloud site → Settings (⚙️) → Apps → ForgeHook Webhook Router. The endpoint URL is displayed at the top of the page.
Why is my webhook returning HTTP 401 Unauthorized?
Make sure your request includes the header x-forgehook-token: <your_secret_token> or Authorization: Bearer <your_secret_token> matching the secret token generated in your ForgeHook settings.
Why is my webhook returning HTTP 402 Payment Required?
HTTP 402 means your Atlassian Marketplace trial has expired or your subscription is inactive. Renew your subscription in Atlassian Marketplace to resume automatic ticket creation.
Is my webhook data safe?
Yes. ForgeHook runs 100% inside Atlassian's secure cloud infrastructure. Webhook data never leaves Atlassian's trust boundary, and secrets are stored using write-only encryption. See the Privacy Policy for details.