Webhooks, Zapier and Make

What you get

• Events: score.dropped, visibility.lost, visibility.gained, scan.completed, answers.updated, site.created, site.deleted.
• An HMAC signature on every request so you can verify it came from us.
• Automatic retries after 5 minutes, 30 minutes, 2 hours, 6 hours and 24 hours.
• A delivery log on the Integrations page showing what was sent and how your endpoint answered.

Before you start

• An OLAB Assist account on the Agency plan, signed in as the account owner.
• A Zapier, Make or n8n account, or an https endpoint of your own.

Set it up step by step

1. 1

   Create a catch hook

   Zapier: new Zap → trigger Webhooks by Zapier → Catch Hook. Make: new scenario → Webhooks → Custom webhook. n8n: a Webhook node with method POST. Copy the address it gives you.

2. 2

   Add it in OLAB Assist

   Integrations → Webhooks: paste the address, set the format to JSON, tick the events you want and click Add webhook. Copy the signing secret shown once.

3. 3

   Send a test

   Click Send test. Your tool receives a ping event and learns the fields.

4. 4

   Add the action

   For example Asana → Create Task with the title “Score dropped on {{data.site.domain}}” and the report link from data.report_url. Add a filter on type if one hook receives several events.

5. 5

   Turn it on

   Publish the Zap or scenario. From now on every matching event runs it.

{
  "id": "evt_4Hh2…",
  "type": "score.dropped",
  "api_version": "v1",
  "created_at": "2026-10-05T10:00:00.000Z",
  "data": {
    "site": { "id": "k3Jd9x2Lq", "domain": "example.com", "app_url": "…" },
    "previous_score": 86, "score": 71,
    "drop_points": 15, "drop_pct": 17.4,
    "report_url": "https://olabassist.com/r/…"
  }
}

Tips

• Use one webhook per destination. Each has its own events, threshold and secret.
• Use the event id to ignore duplicates: a retried event keeps its id.
• Developers: verify OLAB-Signature as shown in the developer docs.

Troubleshooting

Questions