How to Connect Webhooks, Zapier, and Make to SocialProof.Reviews

Testimonials are most powerful when they flow automatically into the rest of your business — your CRM, your Slack, your email marketing platform, your spreadsheet. SocialProof.Reviews fires a webhook every time a new testimonial is submitted, giving you a real-time trigger you can route anywhere.

What Is a Webhook?

A webhook is an HTTP POST request your workspace sends to a URL you choose, the moment a new testimonial comes in. The payload contains everything about the submission — the reviewer's name, email, rating, review text, photos, and metadata. Your receiving system can then do anything: log it, notify your team, update a CRM record, or trigger a drip sequence.

Setting Up Your Webhook URL

Step 1: Navigate to your workspace settings

Log in to SocialProof.Reviews, open your workspace, and go to the Embed & Integrations section in your admin panel. Find the Webhooks tab.

Step 2: Add your endpoint URL

Paste the URL that should receive the POST request. This can be:

• A Zapier Webhook trigger URL
• A Make (formerly Integromat) webhook URL
• Your own server endpoint
• A Pipedream, n8n, or any other automation platform URL

Step 3: Save and test

Click Save, then use the Send test event button to fire a sample payload to your endpoint. Verify it arrives correctly before going live.

Webhook payload format

Every testimonial submission sends a JSON payload structured like this:

{
  "event": "testimonial.submitted",
  "workspaceId": "abc123",
  "testimonialId": "t_xyz789",
  "submittedAt": "2026-03-17T10:30:00Z",
  "reviewer": {
    "name": "Jane Smith",
    "email": "[email protected]",
    "jobTitle": "Head of Marketing",
    "company": "Acme Corp",
    "photoUrl": "https://..."
  },
  "rating": 5,
  "review": "This tool completely changed how we collect and display customer feedback.",
  "photos": ["https://...", "https://..."],
  "videoUrl": null,
  "approved": false,
  "source": "collect-form"
}

---

Connecting to Zapier

Zapier lets you connect SocialProof.Reviews to 6,000+ apps without writing any code.

Step 1: Create a new Zap

Log in to zapier.com and click Create Zap.

Step 2: Set up the trigger

1. Search for and select Webhooks by Zapier as your trigger app
2. Choose Catch Hook as the trigger event
3. Click Continue — Zapier will generate a unique webhook URL like https://hooks.zapier.com/hooks/catch/123456/abcdef/
4. Copy that URL

Step 3: Paste the URL into SocialProof.Reviews

1. Go to your workspace Webhooks & Zapier page in the admin panel
2. Paste the Zapier URL into the Endpoint URL field
3. Click Save changes

Step 4: Test — Zapier must be listening first

⚠️ Important: Zapier only accepts the test payload while it is actively waiting for a trigger. If it is not listening you will get a 401 error.

1. In Zapier, make sure you are on the Test trigger step — Zapier is now listening
2. Go back to SocialProof.Reviews and click ⚡ Send test
3. Return to Zapier and click Test trigger — it will confirm it received the payload and show you all available fields (reviewer name, email, rating, review text, etc.)

Step 5: Add your action

Now connect any action you want. Examples:

Notify your team in Slack:

• Action app: Slack
• Event: Send Channel Message
• Message: New ⭐⭐⭐⭐⭐ review from {{reviewer__name}} at {{reviewer__company}}: "{{review}}"
• Channel: #testimonials

Add reviewer to your email list (Mailchimp):

• Action app: Mailchimp
• Event: Add/Update Subscriber
• Email: {{reviewer__email}}
• First name: {{reviewer__name}}
• Tag: testimonial-submitted

Log to a Google Sheet:

• Action app: Google Sheets
• Event: Create Spreadsheet Row
• Map columns: Date, Name, Email, Company, Rating, Review

Create a contact in HubSpot:

• Action app: HubSpot
• Event: Create or Update Contact
• Email: {{reviewer__email}}
• Custom property "Testimonial given": Yes

Step 6: Turn on your Zap

Click Publish and every new testimonial submission will now automatically trigger your workflow.

---

Connecting to Make (formerly Integromat)

Make is a more visual, developer-friendly automation platform. It's ideal if you need multi-step flows, conditional logic, or data transformation.

Step 1: Create a new scenario

Log in to make.com and click Create a new scenario.

Step 2: Add a Webhooks module

1. Click the + to add a module
2. Search for Webhooks
3. Select Custom webhook (choose this — not "Custom mailhook")
4. Click Add → give it a name (e.g. "SocialProof Reviews") → click Save
5. Make generates a URL like https://hook.eu1.make.com/abc123xyz — copy it
6. Click OK on the webhook module — the module will show a clock icon (🕐), meaning it is now actively waiting for data

Step 3: Paste into SocialProof.Reviews

1. Go to your workspace Webhooks & Zapier page in the admin panel
2. Paste the Make URL into the Endpoint URL field
3. Click Save changes

Step 4: Send the test — Make must be listening first

⚠️ Important: Make only accepts the webhook while it is actively listening. If Make is not in listening mode you will get a 401 error.

1. In Make, confirm the clock icon is visible on the webhook module — this means it is waiting
2. If the clock is not showing, click Run once (bottom-left of the scenario editor) to re-activate it
3. Go back to SocialProof.Reviews and click ⚡ Send test
4. Return to Make — it will have captured the payload and auto-detected all fields (event, reviewer name, email, rating, review text, etc.)
5. Click OK to confirm the data structure

Step 5: Determine the data structure

After the test payload is received, Make shows you every field available to use in your automation. You will see:

Step 5: Add modules after the trigger

Examples of powerful Make automations:

Filter by rating, then notify:

• Add a Filter module: only continue if rating >= 4
• Add a Slack module: post to #wins channel

Approve high-rating testimonials automatically:

• Add a Filter: rating = 5
• Add an HTTP module: PATCH your workspace API endpoint to set approved: true

Add to a CRM with conditional logic:

• Add a Router module to split paths
• Path A: if reviewer.company is not empty → update company record in Salesforce
• Path B: if reviewer.company is empty → add to Mailchimp consumer list

Create a Notion database entry:

• Add a Notion module: Create database item
• Map: Name, Company, Rating, Review text, Submission date

Step 6: Activate the scenario

Click the power toggle at the bottom left of the scenario editor to turn it on. Make will now process every incoming testimonial webhook.

---

Security Note

SocialProof.Reviews sends webhooks from a fixed set of IP addresses and includes a signature header (X-SPR-Signature) you can use to verify the request is genuine. To validate:

1. Compute HMAC-SHA256 of the raw request body using your workspace secret key
2. Compare to the value in X-SPR-Signature
3. Only process the request if they match

This prevents replay attacks and ensures no one can spoof fake testimonials into your automations.

---

Common Webhook Use Cases

Use case	Platform	Trigger	Action
Real-time Slack alert	Zapier	testimonial.submitted	Slack message
Auto-tag in email list	Make	testimonial.submitted (rating ≥ 4)	Tag subscriber
Log all reviews	Zapier	testimonial.submitted	Google Sheets row
Push to CRM	Make	testimonial.submitted	HubSpot/Salesforce contact
Auto-approve 5-star	Make	testimonial.submitted (rating = 5)	API PATCH approved=true
Trigger drip sequence	Zapier	testimonial.submitted	Mailchimp automation

---

Troubleshooting

Step 1 — Verify with webhook.site first

Before blaming Make, Zapier, or your own server, confirm that SocialProof.Reviews is actually sending the request:

1. Go to webhook.site — you'll get a unique URL immediately (no sign-up needed)
2. Copy that URL
3. Paste it into the Endpoint URL field in your Webhooks & Zapier settings
4. Click Save changes
5. Click ⚡ Send test

You should see ✓ Sent! Payload delivered to your endpoint. in the app, and a new request appear on webhook.site within a second or two. Click it to inspect the full JSON payload.

If webhook.site receives it, your SocialProof.Reviews webhook is working correctly — the problem is with your Make/Zapier setup, not with the platform. Proceed to Step 2.

If webhook.site does not receive it, double-check that you clicked Save changes after pasting the URL and that the Enable webhooks toggle is switched on.

---

Step 2 — Fix Make 401: delete and recreate the webhook module

A 401 from Make means the webhook token is invalid or unregistered — Make does not recognise the URL. This happens when a scenario was not properly saved after the webhook was created, or the webhook was deleted. Simply clicking "Run once" will not fix a 401; you need to recreate the webhook module entirely.

1. In your Make scenario, right-click the Webhooks module → click Delete
2. Click the + to add a new module → search for Webhooks → select Custom webhook
3. Click Add → give it a name (e.g. "SocialProof Reviews") → click Save
4. Make generates a new URL — copy it, then click OK to dismiss the dialog
5. Critical: click the 💾 Save button (top of the scenario editor) to persist the new webhook. If you skip this step the token won't be registered and you'll get 401 again.
6. Now click Run once (bottom-left) — a clock icon (🕐) should appear on the webhook module, meaning Make is now actively listening
7. Go back to SocialProof.Reviews — paste the new URL into Endpoint URL, click Save changes, then click ⚡ Send test

Make will capture the payload and show all available fields. Click OK to confirm the data structure, then continue building your scenario.

---

✗ HTTP 401 — Make/Zapier rejected the request. The most common cause is that Make or Zapier was not actively listening when you clicked Send test, or the webhook token is invalid (see Step 2 above for Make). Fix:

• Make: Follow Step 2 above to delete and recreate the webhook module, save the scenario, then click Run once before sending the test.
• Zapier: Navigate to the Test trigger step in your Zap editor so Zapier is waiting, then click Send test again. The listener only stays active for a few minutes, so test promptly after activating it.

✗ HTTP 404 — Webhook URL not found. The URL has been deleted or the scenario/zap has been disabled. Go back to Make or Zapier, check the webhook module still exists, and copy a fresh URL.

✗ Could not connect / HTTP 0. The URL is either not reachable or you have not saved it yet. Make sure you clicked Save changes after pasting the URL, and that the URL starts with https://.

The test delivers but real submissions don't. Check two things: (1) the Enable webhooks toggle is turned on and saved, and (2) the events you want are checked under Events to send. Real submissions only trigger when the webhook is enabled.

My endpoint isn't receiving the webhook. Check that your URL is publicly accessible — localhost URLs will be rejected. Use webhook.site to confirm the payload is being sent (see Step 1 above).

I'm getting duplicate events. Implement idempotency on your receiving endpoint using testimonialId as a deduplication key.