Make.com Integration

Forager has no dedicated Make.com app. Instead, Make connects through the same outbound CMDB webhook system used for ServiceNow, Freshservice proxies, and other targets — pointed at a Make Custom webhook trigger. No API key is needed. Choose this approach if you’re building automations in Make and want Forager attestations as a trigger, without waiting on a dedicated Make app.

What happens

Tech scans an asset (Forager app)
  → Attestation recorded in Forager
  → Forager POSTs the configured JSON template to your Make webhook URL
  → Make scenario runs, using the payload fields

Every attestation is sent — match, mismatch_confirmed, mismatch_dismissed, and new_asset alike. If you only want mismatches, filter for them inside the Make scenario (see below).

Step 1 — Create the Make scenario

In Make, create a new scenario
Add a Webhooks module → Custom webhook as the trigger
Click Add, name it (e.g. Forager Attestations), and save
Copy the generated webhook URL — it looks like https://hook.us1.make.com/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Step 2 — Add the webhook in Forager

Go to Dashboard → Settings → CMDB Webhooks → Add Webhook
Fill in:

Field	Value
Name	`Make.com`
Endpoint URL	The Custom webhook URL you copied from Make
Target Platform	`Custom template`
Payload Template	The default template (see below) works as-is — edit it if your scenario needs different fields

Save. The webhook fires on every attestation from this point forward.

Recommended JSON template

This is Forager’s default webhook_configs payload template — it works unmodified for Make:

{
  "asset_tag": "{{asset_tag}}",
  "location": "{{location_path}}",
  "anchor": "{{anchor_name}}",
  "confidence": {{confidence}},
  "updated_by": "{{updated_by}}",
  "timestamp": "{{timestamp}}"
}

Available template variables

Variable	Resolves to
`{{asset_tag}}`	Barcode of the scanned device
`{{location_path}}`	Full location breadcrumb
`{{anchor_name}}`	Room name (last segment of `location_path`)
`{{confidence}}`	Match confidence score
`{{updated_by}}`	Tech’s display name
`{{timestamp}}`	ISO 8601 UTC timestamp
`{{type}}`	Attestation outcome — `match`, `mismatch_confirmed`, `mismatch_dismissed`, or `new_asset` (add this to the template if you plan to filter on it, per Step 3 below)

The default template doesn’t include {{type}}. Add "type": "{{type}}" to the JSON template in Forager if you want to filter on attestation outcome inside Make — see Step 3.

Step 3 — Filter for mismatches only (optional)

Because Make receives every attestation, add a Filter immediately after the trigger module if your scenario should only act on mismatches:

Click the filter icon on the connection between the trigger and your next module
Set the condition: {{type}} Equal to mismatch_confirmed
Save

Only attestations where a tech confirmed a location discrepancy will continue past this point in the scenario.

Troubleshooting

Symptom	Likely cause	Fix
Scenario never runs	Webhook URL mismatched, or webhook not saved/enabled in Forager	Re-copy the Make webhook URL into Forager’s CMDB Webhooks panel and confirm it’s enabled
Scenario runs but fields are empty	Template variable names don’t match the JSON template	Check `{{variable}}` names in the Forager payload template against the reference table above
Scenario runs on events you don’t want	No filter step added	Add a Filter module after the trigger, per Step 3
Nothing recorded in Make’s execution history	No attestations have fired yet	Perform a test scan in the Forager app to trigger a delivery

Zapier Integration

Instant triggers via Forager’s private Zapier app — no webhook template needed

Webhook Reference

Full schema and delivery behavior for Forager’s custom CMDB webhooks

Getting Started

Field Tech Guide

Dashboard

EC Inspection Rounds

Admin

Integrations

API Reference

Troubleshooting

What happens

Step 1 — Create the Make scenario

Step 2 — Add the webhook in Forager

Recommended JSON template

Available template variables

Step 3 — Filter for mismatches only (optional)

Troubleshooting

See also

Zapier Integration

Webhook Reference

​What happens

​Step 1 — Create the Make scenario

​Step 2 — Add the webhook in Forager

​Recommended JSON template

​Available template variables

​Step 3 — Filter for mismatches only (optional)

​Troubleshooting

​See also

Zapier Integration

Webhook Reference

What happens

Step 1 — Create the Make scenario

Step 2 — Add the webhook in Forager

Recommended JSON template

Available template variables

Step 3 — Filter for mismatches only (optional)

Troubleshooting

See also