Skip to main content
Plan requirement: This feature requires an On-call Standard or higher subscription. Learn more
Use a Flagsmith organisation-level audit log webhook to sync feature flag and segment changes to Flashduty On-call. Each Flagsmith audit log entry that affects flag evaluation becomes one Flashduty change. Examples include changing a flag’s state or remote config value, creating or deleting a flag, editing segment rules or segment overrides, publishing an environment feature version, or changing an identity override. Flagsmith sends changes that have already taken effect, so Flashduty records each change as Done directly.

In Flashduty On-call

  1. In the Flashduty console, go to Integration Center → Change Events
  2. Select Flagsmith and enter an integration name
  3. To assign changes to specific channels, add rules under the integration’s Routes that match labels such as project or environment
  4. Click Save and copy the generated Push URL

Configure Flagsmith

1

Create an organisation webhook

  1. Go to Organisation Settings and open the Webhooks tab
  2. Create an audit log webhook
You need organisation administrator permission. Use the organisation audit webhook (Create audit webhook). Besides audit log entries, Flagsmith also sends FLAG_UPDATED and FLAG_DELETED events to this URL; Flashduty returns success for them and records nothing.
2

Enter the push URL

  1. URL: paste the full push URL of the Flashduty integration
  2. Secret: leave it empty. Flashduty authenticates the delivery by the integration_key in the push URL and does not verify X-Flagsmith-Signature
  3. Enable the webhook and save
Flagsmith sends the audit log of every project in the organisation to this URL. After saving, make a change to any flag and it appears in the Flashduty change list. The Test your webhook button in the webhook dialog gets a success response from Flashduty and records no change.

How changes are merged

Create one integration per Flagsmith instance: if several instances share an integration, audit log entries from different instances can be treated as the same change.

Status mapping

These deliveries return success but record no change:
  • Entries of other types, such as change requests (CHANGE_REQUEST), environments, import requests, feature health, and release pipelines
  • Flag metadata edits such as name, description, and tags (Flag / Remote Config updated)
  • Entries that only schedule a change that has not taken effect yet (the log text contains scheduled for); Flagsmith sends a separate entry when the change goes live
  • Deliveries whose event type is not AUDIT_LOG_CREATED, such as FLAG_UPDATED and FLAG_DELETED
  • Flagsmith’s test request

Change content

Use labels for routing and for filtering the change list:

FAQ

No. A retry carries the same content as the original delivery, and Flashduty records it once.
Check the ignore list in Status mapping above: metadata edits, the change request itself, and the creation of a scheduled change don’t create records. A record appears when the change request is committed and takes effect, or when the scheduled change goes live. Also confirm the webhook is configured at the organisation level and enabled.
  • … is missing or invalid …: the payload is incomplete or a field is malformed. Confirm it comes from a Flagsmith organisation-level webhook