Skip to main content

Webhooks

Webhooks are automatic notifications. When something happens in RuleForge (an approved review, a published version, a failing regression), the product notifies the system you choose — Slack, Microsoft Teams, a Jira ticket, an internal automation, any tool that accepts URL-based notifications.

When to use them​

Use webhooks to:

  • alert the team in a chat channel when a version is published;
  • open a ticket automatically when a regression fails;
  • notify an internal system when a review needs attention;
  • trigger an automation whenever new feedback arrives.

Create a webhook​

  1. Open Settings → Integrations → Webhooks.
  2. Click New webhook.
  3. Enter the destination URL (the system that will receive the notification).
  4. Add a short description so you can identify it later.
  5. Choose which events should trigger the notification.
  6. Optionally, set a secret — it lets the destination system verify the notification really came from RuleForge.
  7. Save.

Available events​

Events are grouped by subject. The main ones:

  • Validation and testing: when a validation or log test ends, success or failure.
  • Regression: when a regression is executed and the outcome is known.
  • Review: when a review is created, approved, rejected, or receives change requests.
  • Version: when a version is created, published, or the publish attempt fails.
  • Feedback: when someone sends feedback to your organization.
  • API keys: when a key is created or revoked (useful for security trails).

The full, always up-to-date list is in Webhook events.

Accepted URLs​

To protect your organization, RuleForge only accepts public URLs with http or https. Local or private-network URLs are blocked — this prevents a misconfigured webhook from reaching sensitive internal addresses.

Delivery and retries​

  • Every notification is recorded in the webhook's history, with the result (success or error).
  • If the destination is temporarily unavailable, RuleForge retries before giving up.
  • You can open the history to understand specific failures and resend manually when needed.

Common issues​

The webhook didn't fire​

Check, in order:

  1. Whether the event is selected in the webhook options.
  2. Whether the flow that should trigger the event actually happened (for example, did a version actually get published?).
  3. Whether your organization's plan includes integrations.
  4. Whether the destination system is publicly accessible.

The destination rejects the notification​

Confirm that the secret configured on the webhook matches what the destination system uses to validate notifications.

I can't save the URL​

You probably entered a local or private URL. Use the destination system's public address.