Register a SafetyCulture webhook for inspection, action, and issue events

Steps

1. Ensure the registering credential has the right permission: a user needs "Administrator," a service user needs "Override permissions: Manage all data."
2. Register an HTTPS endpoint in your application to receive webhook POST payloads, then create the webhook subscription selecting one or more trigger events (e.g., `TRIGGER_EVENT_INSPECTION_HAS_STARTED`, `TRIGGER_EVENT_ACTION_CREATED`, `TRIGGER_EVENT_INCIDENT_CREATED`, `TRIGGER_EVENT_MEDIA_UPLOADED`).
3. On receipt, read `event.event_types`, `resource.id`/`resource.type`, and the `data` block — SafetyCulture sends a lightweight payload, not the full record.
4. For inspections, cross-check completeness periodically using the Search modified inspections endpoint (`modified_after`) as a fallback for missed or out-of-order deliveries.
5. Handle retries and duplicates idempotently: failed deliveries (4xx/5xx) are retried up to 4 times with a 100-second delay between attempts, and delivery order/uniqueness is not guaranteed.