Skip to content
EntryWick documentation

Make — EntryWick for Make · integrations/make

Build Make scenarios on EntryWick: watch for registrations, check-ins and payments, look registrations up, and on Scale create registrations, issue tickets and record check-ins. Built in week 15 step 5 on API v1 and webhooks alone (ADR-009, ADR-027), alongside the Zapier app (docs/product/zapier.md).

Who can use it

  • Growth and above can connect it (zapier covers Zapier and Make). On Growth: Watch Events and Search Registrations.
  • Scale and above also get Create a Registration, Issue a Ticket and Record a Check-in; on Growth they answer "This action needs the Scale plan".

Connecting

In EntryWick, Organization → API keys → New key with the read and write scopes (and scanner to record check-ins); in Make, add an EntryWick connection and paste it. The connection is labelled with the organization and key.

Modules

  • Watch Events — pick what happened (any of the 19 webhook types, WEBHOOKS §1) and optionally one event. Make creates a webhook endpoint in Organization → Webhooks described "Make: …" and deletes it when the scenario's webhook is removed. The bundle is the envelope as sent: type, created_at, livemode, and the resource under data (previous on an update).
  • Search Registrations — by name, email, phone or ticket, or external id; up to the number of results asked for.
  • Create a Registration — one person, through the event's rules, capacity and approval.
  • Issue a Ticket — for a person (and day) with none.
  • Record a Check-in — the scanner's decision; a refused scan is a result, not an error.

Audit

Changes made through Make are in the audit log with source api, the key as actor and client make.

Open

  • Owner: Make account, deploying the project, publishing it as a community app (NEEDS_FROM_OWNER.md).
  • Unlike the Zapier app, Watch Events does not check EntryWick-Signature: Make gives the module the parsed body, not the raw bytes the signature covers (decisions-pending.md).