Opsgenie webhook setup

Create Velocity issues from alerts in an existing Opsgenie account.

Configure Velocity and Opsgenie

  1. As a workspace owner or admin, open Settings → Integrations → Opsgenie, choose the target team and a secret of at least 16 characters, then save.
  2. Choose whether closing an alert should complete its linked issue. This is off by default for new connections.
  3. In Opsgenie, open Settings → Integrations, add a Webhook integration and enable it. Configure its alert-created and alert-closed action mappings to POST to https://velocity.quest/api/webhooks/opsgenie.
  4. Add a custom header named X-Velocity-Secret with the same secret you saved in Velocity. Send the native JSON payload with action and alert fields.
  5. Create an owned alert. Refresh Recent callbacks in Velocity and open its linked issue. Close the alert to verify the completion setting.

Events

Create creates an issue in the selected team, or reuses the issue linked to that alert ID. Acknowledge, unacknowledge, escalation and note events add alert activity. Close completes the linked issue when the completion setting is enabled. The Velocity activity records automated status changes as System.

Secrets and reconnecting

The custom header authenticates native Opsgenie callbacks. Keep it private and out of the callback URL. Saved secrets are encrypted in configured deployments and never returned to the settings page. Rotate the secret in Velocity, copy the new value into Opsgenie, and choose a bounded overlap window. Existing relays that compute X-Opsgenie-Webhook-Signature HMAC-SHA256 continue to work; an explicitly supplied HMAC must be valid.

Disconnect in Velocity and disable the provider webhook when removing the connection. Reopen the setup page to connect again.

Troubleshooting

If delivery is rejected, check the custom header and enabled integration. If a callback arrives without an issue, check the target team and any issue-creation warning shown in Recent callbacks. Configure provider action mappings for every action you expect to receive.

Atlassian Webhook integration documentation · Native alert callback payloads