Make integration
Yes, over plain HTTP. There is no dedicated Make app: a scenario subscribes with POST /api/v1/hooks and unsubscribes with DELETE /api/v1/hooks/{id}, using an organisation API key. The subscribe response does not include the signing secret. To verify deliveries, an administrator rotates that hook on the Webhooks page, which shows a new secret once, and the scenario checks X-Webhook-Signature with it.
See pricing (from $1 per active user)
Included from the Basic plan, $1 per active user per month.
At a glance
Make has no dedicated app yet, so a scenario subscribes with two plain HTTP module calls and receives deliveries on a Make webhook URL. Signature verification needs the secret from a rotation on the Webhooks page.
| Status | Built, not yet verified |
|---|---|
| Included from | Basic plan (API) |
| Authentication | Organisation API key; HMAC-SHA256 signed deliveries |
| Data that flows | Out: the subscribed event payload to your Make webhook URL |
| Not yet | A dedicated Make app; the secret returned at subscribe time |
How to set it up
- Create an API key in the Personal Academy admin area with the scopes you need.
- In Make, add a webhook trigger and an HTTP module that POSTs its URL and the event name to /api/v1/hooks.
- To verify signatures, rotate the new hook on the Webhooks page and store the secret shown once in the scenario.
Highlights
- Same REST Hooks endpoints as the Zapier app
- HMAC-SHA256 signed deliveries
- Works with any Make plan that includes the HTTP module
Technical overview
Authentication:API key (Authorization: Bearer)
Setup Time:~15 minutes
Prerequisites:
- •An API key with the relevant module scopes and settings.manage.
- •A scenario that can make outbound HTTP calls.