Integrations · Make

Run Subscriby Scenarios in Make

A webhook listener for any of the 145 events and HTTP modules for every read and write, on the same token and spec as everything else

Make has no native Subscriby app, and it does not need one: its custom webhook listener takes any of the 145 signed events, and its HTTP modules call every read and write on the REST API from the published OpenAPI spec. The guide gives you the listener setup, the signature check as a short JavaScript module, and the HTTP module settings, so a scenario that starts from a new member and ends with a coupon or a broadcast is a few modules long.

Set Up Free in 30 Minutes

Read the guide

Inbound: Custom webhook listener; Create the listener, paste its address as a webhook endpoint in Subscriby, pick the events; every delivery arrives signed.
Outbound: HTTP modules on the OpenAPI spec; Every read and write across 30 resource families, called with a personal access token you scope yourself.
Signature check: A short module; The guide ships the HMAC verification as a serverless JavaScript module you paste once and reuse in every scenario.
Retries: 8 attempts over about 4 days; A listener that is down does not lose the event: Subscriby retries on a widening ladder and logs every attempt.
Sign-in: One personal access token; You choose which of the 107 abilities the token carries; a scenario that only reads never holds the right to write.
Included on: Every plan, including Free; The API and the webhooks cost nothing extra on any plan; Make bills you for Make.

What Make gives you

No app to wait for

The listener and the HTTP module are built into Make, so there is nothing to install, approve or update; the OpenAPI spec tells the module every field.

Every event, signed

Any of the 145 events can start a scenario, and the signature module proves each delivery came from Subscriby before the scenario acts on it.

Every read and write

Anything the dashboard can do, an HTTP module can do, with the same token abilities; add an idempotency key header to a write and a re-run scenario never creates a duplicate.

Switch later without loss

A scenario built on the raw API and webhooks moves to Zapier, n8n or your own code unchanged in substance, because they all use the same two doors.

How to connect

1
Create a scenario in Make and add a Webhooks, Custom webhook listener at the top; copy its address.
2
In Subscriby, add a webhook endpoint with that address, pick the events, save, and copy the endpoint secret.
3
Paste the signature module from the guide into the scenario and give it the secret, so unsigned deliveries stop there.
4
Create a personal access token with the abilities the scenario needs, under Settings, API tokens.
5
Add HTTP modules for the reads and writes you need, with the token as a bearer header and the fields from the OpenAPI spec.

Read the guide

Best for

Teams already on Make
Scenarios that mix Subscriby with a dozen other apps
Anyone who prefers built-in modules to yet another app

Often paired with

The integrations creators wire in beside this one.

ZapierAn instant trigger for each of the 145 events, an action for every write and a search for every read, on a token you scope yourself n8nA verified community node: a trigger for each of the 145 events and an action for every REST endpoint, on Cloud and self-hosted

Common Questions

Read the guide

Is there a native Make app?

No, and none is needed: the custom webhook listener and the HTTP module are built into Make and cover every event and every endpoint. The guide has the exact settings.

How do I verify a delivery is from Subscriby?

Every delivery carries an HMAC signature header over the timestamp and the body. The guide ships the check as a short JavaScript module for Make; a mismatch means the scenario should stop.

What if my scenario is off when an event fires?

Subscriby retries a failed delivery up to 8 times over about 4 days on a widening ladder, and the delivery log shows every attempt; when the listener is back, the event arrives.

Which token do I use?

A personal access token created in Subscriby with only the abilities the scenario needs, out of 107, sent as a bearer header from the HTTP module.

Does it cost extra?

No. The API and the webhooks are on every plan, including Free; your Make plan is your own.

Start Free — Build Your First Scenario Today

Free plan includes 3 projects. No monthly fee — card on file required to charge transaction fees.

Set Up Free in 30 Minutes