Webhooks & CRM Integrations

Push review data to your CRM, Slack, or any system with a URL. HMAC-signed payloads with automatic retries.

Who this is for

Businesses with existing systems

You already use a CRM, ticketing system, or automation platform. You need review data flowing into it — not another tab to check.

Teams using Slack, HubSpot, or Salesforce

Get pinged when ratings change. Route review metadata to the right CRM contact or account automatically.

The problem

Review data is siloed in ReviewPanel. Your CRM doesn't know when ratings change. Your Slack doesn't get pinged when new reviews arrive. Your automation workflows can't react to review events.

Without webhooks, someone has to manually check and relay information between systems — or it simply doesn't happen.

How it works

  1. 1

    Configure a webhook endpoint URL

    Point to any HTTPS endpoint — your own server, Zapier, Make, n8n, or a Slack incoming webhook.

  2. 2

    Choose payload detail level

    Metrics only, metrics + locations, or metrics + locations + latest review. Control how much data each webhook sends.

  3. 3

    Attach CRM identifiers (optional)

    Include a HubSpot Company ID, Salesforce Account ID, or custom key-value pairs in every payload for routing.

  4. 4

    Events fire on each sync when data changes

    Webhooks only fire when something actually changes — new reviews, rating shifts, or deleted reviews detected.

  5. 5

    HMAC-signed payloads with automatic retries

    Every payload is signed with your webhook secret for verification. Failed deliveries are retried automatically with exponential backoff.

Feature availability by plan

PlanWebhooksCRM identifiers
Starter (free)
Personal
Professional
Enterprise

Limitations

  • Webhooks fire when data changes are detected during a sync — not instantly when a review is posted on Google. Timing depends on your sync schedule.
  • This is CRM metadata passthrough, not a direct API integration with HubSpot or Salesforce. You attach identifiers; your automation tool routes them.
  • Webhooks require your endpoint to respond with a 2xx status. Non-responsive endpoints are retried up to 5 times before being marked as failing.

FAQ

Is this real-time?

No. Webhooks fire when data changes are detected during a sync cycle. This means there's a delay between when a review is posted on Google and when your webhook fires — depending on your plan's sync frequency.

Does this integrate directly with HubSpot or Salesforce?

Not directly. ReviewPanel sends webhook payloads with your CRM identifiers (Company ID, Account ID, or custom pairs) attached. Your middleware or automation tool (Zapier, Make, n8n) routes them to the correct CRM record.

What's in the payload?

JSON with metrics (rating, review count, changes), optionally location details and the latest review. All payloads include a timestamp and your configured CRM identifiers.

What's the retry behavior?

Failed deliveries (non-2xx response or timeout) are retried up to 5 times with exponential backoff. If all retries fail, the webhook is marked as failing and you're notified in your dashboard.

Can I rotate my webhook secret?

Yes. You can regenerate your HMAC signing secret at any time from webhook settings. The old secret is invalidated immediately — update your verification logic before rotating.

Connect your reviews to everything else

Webhooks available on Professional and Enterprise plans. Start tracking reviews free, upgrade when you're ready to integrate.

Get Started Free