Skip to main content

Make scenario

Connect Testimonial Webhooks to Make Scenarios

Make (the tool once called Integromat) starts a scenario when its Custom webhook module receives a request. StoryProof, from Pro, sends one for every new review. The pairing is simple; the details worth getting right are the data structure, the queue, and a webhook that Make switches off if left unattached.

  • One Custom webhook per scenario
  • Data structure detected from a real review
  • What happens when the scenario is off

Scenario checklist

Build the Custom webhook properly the first time

Make’s webhook docs are short on warnings, so the ones that matter for a review feed are pulled into this list.

Create the webhook
Teach it the shape of a review
Run it safely

Ticks are stored nowhere but this page view.

The problem, solved

Where review scenarios break in Make

  • Problem 1

    There is no StoryProof module to choose

    Make’s app list does not show one, so the scenario seems impossible.

  • Problem 2

    Later modules cannot see the review fields

    Without a detected structure, Make has nothing to offer in the mapping panel.

  • Problem 3

    An agency runs this for several clients

    One shared webhook mixes clients’ reviews in a single scenario.

  • Problem 4

    A scenario published a review before anyone read it

    The webhook fires as reviews arrive, before any decision about them.

  • Problem 5

    No webhooks on our current plan

    There is nothing to start the scenario.

Make webhook facts that shape the design

All from Make’s documentation as read on 2026-11-17.

FactWhat it means for a review feed
Default response is 200 AcceptedStoryProof gets a success reply unless you add a Webhook response module
Rate limit of 300 requests per 10 secondsFar above a normal review flow
Requests queue when not processed at onceA scheduled scenario still receives reviews; they wait
Logs kept for 3 days (30 on Enterprise)Debug a missing review soon, not next month

In StoryProof

From first module to live scenario

Step 1 of 4

Create the Custom webhook

Add the module, create and name the webhook, and copy its address.

Before you start

Limits of this setup

  • No StoryProof app in Make

    StoryProof is not described as a Make integration. The webhook and Make’s Custom webhook module are the link.

  • Structure comes from a sample

    This page does not describe the delivery’s fields. Make learns them from a real review, and so should you.

  • Webhooks have a plan floor

    Included from Pro. Make’s own credits are separate.

  • Make’s docs, not a live run

    The Make steps follow its help center and app docs as of 2026-11-17 and were not run in a live account.

FAQ

Questions people ask

Short answers to what usually comes up next.

Is Make the same as Integromat?

Make is the current name of the product once called Integromat. The Custom webhook module is in its Webhooks app.

Can two scenarios share one StoryProof webhook address?

Make gives each scenario its own webhook. If two jobs need the same reviews, run both from one scenario, or have that scenario pass the data on.

Why did my webhook start returning 410?

Make deactivates a webhook that has not been connected to any scenario for more than five days.

Should I turn on the API key option?

Only if you can confirm the StoryProof request carries Make’s key header. Otherwise the requests will be refused.

Still have a question? Ask the StoryProof team or book a demo.

Start a Make scenario with every new review

Collect reviews with StoryProof and catch each one in a Make Custom webhook.

Sources

  1. Webhooks app: Custom webhook, Make Apps documentation. Checked 2026-11-17.
  2. Webhooks, Make Help Center. Checked 2026-11-17.

Last updated 2026-11-17.