Webhooks let Forager automatically notify an external system every time an attestation is recorded. The most common use is pushing location updates to ServiceNow CI records.Documentation Index
Fetch the complete documentation index at: https://docs.harbinge.rs/llms.txt
Use this file to discover all available pages before exploring further.
Where to find it
Webhook configuration is in the Forager Android app, not the web dashboard. You must be logged in as an admin. From the home screen: tap your profile avatar → Admin → expand the Webhooks section.Adding a webhook
Enter the endpoint details
| Field | What to enter |
|---|---|
| Name | A label for your own reference, e.g. ServiceNow Production |
| URL | The full HTTPS URL Forager will POST to on every attestation |
| Secret Header | The HTTP header used for authentication, e.g. X-ServiceNow-Token or Authorization |
| Secret Value | The credential value, e.g. Basic abc123... or Bearer token... |
Available payload variables
| Variable | Description |
|---|---|
{{asset_tag}} | The scanned asset tag |
{{location_path}} | Full breadcrumb, e.g. Building A / Floor 2 / IT Office |
{{anchor_name}} | Room name only, e.g. IT Office |
{{updated_by}} | Display name of the tech who scanned |
{{type}} | match, mismatch_confirmed, mismatch_dismissed, or new_asset |
{{timestamp}} | ISO 8601 UTC timestamp |
Disabling a webhook temporarily
Toggle the switch on the webhook card to off. Attestations continue to be recorded in Forager — they are not queued for later delivery. Re-enable when ready; only new attestations from that point forward will be sent.Detailed setup guides
ServiceNow — Scripted REST API
Recommended for direct, real-time CI updates
ServiceNow — Import Sets
For environments that require staged CMDB writes