Skip to main content
Forager ships a private Zapier app with two instant triggers: New Attestation and Mismatch Detected. Unlike the custom CMDB webhooks, this path needs no proxy server, no code, and no payload template — you connect Zapier to Forager with an API key and build Zaps directly in Zapier’s editor. Choose this approach if you want to react to Forager events in Zapier without standing up your own endpoint — for example, posting to Slack, filing a row in Google Sheets, or creating a ticket in a tool Forager doesn’t natively integrate with.

​
What the integration does

Forager’s Zapier app exposes two instant triggers (delivered via REST hooks, not polling): Both triggers fire within seconds of the scan, the same as Forager’s CMDB webhooks.

​
Step 1 — Generate an API key

  1. Go to Dashboard → Settings → API Keys & Zapier
  2. Click Generate Key
  3. Copy the key immediately — it is shown only once and cannot be retrieved again after you leave the page
If you lose the key, you’ll need to generate a new one and reconnect your Zaps. Store it in a password manager if you’re not connecting Zapier right away.
The same panel lists your active Zapier subscriptions (one per Zap trigger you’ve turned on) and lets you revoke the key entirely.

​
Step 2 — Accept the private app invite

Forager’s Zapier app is currently unlisted (private). Your Forager administrator will provide an invite link to the private app — accepting it adds “Forager” as an available app in your Zapier account. You only need to do this once per Zapier account.

​
Step 3 — Build a Zap

  1. In Zapier, create a new Zap and search for Forager as the trigger app
  2. Choose New Attestation or Mismatch Detected as the trigger event
  3. Click Connect Account and paste the API key from Step 1
  4. Click Test trigger — Zapier pulls a handful of recent attestations (or mismatches) as sample data so you can map fields into the rest of your Zap
  5. Add your action steps (Slack message, Google Sheets row, ticket creation, etc.) and turn the Zap on
Once the Zap is on, Forager registers a subscription and pushes matching events to Zapier in real time — no polling delay.

​
Payload field reference

Every trigger delivers the same shape, regardless of which of the two triggers fired:
Mismatch Detected only ever delivers type: "mismatch_confirmed" — it’s a pre-filtered feed of the New Attestation trigger. Use it when you only care about location discrepancies and don’t want to add a Zapier filter step.

​
Revoking access

Revoking the API key (Settings → API Keys & Zapier → Revoke) immediately deletes all Zapier subscriptions tied to it. Any Zaps using that connection stop receiving events right away — you’ll need to generate a new key and reconnect before they’ll fire again.

​
Troubleshooting

​
See also

Make.com Integration

Reuse Forager’s existing CMDB webhooks to trigger Make scenarios

Webhook Reference

Schema and delivery behavior for Forager’s custom CMDB webhooks