Make connects to Quire through the REST API and webhooks, with Make’s own HTTP and webhook modules. Everything in the API reference is available.
Start a scenario from a Quire event
- Add the Webhooks module Custom webhook as the first module, and copy its address.
- In Quire, open
/admin/webhooks, choose Add subscription, paste the address and choose the events. Quire’s test event lets Make learn the shape of the body: run the module once while it is sent. - Verify the signature before acting. In the webhook’s advanced settings,
pass the headers through, then check
webhook-signatureagainst{webhook-id}.{webhook-timestamp}.{body}with the subscription secret, as the developer guide describes. Add a filter that stops the scenario when the check fails.
Call Quire from a scenario
Use the HTTP module Make a request:
| Field | Value |
|---|---|
| URL | https://acme.quirelms.com/api/v1/<resource> |
| Method | As the API reference says |
| Headers | Authorization: Bearer qk_live_..., and Idempotency-Key for writes |
| Body type | Raw, JSON |
| Parse response | Yes |
Make a key for Make alone at /admin/integrations/api-keys, with only the
scopes the scenario needs. For lists, loop while page.has_more is true,
passing page.next_cursor as cursor: Make’s Repeater with a Set
variable carrying the cursor does this.
For scenarios that should act as a person, register an OAuth client at
/admin/integrations/oauth-clients and use Make’s HTTP module Make an
OAuth 2.0 request with it.
Example: weekly completion digest
- Schedule: every Monday.
- HTTP:
GET /api/v1/course_completions?updated_since=<a week ago>. - Iterator over
data, Aggregator into a table. - Email or post the table.